Inconsistent results (f64.abs or f64.lt) on Intel vs M1 Mac
Categories
(Core :: JavaScript: WebAssembly, defect, P1)
Tracking
()
People
(Reporter: aswan, Assigned: yury)
Details
Attachments
(2 files)
1.11 KB,
text/html
|
Details | |
48 bytes,
text/x-phabricator-request
|
dmeehan
:
approval-mozilla-beta-
dmeehan
:
approval-mozilla-release+
RyanVM
:
approval-mozilla-esr91+
|
Details | Review |
See attached test case -- the page displays "OK" on an Intel-based Mac and "Error: NaN" on an M1. Also running on M1 and setting a breakpoint in the wasm and then stepping through causes the page to display "OK", which suggests a bug in native code generation on M1?
All tests were with Firefox 98.0.2.
Assignee | ||
Comment 1•3 years ago
|
||
JSOpToCondition is applicable only to integer types. JSOpToDoubleCondition and
ConditionFromDoubleCondition sequence has to be used for float types.
Updated•3 years ago
|
Comment 2•3 years ago
|
||
I assume FF98, FF99, and even FF91ESR are affected; please investigate. Uplifts would be welcome for at least 91 and 99.
Assignee | ||
Comment 3•3 years ago
|
||
Looks like bug 1710024 is prerequisite for this bug, and it is present in esr91. I will check if the patch lands cleanly with all suggested versions.
Comment 5•3 years ago
|
||
bugherder |
Assignee | ||
Comment 6•3 years ago
|
||
Comment on attachment 9269769 [details]
Bug 1761850 - Fix wasm select on ARM64. r?jseward
Beta/Release Uplift Approval Request
- User impact if declined: Some wasm application may not work properly on Aarch64 or Apple M1 hardware.
- Is this code covered by automated tests?: Yes
- Has the fix been verified in Nightly?: Yes
- Needs manual test from QE?: No
- If yes, steps to reproduce:
- List of other uplifts needed: None
- Risk to taking this patch: Low
- Why is the change risky/not risky? (and alternatives if risky): The changes only affect the code that produces the error, limited to the affected platform, and tests are provided.
- String changes made/needed:
ESR Uplift Approval Request
- If this is not a sec:{high,crit} bug, please state case for ESR consideration: Having the proper implementation of Wasm SIMD is somewhat important -- new application that use this technology are appearing on the market at this moment and could cause issues for ESRs.
- User impact if declined: Some wasm application may not work properly on Aarch64 or Apple M1 hardware.
- Fix Landed on Version: 100
- Risk to taking this patch: Low
- Why is the change risky/not risky? (and alternatives if risky): The changes only affect the code that produces the error, limited to the affected platform, and tests are provided.
Comment 7•3 years ago
|
||
Comment on attachment 9269769 [details]
Bug 1761850 - Fix wasm select on ARM64. r?jseward
This will be carried from Central to Beta with Merge Day
Comment 8•3 years ago
|
||
Comment on attachment 9269769 [details]
Bug 1761850 - Fix wasm select on ARM64. r?jseward
Important ARM64 WASM correctness fix with tests. Approved for 91.9esr.
Comment 9•3 years ago
|
||
bugherder uplift |
Comment 10•3 years ago
|
||
Comment on attachment 9269769 [details]
Bug 1761850 - Fix wasm select on ARM64. r?jseward
Approved for 99.0.1.
Comment 11•3 years ago
|
||
bugherder uplift |
Description
•