-
Notifications
You must be signed in to change notification settings - Fork 3.5k
Disable assertions in tsgen #25780
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
base: main
Are you sure you want to change the base?
Disable assertions in tsgen #25780
Conversation
When using tsgen with -sASYNCIFY=1 and assertions enabled, an assertion failure occurs: `Assertion failed: missing Wasm export: asyncify_start_unwind`. This is due to emscripten-core#25541. This change disables assertions when running tsgen to resolve the issue.
sbc100
left a comment
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.
@brendandahl do you know why this is needed?
Can you add a tsgen test that covers this case?
| settings.MEMORY64 = 2 | ||
| # Source maps haven't been generated yet and aren't needed to run embind_gen. | ||
| settings.LOAD_SOURCE_MAP = 0 | ||
| settings.ASSERTIONS = 0 |
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.
Maybe add a comment here as to why this is needed?
We run tsgen before the wasm-opt asyncify pass so the asyncify functions haven't been created yet. |
|
Yeah, basically the wasm isn't fully generated yet... disabling assertions fixes asserts that expect those contents, but I wonder if we might hit other issues later. If so, for Asyncify at least, we'd need to run it before tsgen somehow... |
When using `tsgen` with `-sASYNCIFY=1` and assertions enabled, an assertion failure occurs: `Assertion failed: missing Wasm export: asyncify_start_unwind`. This is due to #25541. This PR disables assertions for the `_asyncify_<x>` exports when running `tsgen` to resolve the issue. Continuation of #25780 --------- Co-authored-by: stephenduong1004 <[email protected]> Co-authored-by: Alon Zakai <[email protected]>
When using
tsgenwith-sASYNCIFY=1and assertions enabled, an assertion failure occurs:Assertion failed: missing Wasm export: asyncify_start_unwind. This is due to #25541.This PR disables assertions when running
tsgento resolve the issue.