-
Notifications
You must be signed in to change notification settings - Fork 5k
[browser] remove EXPORT_EXCEPTION_HANDLING_HELPERS #111033
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
[browser] remove EXPORT_EXCEPTION_HANDLING_HELPERS #111033
Conversation
Why are they unused? These were needed to fix an exception handling issue in the jiterpreter before. |
Our code never references |
Maybe this is about |
05bd6be
to
e572991
Compare
IIRC most scenarios this covers will be exercised by https://github.com/dotnet/runtime/tree/main/src/mono/sample/wasm/browser-shutdown but there were some (JS exception handling on targets without WASM EH) that require manual testing with explicit browser flags or something. On the other hand WASM EH has been available for so long that maybe we can stop caring about JS emulation... |
Thanks, I tested it and it's working fine. The scenario I was worried about is jiterp, but I was also able to confirm it now.
Created #112686 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
get rid of un-used
getExceptionMessage
->__cxa_demangle
->itanium_demangle
Fixes #110861