Closed
Bug 523381
Opened 16 years ago
Closed 14 years ago
add un-blacklisting to jitstats
Categories
(Core :: JavaScript Engine, defect)
Core
JavaScript Engine
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: luke, Assigned: luke)
Details
Attachments
(1 file, 1 obsolete file)
|
3.73 KB,
patch
|
Details | Diff | Splinter Review |
Currently, if an outer loop is blacklisted in the course of recording an inner loop, it will be un-blacklisted when the inner loop finishes recording. The initial blacklisting is recorded in the jitstats, but not the subsequent un-blacklisting. This attached patch adds a new "unblacklisted" jitstat so that we may better interpret the behavior of the JIT.
| Assignee | ||
Comment 1•16 years ago
|
||
Also, David: should AttemptCompilation also have:
else if (*pc == JSOP_CALL && *(pc + JSOP_CALL_LENGTH) == JSOP_NOOP) {
AUDIT(unblacklisted);
*(pc + JSOP_CALL_LENGTH) = JSOP_TRACE;
}
?
| Assignee | ||
Comment 2•16 years ago
|
||
Attachment #407305 -
Attachment is obsolete: true
(In reply to comment #1)
Yes. I'm planning on a separate bug for this because right now recursion and blacklisting is messed up in a few places.
| Assignee | ||
Comment 4•14 years ago
|
||
I'm not planning to do this.
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•