Closed
Bug 1511429
Opened 7 years ago
Closed 6 years ago
ARM simulator disable-debug enable-optimize test failure
Categories
(Core :: JavaScript: WebAssembly, defect, P3)
Tracking
()
RESOLVED
FIXED
mozilla66
| Tracking | Status | |
|---|---|---|
| firefox66 | --- | fixed |
People
(Reporter: lth, Assigned: lth)
Details
Attachments
(1 file)
|
1.78 KB,
patch
|
lth
:
review+
|
Details | Diff | Splinter Review |
inbound 448961:91e1fe27cef9 but failed also on a pre-reformat rev.
This looks like some stack walking thing. Only fails (so far) in release builds for ARM simulator.
js/src/jit-test/lib/wasm.js:292:11 Error: no plausible stacks found, observed: /!>/0,!>/!>/
js/src/jit-test/lib/wasm.js:292:11 Expected one of:
js/src/jit-test/lib/wasm.js:292:11 /!>/0,!>//0,!>/!>/
Stack:
WasmHelpers.assertEqPreciseStacks@js/src/jit-test/lib/wasm.js:292:11
@js/src/jit-test/tests/wasm/gc/anyref-global-prebarrier.js:38:1
Config:
export CC='gcc -m32 -mfpmath=sse -msse -msse2'
export CXX='g++ -m32 -mfpmath=sse -msse -msse2'
../configure --target=i686-linux --disable-debug --enable-optimize --without-intl-api --enable-simulator=arm
Run:
../jit-test/jit_test.py -f dist/bin/js wasm/gc
Compiler:
gcc (GCC) 8.2.1 20181105 (Red Hat 8.2.1-5)
| Assignee | ||
Comment 1•6 years ago
|
||
This is because the JIT has time to kick in in some configurations and confuses the stacks. There's a fix being worked up in bug 1515917. Taking this meanwhile.
Assignee: nobody → lhansen
Status: NEW → ASSIGNED
Priority: -- → P3
| Assignee | ||
Comment 2•6 years ago
|
||
Patch. R+ from benjamin on bug 1515917.
Attachment #9035585 -
Flags: review+
Pushed by lhansen@mozilla.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/676b002d0640
Run a test only if no JS jit compilation. r=bbouvier
Comment 4•6 years ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 6 years ago
status-firefox66:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla66
You need to log in
before you can comment on or make changes to this bug.
Description
•