You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
WebAssembly memory is normally exported under memory name, but when wasm-bindgen runs on a Wasm file built with an atomics feature, it gets mangled to __wbindgen_export_0.
That sounds like a bug in one of the possible passes along the way, likely something that's de-exporting it and then re-exporting it later, forgetting the original export name along the way.
The text was updated successfully, but these errors were encountered:
Describe the Bug
WebAssembly memory is normally exported under
memory
name, but when wasm-bindgen runs on a Wasm file built with anatomics
feature, it gets mangled to__wbindgen_export_0
.Steps to Reproduce
wasm2wat
orwasm-dis
orwasm-objdump
etc.Expected Behavior
The memory is exported under name
"memory"
as it does by default in any Wasm builds by LLVM.Actual Behavior
The memory is exported under name
"__wbindgen_export_0"
which is not stable enough name to rely on.Additional Context
From #2102 (comment) via @alexcrichton:
The text was updated successfully, but these errors were encountered: