-
Notifications
You must be signed in to change notification settings - Fork 3.4k
Disable import/export name mangling in -O3 builds #16695
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
Comments
There is an option in one of the Binaryen tools wasm-emscripten-finalize.cpp on line 60 that could be relevant. Also this issue is marked as relevant in the code: WebAssembly/binaryen#3043. |
You can build at |
We did have another request to explicitly disable this minification from @eyebrowsoffire.. should we consider making this separately configurable? |
I guess that would mean moving |
I am working with a custom runtime and would like to disable the name mangling in the generated runtime, i.e., the renaming of imports/exports inside the WebAssembly module to
a
,b
,c
, etc. WhileSTANDALONE_WASM
sounds ideal for this use case, unfortunately it is nowhere near ready for more complicated applications that need runtime support for Pthreads and Asyncify. Is there a hack or a workaround to disable this name mangling so that the module imports/exports have deterministic names?Version of emscripten/emsdk:
The text was updated successfully, but these errors were encountered: