Closed
Bug 1128653
Opened 10 years ago
Closed 10 years ago
Make native code bounds of tracked optimization regions closed
Categories
(Core :: JavaScript Engine: JIT, defect)
Core
JavaScript Engine: JIT
Tracking
()
RESOLVED
FIXED
mozilla38
Tracking | Status | |
---|---|---|
firefox38 | --- | fixed |
People
(Reporter: shu, Unassigned)
Details
Attachments
(1 file)
4.31 KB,
patch
|
djvj
:
review+
|
Details | Diff | Splinter Review |
For two adjacent regions [i, j] and [j, k], an offset at exactly j should be associated with the first region (like it is for the JIT code map).
I forgot to fix this for the landing.
Reporter | ||
Comment 1•10 years ago
|
||
Attachment #8558290 -
Flags: review?(kvijayan)
Updated•10 years ago
|
Attachment #8558290 -
Flags: review?(kvijayan) → review+
Comment 2•10 years ago
|
||
Backed out in https://hg.mozilla.org/integration/mozilla-inbound/rev/db6d27b3a8f0 for static analysis bustage, https://treeherder.mozilla.org/logviewer.html#?job_id=6239348&repo=mozilla-inbound
Comment 3•10 years ago
|
||
Sorry had to back this out again in https://treeherder.mozilla.org/#/jobs?repo=mozilla-inbound&revision=6ae06b9d651b since one of this changes caused xpcshell test failures like https://treeherder.mozilla.org/logviewer.html#?job_id=6253683&repo=mozilla-inbound
Comment 4•10 years ago
|
||
Status: NEW → RESOLVED
Closed: 10 years ago
status-firefox38:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla38
Comment 5•10 years ago
|
||
You need to log in
before you can comment on or make changes to this bug.
Description
•