-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
Asyncify whitelist and blacklist support #9094
Conversation
…le Asyncify implementation in the wasm backend.
@kripken I tried new WHITELIST feature of asyncify. I used emscripten/incoming, binaryen/incoming and emsdk/clang-incoming-64bin (9.0). Hope this envronment config is valid, because emcc told me
many times. Also I have those warnings, which seems strange:
In runtime I have this error
Also I little bit worried that symbols file now contain demangled names, it's breaking change for tools such bug reporters. Seems I need to demangle whitelist file to use it with this feature, is it correct? (I replaced "_main" with "main" and it remove one warning). |
After passing function names with
I think parser didn't catch function names like
|
Nope, even I used exact name from
|
@caiiiycuk yeah, this is tricky - the wasm backend emits "human-readable" names, not normal mangled ones. I added some notes in settings.js about this. I'm surprised by your second comment though. Perhaps |
A slight complication here is that we need function names for the lists. This extends the current symbol-map mechanism to keep around function names in the wasm until the very end of the optimization pipeline. (There are still risks with inlining and duplicate function elimination changing things, though, which can't be solved without adding some new special function annotation.) Uses WebAssembly/binaryen#2218
A slight complication here is that we need function names for the lists. This extends the current symbol-map mechanism to keep around function names in the wasm until the very end of the optimization pipeline. (There are still risks with inlining and duplicate function elimination changing things, though, which can't be solved without adding some new special function annotation.)
This depends on WebAssembly/binaryen#2218 for tests to pass.
cc @Keno @caiiiycuk @gabrielcuvillier - if you're curious to try this out, let me know how it goes!