-
-
Notifications
You must be signed in to change notification settings - Fork 223
RFC: Rust considering switching to using WebAssembly exception handling #1119
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
Hello, Something that would make a larger difference would be full support for |
You can try it out now with
I didn't think that workaround was good enough since code gen for the
As far as I am aware, |
Thanks. This compiles, but gives me the following error on run: Chromium:
Firefox:
The error still occurs even if I add Do you have any ideas on this? Flags used were as follows [target.wasm32-unknown-emscripten]
rustflags = [
"-C", "link-args=-sSIDE_MODULE=2",
"-Zlink-native-libraries=no",
"-Zemscripten-wasm-eh"
# "-Cllvm-args=-enable-emscripten-cxx-exceptions=0", # uncommenting doesn't help
]
The workaround very much worked for our purposes. The problem is that upstream Godot switched to Wasm exceptions, so our code compiled with old / js exceptions wouldn't even run because it would expect functions named By using your workaround, the compiled code would successfully run alongside Godot, as it wouldn't generate those calls to That is, solving unwinding panic was only secondary compared to making the code run in the first place, haha.
I just tested it and it's still aborting regardless, but I'm not using |
Rust is considering switching to using WebAssembly exception handling. See this major change proposal. We will initially leave in nightly support for opting out. How would such a change affect this project?
The text was updated successfully, but these errors were encountered: