TM: JIT turns (undefined) into "undefined" in this crazy testcase

RESOLVED FIXED

Status

()

Core
JavaScript Engine
RESOLVED FIXED
10 years ago
10 years ago

People

(Reporter: Jesse Ruderman, Unassigned)

Tracking

(Blocks: 1 bug, {testcase})

Trunk
x86
Mac OS X
testcase
Points:
---
Dependency tree / graph
Bug Flags:
in-testsuite +
in-litmus -

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

10 years ago
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!
(Reporter)

Updated

10 years ago
Blocks: 465479
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?
Yeah, this has to be bug 465483.

/be
Status: NEW → RESOLVED
Last Resolved: 10 years ago
Depends on: 465483
Resolution: --- → FIXED

Comment 3

10 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-
You need to log in before you can comment on or make changes to this bug.