Closed
Bug 1819351
Opened 1 year ago
Closed 1 year ago
Fix wasm command line parsing for wasm features following bug 1818516
Categories
(Core :: JavaScript Engine, defect, P1)
Core
JavaScript Engine
Tracking
()
RESOLVED
FIXED
112 Branch
| Tracking | Status | |
|---|---|---|
| firefox-esr102 | --- | unaffected |
| firefox110 | --- | unaffected |
| firefox111 | --- | unaffected |
| firefox112 | --- | fixed |
People
(Reporter: jseward, Assigned: jseward)
References
(Blocks 1 open bug, Regression)
Details
(Keywords: regression)
Attachments
(1 file)
It seems that bug 1818516 causes at least --wasm-gc to be ignored, and
possibly other --wasm-<feature> flags too. It may be that the relevant flags
are not handed to JS::ContextOptionsRef(cx).setXYZ(..).
|
||
Comment 1•1 year ago
|
||
Set release status flags based on info from the regressing bug 1818516
status-firefox110:
--- → unaffected
status-firefox111:
--- → unaffected
status-firefox112:
--- → affected
status-firefox-esr102:
--- → unaffected
|
||
Updated•1 year ago
|
|
||
Comment 2•1 year ago
|
||
Pushed by rhunt@eqrion.net: https://hg.mozilla.org/integration/autoland/rev/2d7f68d0534c Fix command line parsing for wasm flags. r=rhunt
|
||
Comment 4•1 year ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
Target Milestone: --- → 112 Branch
|
||
Comment 5•1 year ago
|
||
Thanks for fixing this.
You need to log in
before you can comment on or make changes to this bug.
Description
•