Enable JIT exit for JS PI
Categories
(Core :: JavaScript: WebAssembly, task, P2)
Tracking
()
Tracking | Status | |
---|---|---|
firefox130 | --- | fixed |
People
(Reporter: yury, Assigned: yury)
References
(Blocks 1 open bug)
Details
Attachments
(2 files)
Currently, when Wasm JS Promise Integration is enabled, the JIT exit optimization is disabled. The main issue that we need to track if execution is happening on the main (not suspendable) stack, and switch stacks otherwise.
Updated•1 year ago
|
Assignee | ||
Updated•1 year ago
|
Comment 1•1 year ago
|
||
I think we'll need to expand our JIT exit code so that performs an optional stack switch to the main stack. It'd be nice if the masm/stubs code we add for this was general enough that we could re-use it for our interpreter exit code too. This would let us have remove the inline assembly and solve bug 1894759. I'm a little worried that inline assembly is going to be hard to maintain, as it requires us to duplicate a lot of logic that we already have in masm.
Assignee | ||
Comment 2•1 year ago
|
||
Updated•1 year ago
|
Assignee | ||
Comment 3•1 year ago
|
||
Avoids collision of two different js::jit::AssemblerBuffer's.
Comment 5•1 year ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/309324abbc48
https://hg.mozilla.org/mozilla-central/rev/fe319ced93e9
Description
•