Closed
Bug 885180
Opened 12 years ago
Closed 12 years ago
isLoopBackedge doesn't work after critical edge unsplitting
Categories
(Core :: JavaScript Engine, enhancement)
Core
JavaScript Engine
Tracking
()
RESOLVED
FIXED
mozilla24
People
(Reporter: sunfish, Unassigned)
Details
Attachments
(1 file)
|
1.77 KB,
patch
|
bhackett1024
:
review+
|
Details | Diff | Splinter Review |
After the fix for bug 881412, debugging/printing routines which call isLoopBackedge don't work, because its assertions assume that critical edges are split.
| Reporter | ||
Comment 1•12 years ago
|
||
Attachment #765173 -
Flags: review?(bhackett1024)
Comment 2•12 years ago
|
||
Comment on attachment 765173 [details] [diff] [review]
a proposed fix
Review of attachment 765173 [details] [diff] [review]:
-----------------------------------------------------------------
::: js/src/ion/MIRGraph.h
@@ +312,5 @@
> return kind_ == LOOP_HEADER;
> }
> + bool hasUniqueBackedge() const {
> + JS_ASSERT(isLoopHeader());
> + return numPredecessors() == 2;
Could this assert numPredecessors() >= 2? I think the numPredecessors() == 1 bit in the assertion you removed is antiquated, and now that we prune dead code from the graph it should (at least after that pass) be the case there are at least two predecessors.
Attachment #765173 -
Flags: review?(bhackett1024) → review+
| Reporter | ||
Comment 3•12 years ago
|
||
I added numPredecessors() >= 2 as you suggested.
https://hg.mozilla.org/integration/mozilla-inbound/rev/f7c30b1d5c35
Comment 4•12 years ago
|
||
Status: UNCONFIRMED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla24
You need to log in
before you can comment on or make changes to this bug.
Description
•