Closed
Bug 463258
Opened 17 years ago
Closed 14 years ago
Simplify guard record at LIR_loop
Categories
(Core :: JavaScript Engine, enhancement)
Core
JavaScript Engine
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: dmandelin, Unassigned)
References
Details
Given that LIR_loop does not in fact exit, it seems that a guard record and side exit are unnecessary. Ideally, can we eliminate the need for them entirely? Or, failing that, a simple API that will insert the minimal data and close the loop?
Comment 1•17 years ago
|
||
LIR_loop exits now, conditionally; depends if its hot-patched by a timeout handler. But a side exit gets generated, and is used.
Comment 2•17 years ago
|
||
LIR_loop has to be a guard for 2 reasons, one is the StackFilter (need the start state for the stack water-level analysis) and the other one is timeout handling. We can remove a lot of the SideExit state though and provide a SideExit base class and optional and separate extensions for the tracer and regexp.
| Reporter | ||
Comment 3•17 years ago
|
||
Hmm. I guess the hot-patching mechanism should behave identically on regexp native code loops to how it does for TM loops.
Updated•17 years ago
|
Severity: normal → enhancement
Comment 4•14 years ago
|
||
Obsolete with the removal of tracejit.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•