Closed
Bug 1064540
Opened 10 years ago
Closed 6 years ago
Optimize SIMD code generation in the JIT compilers
Categories
(Core :: JavaScript Engine: JIT, defect, P5)
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: evilpie, Unassigned)
References
Details
IonMonkey should when possible match Odinmonkey in code quality when using SIMD.
Comment 1•10 years ago
|
||
Is anyone taking this?
/be
Comment 2•10 years ago
|
||
(In reply to Brendan Eich [:brendan] from comment #1)
> Is anyone taking this?
>
> /be
My plan is to work on this once full support has been added in OdinMonkey / asm.js, meaning all operations which are in the polyfill and in the interpreter should also be implemented in Odin, at least. As the compilation backend is shared by Odin and Ion, this should probably help and makes sense in my head. Some of the Ion work already has been done in bug 947711, fwiw (maybe we should dup?), but the patches probably bitrotted and can't be applied anymore now.
Thinking about it, adding support for the SIMD operations can be done in parallel with adding (partial) JIT support. What should be needed:
- Support for ARM:
- generalize regalloc to handle aliased registers, see bug 1052384
- implement backend for ARM
- Make sure to align the stack pointer at all times (funny times ahead).
- Support for bailouts and so on.
- Probably other things I am not really aware of, like TI and IonBuilder.
Comment 3•10 years ago
|
||
We prioritized Odin and x86 to make the IDC14 demo deadline. The team will divy the IonMonkey and ARM work over the next few releases. My goal is to have equality in JS with Asm before end of year and keep up with spec changes from there.
Updated•8 years ago
|
Priority: -- → P5
Comment 4•6 years ago
|
||
Repurposing this bug after the removal of SIMD.js.
Summary: Optimize SIMD in IonMonkey → Optimize SIMD code generation in the JIT compilers
Updated•6 years ago
|
Updated•6 years ago
|
Updated•6 years ago
|
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•