-
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
[mono] [wasi][wasm] Wasm AOT breaks wasm export functions #101276
Labels
arch-wasm
WebAssembly architecture
area-Codegen-AOT-mono
os-wasi
Related to WASI variant of arch-wasm
Milestone
Comments
dotnet-issue-labeler
bot
added
the
needs-area-label
An area label is needed to ensure this gets routed to the appropriate area owners
label
Apr 19, 2024
dotnet-policy-service
bot
added
the
untriaged
New issue has not been triaged by the area owner
label
Apr 19, 2024
vcsjones
removed
the
needs-area-label
An area label is needed to ensure this gets routed to the appropriate area owners
label
Apr 19, 2024
dotnet-policy-service
bot
removed
the
untriaged
New issue has not been triaged by the area owner
label
Apr 25, 2024
I can reproduce this. Works with trimming but no aot, does not work with |
I also have a repro
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
arch-wasm
WebAssembly architecture
area-Codegen-AOT-mono
os-wasi
Related to WASI variant of arch-wasm
Description
After a recent fix, wasm interpreter no longer require a unmanaged delegate as workaround to initialize exports. But it looks like the AOT version still get the uninitialized element error.
Reproduction Steps
Expected behavior
The console prints:
Actual behavior
The console prints:
Regression?
No response
Known Workarounds
No response
Configuration
NET9 + Windows + Wasmtime + WASI SDK 21
Tested with .NET 9 alpha local build with latest commit a344abd
Tested with .NET 9 Preview 3 installed from the official website
Other information
Directly export function to Wasmtime lead to the same issue.
It worked fine with no RunAOTCompilation
The text was updated successfully, but these errors were encountered: