Open Bug 586232 Opened 15 years ago Updated 1 years ago

IonMonkey: Investigate an optimal solution for branchTruncateDoubleToInt32 for ARM.

Categories

(Core :: JavaScript Engine, enhancement, P3)

ARM
All
enhancement

Tracking

()

People

(Reporter: jbramley, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: [js:t])

Refer to bug 585918 for a short discussion. In jsnum.h's DoubleToECMAInt32 function, a decent performance improvement could be gained by using a soft-float routine to cover all the corner-cases of ECMA's "ToInt32" function. (VFP can't do the whole operation by itself.) branchTruncateDoubleToInt32 might behave differently. Bug 585918 added a VFP-based conversion routine which falls back to a slow path in case of overflow, but this might not be the best solution.
Depends on: 585918
Still relevant for IM?
Flags: needinfo?(mrosenberg)
IM still needs to convert doubles to int32s. I suspect we call into the interpreter a lot less, but it still happens. Also, I have spent about 0 time optimizing the IM code that is generated for these operations. I'm sure we can get a small gain by actually getting that code closer to optimal.
Flags: needinfo?(mrosenberg)
Ok, thanks for the info. Updating description and resetting assignee. @jbramley, please don't let that keep you from working on this, of course. ;)
Assignee: Jacob.Bramley → general
Status: ASSIGNED → NEW
OS: Linux → All
Whiteboard: [js:t]
Summary: JM: Investigate an optimal solution for branchTruncateDoubleToInt32 for ARM. → IonMonkey: Investigate an optimal solution for branchTruncateDoubleToInt32 for ARM.
Assignee: general → nobody
Severity: normal → S3

Appears we're still pretty much using the implementation from bug 585918

Blocks: 1729507
Priority: -- → P4
Severity: S3 → N/A
Priority: P4 → P3
You need to log in before you can comment on or make changes to this bug.