Closed Bug 1423496 Opened 7 years ago Closed 6 years ago

Wasm atomics should not use asm.js fallback for OOB

Categories

(Core :: JavaScript Engine: JIT, defect, P3)

Product:
Core
Component:
JavaScript Engine: JIT
Type:
defect

Tracking

()

Status:
RESOLVED DUPLICATE of bug 1481171

People

(Reporter: lth, Unassigned)

References

Details

Currently no memory access descriptors are emitted for new-style wasm atomic accesses, so if they reference OOB they will use the initial asm.js path in HandleMemoryAccess() in WasmSignalHandlers.cpp, triggering a Wasm interrupt and a call to generic OOB code. This will cause the current wasm activation to be lost; presumably that will in turn result in poor error messages / debuggability. It's desirable to clean this up, and use the same trapOutOfLine path as other wasm accesses.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.