Closed
Bug 636219
Opened 14 years ago
Closed 14 years ago
JM: Interpreter's useMethodJIT flag needs to be reset when entering a new function
Categories
(Core :: JavaScript Engine, defect)
Core
JavaScript Engine
Tracking
()
RESOLVED
FIXED
People
(Reporter: billm, Assigned: billm)
References
Details
(Whiteboard: fixed-in-tracemonkey)
Attachments
(1 file)
4.55 KB,
patch
|
dvander
:
review+
shaver
:
approval2.0+
|
Details | Diff | Splinter Review |
Bug 631951 introduced the useMethodJIT flag to the interpreter, which determines whether we should try to methodjit a function after enough back edges have been taken. This flag gets disabled if we try to methodjit and abort (due to code not handled by the mjit).
The problem is that this doesn't account for the fact that a single Interpret invocation can enter and exit functions many JS functions. We should be resetting the useMethodJIT flag each time. Otherwise we won't JIT enough stuff. This is causing a slowdown in bug 636096.
Assignee | ||
Comment 1•14 years ago
|
||
This patch adds a RESET_USE_METHODJIT macro that resets the flag. This macro gets called when we enter Interpret and any time we increment or decrement inlineCallCount.
Updated•14 years ago
|
Attachment #514554 -
Flags: review?(dvander) → review+
Comment 2•14 years ago
|
||
Comment on attachment 514554 [details] [diff] [review]
patch
a=shaver
Attachment #514554 -
Flags: approval2.0+
Assignee | ||
Comment 3•14 years ago
|
||
Whiteboard: fixed-in-tracemonkey
Comment 4•14 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•