Closed Bug 457778 Opened 17 years ago Closed 17 years ago

TM: "Assertion failed: cond->isCond()" with "if(undefined < false)"

Categories

(Core :: JavaScript Engine, defect, P1)

x86
macOS
defect

Tracking

()

VERIFIED FIXED
mozilla1.9.1b2

People

(Reporter: jruderman, Assigned: gal)

Details

(Keywords: assertion, testcase)

Attachments

(1 file)

$ ./js -j js> for (var j = 0; j < 4; ++j) { if (undefined < false) { } } Assertion failed: cond->isCond() (nanojit/Assembler.cpp:1228)
Summary: "Assertion failed: cond->isCond()" with "if(undefined < false)" → TM: "Assertion failed: cond->isCond()" with "if(undefined < false)"
Assignee: general → gal
Flags: blocking1.9.1?
Priority: -- → P1
Target Milestone: --- → mozilla1.9.1b2
Attachment #342130 - Flags: review?(danderson) → review+
From this day on forward, I shall never write a JIT again without Jesse. http://hg.mozilla.org/tracemonkey/rev/c3c2752185c3
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
this still occurs on mozilla-central. when will tm by synced with mc?
/cvsroot/mozilla/js/tests/js1_5/Regress/regress-457778.js,v <-- regress-457778.js initial revision: 1.1 http://hg.mozilla.org/mozilla-central/rev/b04c04268a94
Flags: in-testsuite+
Flags: in-litmus-
Flags: blocking1.9.1?
v 1.9.1 mozilla-central and tracemonkey
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: