Fix Wasm jit-tests expecting specific non-canonical NaN values
Categories
(Core :: JavaScript: WebAssembly, task, P3)
Tracking
()
Tracking | Status | |
---|---|---|
firefox81 | --- | fixed |
People
(Reporter: jandem, Assigned: lth)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
On Apple ARM64 hardware we fail these two jit-tests:
These tests are checking for particular bit patterns for operations involving non-canonical NaNs. We get a different NaN value on Apple CPUs and that's fine because the Wasm spec doesn't specify all NaN bits, so we just need to fix the tests.
Assignee | ||
Updated•5 years ago
|
Assignee | ||
Comment 1•5 years ago
|
||
Candidate: https://phabricator.services.mozilla.com/D87455. Jan, can you see if that resolves the problem on the device?
Assignee | ||
Comment 2•5 years ago
|
||
These test cases expected specific payloads for some NaN results but
the wasm spec does not guarantee that, and some implementations of
some architectures will not return the same payloads as x64. So
adjust the tests.
Reporter | ||
Comment 3•5 years ago
|
||
(In reply to Lars T Hansen [:lth] from comment #1)
Candidate: https://phabricator.services.mozilla.com/D87455. Jan, can you see if that resolves the problem on the device?
It does!
% ./mach jit-test nan-semantics
[5|0|0|0] 100% ======================================================>|
PASSED ALL
% ./mach jit-test conversion.js
[5|0|0|0] 100% ======================================================>|
PASSED ALL
% ./mach jit-test
[8110| 0| 0| 0] 100% ==========================================>|
PASSED ALL
Comment 5•5 years ago
|
||
bugherder |
Description
•