-
Notifications
You must be signed in to change notification settings - Fork 3.5k
Fix bulk memory feature removal in optimizing builds #25719
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
Conversation
|
Depends on #25718 |
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.
Nice work!
f285fef to
2dd506a
Compare
|
Rebased |
| self.emcc('hello_world.c', ['-O3', '-o', 'bulk.js']) | ||
| self.assertTrue(has_data_count('bulk.wasm')) | ||
|
|
||
| self.emcc('hello_world.c', ['-O3', '-o', 'nobulk.js', '-mno-bulk-memory', '-mno-bulk-memory-opt']) |
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.
I wonder if it might make sense to test the '-mno-bulk-memory' and '-mno-bulk-memory-opt' separately?
IIUC '-mno-bulk-memory' implies '-mno-bulk-memory-opt'?
So self.emcc('hello_world.c', ['-O3', '-o', 'nobulk.js', '-mno-bulk-memory'] should not get bulk memory either?
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.
IIUC
'-mno-bulk-memory'implies'-mno-bulk-memory-opt'?
From the LLVM POV, I'm not sure it does sadly.
The bug here was the `binaryen_features` was been stashed right away after linking and then used unmodified for future binaryen calls. Fixes: emscripten-core#25479
The bug here was the BINARYEN_FEATURES was been stashed right away after linking and then used unmodified for future binaryen calls.
Fixes: #25479