-
Couldn't load subscription status.
- Fork 819
[emscripten] Enable WASM_BIGINT by default #7984
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?
Conversation
2484a29 to
b84c9bd
Compare
834c3bd to
aa256bb
Compare
|
Hm.. it looks like more work is requires to make the binaryen API bigint friendly. @kripken did you take a look at this in the past? |
|
Hmm, no, I don't recall doing that. More generally, my hope is we can move binaryen.js to embind so stuff like this is handled automatically. |
It seems like there are places where the API uses 64-bit stuff and is not expecting it to simply use bigints |
2a689a6 to
991158b
Compare
This flag has been enabled by default in emscripten for a while now so I don't think we need this here anymore. The main user-visible effect of this change is that it makes the `module.i64.const` JS method now simply take a single bigint rather than a pair numbers.
|
I decided to look into the changes needed to the JS API.. WDYT? |
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.
Changes make sense to me, but they are breaking, so please update the changelog.
This flag has been enabled by default in emscripten for a while now so I don't think we need this here anymore.
Also remove the
-Wno-experimentalflag which is no longer needed for-sMEMORY64.Also remove
-sMODULARIZEwhich is implied by-sEXPORT_ES6.