Skip to content

Add changelog entry for --zero-filled-memory / 3306 #4735

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
merged 1 commit into from
Jun 16, 2022
Merged

Add changelog entry for --zero-filled-memory / 3306 #4735

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
7 changes: 7 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -168,6 +168,13 @@ v100
v99
---

- Fix optimization behavior on assuming memory is zero-filled. We made that
assumption before, but it is incorrect in general, which caused problems.
The fixed behavior is to not assume it, but require the user to pass it in as
a flag, `--zero-filled-memory`. Large binaries with lots of empty bytes in the
data section may regress without that flag. Toolchains like Emscripten can
pass the flag automatically for users if they know it is right to assume,
which can avoid any regressions. (#3306)
- `RefFunc` C and JS API constructors (`BinaryenRefFunc` and `ref.func`
respectively) now take an extra `type` parameter, similar to `RefNull`. This
is necessary for typed function references support.
Expand Down