[mono][wasm] Fix the usage of function pointers in mixed mode.

[vargaz]

The llvm compiled code expects function pointers to be a MonoFtnDesc*, while
the interpreter expects them to be a InterpMethod*. Use a MonoFtnDesc in
both cases.

[ghost]

Tagging subscribers to this area: @BrzVlad
See info in area-owners.md if you want to be subscribed.

Issue Details

---

The llvm compiled code expects function pointers to be a MonoFtnDesc*, while
the interpreter expects them to be a InterpMethod*. Use a MonoFtnDesc in
both cases.

Author:	vargaz
Assignees:	-
Labels:	area-Codegen-Interpreter-mono
Milestone:	-

[vargaz]

Fixes #50965

[BrzVlad]

It's ugly that passing function pointers between aot and interp would only work in llvmonly. Is it feasible, if we decide to care about it, to use function descriptors also in normal jit/aot mode when doing a ldftn ?

[vargaz]

For non-llvmonly mode, the interpreter should use the same representation as the jitted code i.e. normal pointers to the method code, for interpreted code, that would be some kind of trampoline to enter the interpreter.

[BrzVlad]

That would have problems on the interp side, since, instead of having direct access to the InterpMethod when doing a ldftn, we would have this native pointer that we have to call and enter the interpreter every time.

[vargaz]

/azp run

[azure-pipelines]

You have several pipelines (over 10) configured to build pull requests in this repository. Specify which pipelines you would like to run by using /azp run [pipelines] command. You can specify multiple pipelines using a comma separated list.

[vargaz]

/azp run runtime runtime-staging

[azure-pipelines]

No pipelines are associated with this pull request.