Enable WebAssembly JS-PI in Nightly
Categories
(Core :: JavaScript: WebAssembly, enhancement, P3)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox152 | --- | fixed |
People
(Reporter: rhunt, Assigned: rhunt)
References
(Blocks 1 open bug)
Details
(Keywords: dev-doc-complete)
Crash Data
Attachments
(3 files)
Tracking bug for flipping on JS-PI in Nightly.
| Assignee | ||
Updated•4 months ago
|
Updated•2 months ago
|
Comment 1•2 months ago
|
||
Once it's enabled, it should probably be added to https://developer.mozilla.org/en-US/docs/Mozilla/Firefox/Experimental_features and be mentioned in the Nightly release notes.
Sebastian
| Assignee | ||
Comment 2•1 month ago
|
||
- Extend getBuildConfiguration to report what's compiled in the binary.
- Ensure we're feature testing everything that's compiled in.
- Move to directiveless so we can assume no experimental flags were added
by a jit-test directive. - Normalize the relaxedSIMD name to simplify the test.
Updated•1 month ago
|
| Assignee | ||
Comment 3•1 month ago
|
||
Don't force enable stack-switching when we enable JS-PI, instead
only enable it for the builtin modules that JS-PI internally uses.
Backed out for causing mochitest failures at test_worker_interfaces.html
Backout link
Push with failures
Failure log(s)
| Assignee | ||
Updated•1 month ago
|
Comment 8•1 month ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/52c9919cbbef
https://hg.mozilla.org/mozilla-central/rev/d04dd7575cde
Comment 9•1 month ago
|
||
This causes wasm crashes such as bp-2dc78c16-94c6-414c-a153-8d5f90260506. Code sheriffs will revert the changes to resolve the issue with the next Nightly.
Comment 10•1 month ago
|
||
Comment 11•1 month ago
|
||
Reverted this as requested by @aryx for causing wasm crashes.
| Assignee | ||
Comment 12•1 month ago
|
||
Looks like that website was feature-detecting JS-PI and started running it in Nightly once it was enabled.
Their code ran into a bug in the wasm bytecode we internally emit, which was caught by our validator and turned into a crash. I have a fix to handle it. I verified that website no longer crashes.
| Assignee | ||
Comment 13•1 month ago
|
||
Comment 14•1 month ago
|
||
Comment 15•1 month ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/231be873b268
https://hg.mozilla.org/mozilla-central/rev/95cf8946e2e4
https://hg.mozilla.org/mozilla-central/rev/4805c9f7f6f0
Updated•1 month ago
|
Comment 16•1 month ago
|
||
Is this something you wanted to call out in the Nightly release notes? Please add a relnote-firefox? nomination to the bug if yes.
| Assignee | ||
Comment 17•1 month ago
|
||
Yes this is worth calling out in Nightly release notes (didn't know we had had Nightly only release notes). I was planning on the main release notes when we let it ride the trains (either this release or next).
Release Note Request (optional, but appreciated)
[Why is this notable]: New WebAssembly feature the helps porting applications to the Web.
[Affects Firefox for Android]: Yes
[Suggested wording]: Enabled the WebAssembly JS-Promise-Integration proposal in Nightly.
[Links (documentation, blog post, etc)]: https://github.com/WebAssembly/js-promise-integration/blob/main/proposals/js-promise-integration/Overview.md
Comment 18•1 month ago
|
||
Added to the Fx152 nightly release notes, please allow 30 minutes for the site to update.
The nightly-only note will be removed after three cycles or when it is enabled by default, whichever comes earlier.
Updated•1 month ago
|
| Assignee | ||
Updated•20 days ago
|
Updated•11 days ago
|
Comment 19•4 days ago
|
||
Docs for 152: We've just added a release note for now.
We are documenting the feature properly for 153, with docs work being tracked in https://github.com/mdn/content/issues/44468 / https://bugzilla.mozilla.org/show_bug.cgi?id=2044809
Description
•