Open Bug 777598 Opened 12 years ago Updated 2 years ago

IonMonkey: Inlined math operations should use isVolatileCall to inform the RA.

Categories

(Core :: JavaScript Engine, defect)

Product:
Core
Component:
JavaScript Engine
Type:
defect

Tracking

()

People

(Reporter: nbp, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: [ion:t])

In bug 777570 suggest to use isCall LIR property instead of saveVolatile. The problem is that saveVolatile is not aware of the allocated registers and is saving all FPU registers which end-up being costly. At the opposite isCall cause the register allocator to spill everything before the Call instruction. This bug suggest adding an isVolatileCall LIR property such as we can only spill the intersection of live and volatile registers instead of one set or the other.
Whiteboard: [js:t] → [ion:t]
Assignee: general → nobody
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.