Closed
Bug 459151
Opened 16 years ago
Closed 16 years ago
TM: non-fused ifs emit different comparison than the interpreter evaluates
Categories
(Core :: JavaScript Engine, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: gal, Unassigned)
Details
Attachments
(1 file)
|
4.95 KB,
patch
|
dvander
:
review+
|
Details | Diff | Splinter Review |
No description provided.
Attachment #342342 -
Flags: review?(danderson)
|
||
Comment 1•16 years ago
|
||
tests?
|
||
Updated•16 years ago
|
Attachment #342342 -
Flags: review?(danderson) → review+
|
Reporter | |
Comment 2•16 years ago
|
||
http://hg.mozilla.org/tracemonkey/rev/9ea000c6ffb4
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
|
|
Reporter | |
Comment 3•16 years ago
|
||
Note: this blocked the thin loop change. No extra coverage needed. Our test suite already covers all cases. This change makes cond in ifop predict correctly whether the branch will be taken or not, which we need for the thin loop handling.
|
||
Updated•16 years ago
|
Flags: in-testsuite-
Flags: in-litmus-
You need to log in
before you can comment on or make changes to this bug.
Description
•