Closed
Bug 465453
Opened 16 years ago
Closed 16 years ago
TM: JIT turns (undefined) into "undefined" in this crazy testcase
Categories
(Core :: JavaScript Engine, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: jruderman, Unassigned)
References
Details
(Keywords: testcase)
var out = []; for each (var e in [(new Boolean(true)), (void 0), (new Boolean(true)), (new Boolean(true)), (void 0), (void 0), "", "", (void 0)]) out.push(e); print(uneval(out)); Output with JIT on: [(new Boolean(true)), (void 0), (new Boolean(true)), (new Boolean(true)), (void 0), (void 0), "", "", "undefined"] The last undefined has turned into the string "undefined", a very different thing!
On tm tip I get: [(new Boolean(true)), (void 0), (new Boolean(true)), (new Boolean(true)), (void 0), (void 0), "", "", (void 0)] So I think this was fixed by bug 465483. Could you verify?
Comment 2•16 years ago
|
||
Yeah, this has to be bug 465483. /be
Comment 3•16 years ago
|
||
Checking in js1_8/extensions/regress-465453.js; /cvsroot/mozilla/js/tests/js1_8/extensions/regress-465453.js,v <-- regress-465453.js initial revision: 1.1 done
Flags: in-testsuite+
Flags: in-litmus-
Comment 4•16 years ago
|
||
http://hg.mozilla.org/mozilla-central/rev/3758ef13c6f0
You need to log in
before you can comment on or make changes to this bug.
Description
•