Closed Bug 816661 Opened 12 years ago Closed 5 years ago

BaselineCompiler: Optimize ARM-specific codegen

Categories

(Core :: JavaScript Engine, defect)

defect
Not set
normal

Tracking

()

RESOLVED WONTFIX

People

(Reporter: jandem, Unassigned)

References

Details

Our ARM-specific code should be optimized to have less x86-isms. For instance, we could use a 3-operand add instead of a move + 2-operand add.

Seems best to do this after the code has stabilized a bit more though.
For PowerPC Baseline Compiler, I'm also rewriting some of the guard code. It's not very efficient for CPUs that pay a higher branch penalty. Some of this could be beneficial to ARM as well (e.g., instead of two branchTestInt32s, you could have load temp,JSVAL_INT_32; xor scratch1,R0.typeReg,temp; xor scratch2,R1.typeReg,temp; or temp,scratch1,scratch2; branch(NonZero, failure) -- this gets a branch out of the fastpath and replaces it with fast integer unit work).
Assignee: general → nobody

Closing this as wontfix. Codegen is a whole separate thing to discuss.

Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Resolution: FIXED → WONTFIX
You need to log in before you can comment on or make changes to this bug.