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

Status: RESOLVED FIXED

(Core :: JavaScript Engine, defect)

Description

[Jesse Ruderman]

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!

Comment 1

[David Anderson [:dvander] - inactive, e-mail if emergency]

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

[Brendan Eich [:brendan]]

Yeah, this has to be bug 465483.

/be

Comment 3

[Bob Clary [:bc] (inactive)]

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

Comment 4

[Shawn Wilsher :sdwilsh]

http://hg.mozilla.org/mozilla-central/rev/3758ef13c6f0