-
Notifications
You must be signed in to change notification settings - Fork 5.1k
[wasi] Fix WasmLinkIcalls and WasmNativeStrip support. #91843
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
Conversation
/azp run runtime-wasm |
Azure Pipelines successfully started running 1 pipeline(s). |
Looks like the aot compiler is not included in the wasi runtime pack. |
I thought AOT didn't currently work on wasi due to the inability to rely on runtime features? |
The WasmLinkIcalls task relies on it to generate the icall table in the runtime. |
/azp run runtime-wasm |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run runtime-wasm |
Azure Pipelines successfully started running 1 pipeline(s). |
src/mono/nuget/Microsoft.NET.Workload.Mono.Toolchain.Current.Manifest/WorkloadManifest.json.in
Outdated
Show resolved
Hide resolved
/azp run runtime-wasm |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run runtime-wasm |
Azure Pipelines successfully started running 1 pipeline(s). |
Depends on: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Blocked on #92095 but looks good once that lands
Build analysis is green |
No description provided.