[mono][wasm] wasm interop tracking

[lewing]

Tracking issue for WasmInterop:

• [mono][wasm] Add interpreter support for calls to UnmanagedCallersOnly EntryPoint without managed delegate reference #95087
• PInvokeTableGenerator improvements
  • Handle DllImport function pointers properly [wasm] p/invoke and interop improvements #94446
  • Support Wasm module imports when WasmLinkageAttribute is applied to DllImport
  • Fix DllImport marshaling
  • Support EntryPoint on UnmanagedCallersOnly
    • Export UCO entry point in WASM module

[ghost]

Tagging subscribers to 'arch-wasm': @lewing
See info in area-owners.md if you want to be subscribed.

Issue Details

---

Tracking issue for WasmInterop:

• Make interpreter support calls to UnmanagedCallersOnly EntryPoint without managed delegate reference
• PInvokeTableGenerator improvments
  • Handle DllImport function pointers properly
  • Support Wasm module imports when WasmLinkageAttribute is applied to DllImport [wasm] Implement initial support for WasmImportLinkage in the AppBuilders #94615
  • Fix DllImport marshalling
  • Support EntryPoint on UnmanagedCallersOnly [wasm] Implement initial support for WasmImportLinkage in the AppBuilders #94615
    • Export UCO entry point in WASM module [wasm] Implement initial support for WasmImportLinkage in the AppBuilders #94615

Author:	lewing
Assignees:	-
Labels:	arch-wasm, area-Interop-coreclr, untriaged
Milestone:	-

[silesmo]

#96419

[maxkatz6]

Right now DllImport on WASM throws a compiler error, if there is an unsupported pinvoke or marshaling. Such as com interop, or some windows specific marshaling.

Since on other platforms DllImport seems to be lazily evaluates, unsupported DllImport would crash in runtime when executed. Which is fine, since such code would commonly be hidden under platform conditions, and never actually be executed. But with WASM it’s not possible.

Was there an idea to, possible, replace such pinvokes with stubs that would throw an exception in runtime? Mimicking behavior of non-wasm platforms.

[lewing]

Right now DllImport on WASM throws a compiler error, if there is an unsupported pinvoke or marshaling. Such as com interop, or some windows specific marshaling.

Since on other platforms DllImport seems to be lazily evaluates, unsupported DllImport would crash in runtime when executed. Which is fine, since such code would commonly be hidden under platform conditions, and never actually be executed. But with WASM it’s not possible.

Was there an idea to, possible, replace such pinvokes with stubs that would throw an exception in runtime? Mimicking behavior of non-wasm platforms.

I'm not sure what .NET version or runtime you are referring to but the WASM runtimes definitely support most DLLImports (as static imports) when the build is correctly configured.

[pavelsavara]

maybe this is already fixed @lewing @mkhamoyan ?

[mkhamoyan]

I am not sure about Fix DllImport marshaling.
If that is related to this #94895 I guess we can close this ticket, and follow up in #94895.

[maxkatz6]

@lewing hi. I found that I didn't answer to your question about unsupported DllImports.
Just created an issue with more details and repro: #104463