Unship asm.js
Categories
(Core :: JavaScript: WebAssembly, task, P3)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox148 | --- | fixed |
People
(Reporter: rhunt, Assigned: rhunt)
References
(Blocks 1 open bug)
Details
Attachments
(5 files)
Placeholder bug for unshipping the asm.js optimizing pipeline. This would disable asm.js specific optimizations, while still keeping asm.js working using the existing JS JITs.
| Assignee | ||
Comment 1•3 months ago
|
||
This reverts commit b1053297d5300a282d868a638d12dafabb54cf3b.
| Assignee | ||
Comment 2•3 months ago
|
||
This reverts commit 90af3b6a63d9035d59e2f818bdd2fdc2ab84f6fa.
| Assignee | ||
Comment 3•3 months ago
|
||
Right now we only warn if we successfully compile the asm.js code. Once
we have disabled asm.js optimizations, it would still be good to warn
users that they should migrate to wasm.
| Assignee | ||
Comment 4•3 months ago
|
||
The shell uses a different --no-asmjs flag, and will continue to have asm.js
enabled for testing purposes.
Updated•3 months ago
|
Updated•3 months ago
|
Updated•3 months ago
|
Updated•3 months ago
|
Backed out for causing dt failures
| Assignee | ||
Comment 8•3 months ago
|
||
A devtools test assumes asm.js is enabled. We can workaround it by enabling the pref for that test.
| Assignee | ||
Comment 9•3 months ago
|
||
asm.js is disabled by default now, re-enable it for this test
that requires it to be enabled. Once we remove support for
asm.js we can remove the test.
Comment 10•3 months ago
|
||
Comment 11•3 months ago
|
||
Comment 12•3 months ago
|
||
Comment 13•3 months ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/4fc6d76b52a7
https://hg.mozilla.org/mozilla-central/rev/d3e84da3b331
https://hg.mozilla.org/mozilla-central/rev/54b838317726
https://hg.mozilla.org/mozilla-central/rev/b3577ce67aec
https://hg.mozilla.org/mozilla-central/rev/0c56dd09060d
Comment 14•3 months ago
|
||
expected 30% regression on Octane-zlib
Updated•2 months ago
|
Description
•