Closed Bug 595073 Opened 14 years ago Closed 14 years ago

dont set rval on hot call/return paths

Categories

(Core :: JavaScript Engine, defect)

Product:
Core
Component:
JavaScript Engine
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED DUPLICATE of bug 593882

People

(Reporter: luke, Unassigned)

References

Details

Bug 469713 does a lot of different things to speedup the call/return path.  One of the them is to avoid storing to JSStackFrame::rval on the call path and to avoid loading from it on the return path.  This bug is for pulling out and landing that part of the patch.  It looks like most of what we need is in the patch, but additionally:
 - a JSOP_STOP in a function does not need to load rval: (function(){})() == undefined, so we can write immediates to the return reg.
 - a bit of careful rval-coordination is necessary when returning from the JM-TM bridge to JM on a JSOP_RETURN.
Oops, I meant bug 587707.
Blocks: 557378
nm, fixed in original bug!
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.