Skip to content

Update CHANGELOG.md after #7984. NFC #8339

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.

Sign up for GitHub

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

Merged
sbc100 merged 1 commit into from
Feb 18, 2026
+9 −4
Merged

Update CHANGELOG.md after #7984. NFC #8339

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 9 additions & 4 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,10 +15,15 @@ full changeset diff at the end of each section.
Current Trunk
-------------
- The emscripten build of binaryen no longer targets pure JS (via wasm2js) by
default. In the long run this will allow us to enable WASM_BIGINT and other
features that wasm2js does not support. There is now just a single
binaryen_js target. It should still be possible to inject `-sWASM=0` as a
linker flag but this is not officially supported. (#7995)
default. This allows us to enable WASM_BIGINT and other features that
wasm2js does not support. There is now just a single binaryen_js target. It
should still be possible to inject `-sWASM=0` as a linker flag but this is
not officially supported. (#7995)
- As part of enabling the `WASM_BIGINT` in the emscripten build the JS API for
manipulating 64-bit values was changed. These APIs, such as `i64.const`
and `setValueI64`, previously took a hi/low pair but now take a single value
which can be bigint or a number. Passing two values to these APIs will now
trigger an assertion. (#7984)

v126
----
Expand Down
Loading