-
Notifications
You must be signed in to change notification settings - Fork 4.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[wasm] marshling call to assembly entrypoint via new interop #73156
[wasm] marshling call to assembly entrypoint via new interop #73156
Conversation
…d_assembly_entry_point` - moved legacy imports and split `RuntimeHelpers`
Tagging subscribers to 'arch-wasm': @lewing Issue Details
|
/azp run runtime-wasm |
Azure Pipelines successfully started running 1 pipeline(s). |
# Conflicts: # src/mono/wasm/runtime/imports.ts # src/mono/wasm/runtime/startup.ts
...rvices.JavaScript/src/System/Runtime/InteropServices/JavaScript/Interop/JavaScriptExports.cs
Show resolved
Hide resolved
...rvices.JavaScript/src/System/Runtime/InteropServices/JavaScript/Interop/JavaScriptExports.cs
Outdated
Show resolved
Hide resolved
...rvices.JavaScript/src/System/Runtime/InteropServices/JavaScript/Interop/JavaScriptExports.cs
Outdated
Show resolved
Hide resolved
…stem/Runtime/InteropServices/JavaScript/Interop/JavaScriptExports.cs Co-authored-by: Katelyn Gadd <kg@luminance.org>
/azp run runtime-wasm |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run runtime-wasm |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run runtime-wasm |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run runtime-wasm |
Azure Pipelines successfully started running 1 pipeline(s). |
# Conflicts: # src/mono/wasm/runtime/dotnet.d.ts # src/mono/wasm/runtime/exports.ts # src/mono/wasm/runtime/imports.ts # src/mono/wasm/runtime/managed-exports.ts # src/mono/wasm/runtime/net6-legacy/method-calls.ts # src/mono/wasm/runtime/startup.ts
...rvices.JavaScript/src/System/Runtime/InteropServices/JavaScript/Interop/JavaScriptExports.cs
Outdated
Show resolved
Hide resolved
...rvices.JavaScript/src/System/Runtime/InteropServices/JavaScript/Interop/JavaScriptExports.cs
Outdated
Show resolved
Hide resolved
...rvices.JavaScript/src/System/Runtime/InteropServices/JavaScript/Interop/JavaScriptExports.cs
Outdated
Show resolved
Hide resolved
…stem/Runtime/InteropServices/JavaScript/Interop/JavaScriptExports.cs Co-authored-by: Marek Fišera <mara@neptuo.com>
…stem/Runtime/InteropServices/JavaScript/Interop/JavaScriptExports.cs Co-authored-by: Marek Fišera <mara@neptuo.com>
…stem/Runtime/InteropServices/JavaScript/Interop/JavaScriptExports.cs Co-authored-by: Marek Fišera <mara@neptuo.com>
/azp run runtime-wasm |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run runtime-wasm |
Azure Pipelines successfully started running 1 pipeline(s). |
is #73330 fix should be #73366
is #73347 Debugger failures are #73342 |
for 8 we should consider emitting a |
JavaScriptExports.CallEntrypoint
replacing legacymono_bind_assembly_entry_point
RuntimeHelpers
dotnet-legacy.d.ts
set_arg_type
on manually writtenJavaScriptExports
calls