Closed
Bug 1687654
Opened 4 years ago
Closed 4 years ago
Update wat to 1.0.33
Categories
(Core :: JavaScript: WebAssembly, enhancement, P3)
Core
JavaScript: WebAssembly
Tracking
()
RESOLVED
FIXED
86 Branch
Tracking | Status | |
---|---|---|
firefox86 | --- | fixed |
People
(Reporter: lth, Assigned: lth)
References
Details
Attachments
(3 files)
The newest wat version can handle many new SIMD opcodes.
Assignee | ||
Updated•4 years ago
|
Summary: Update wat/wasmparser → Update wat to 1.0.33
Assignee | ||
Comment 1•4 years ago
|
||
Some test case updates are required:
- All the
iNxM.any_true
instructions are gone;v128.any_true
is the new thing, so update a ton of tests (mostly mechanically) - An error message from the parser has changed in the multi-table case in this version (unrelated change) and needs to be fixed
Assignee | ||
Comment 2•4 years ago
|
||
Pull in a number of new SIMD opcodes, and a change from iNxM.any_true
to v128.any_true. Plus whatever else has landed in the mean time...
Assignee | ||
Comment 3•4 years ago
|
||
This is a mechanical change mostly, anything in wasm/simd/spec will
eventually disappear as we pull in the proper spec tests.
Depends on D102398
Assignee | ||
Comment 4•4 years ago
|
||
The parsing of table indices has changed a little and an error
message needs to be updated.
Depends on D102399
Pushed by lhansen@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/8864d5e2a149
Update wat to 1.0.33. r=rhunt
https://hg.mozilla.org/integration/autoland/rev/7b5f360ff686
Update SIMD tests to use only v128.any_true. r=rhunt
https://hg.mozilla.org/integration/autoland/rev/f0c9ad1ae6fe
Update an error message in the multi-table test. r=rhunt
Comment 6•4 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/8864d5e2a149
https://hg.mozilla.org/mozilla-central/rev/7b5f360ff686
https://hg.mozilla.org/mozilla-central/rev/f0c9ad1ae6fe
Status: ASSIGNED → RESOLVED
Closed: 4 years ago
status-firefox86:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 86 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•