Closed
Bug 713957
Opened 13 years ago
Closed 12 years ago
JS Correctness: Different output without -m and with -m
Categories
(Core :: JavaScript Engine, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: gkw, Unassigned)
Details
(Keywords: regression, testcase, Whiteboard: js-triage-needed)
try { options('strict') } catch (e) {} try { (function() { (eval("((function f(){\ (eval(\"(\\\"\\\"[[]])\",\"\"));\ if(z=1)return f()})())", newGlobal('same-compartment'))) })() } catch (e) {} Compiled with --enable-more-deterministic, on js opt shell on m-c changeset 7e28cce342a6, shows (with -m) an extra error: typein:6: strict warning: reference to undefined property ""[[]] but does not show without -m, before the "js_ReportOverRecursed called" message is displayed. I'm not sure if this is intended behaviour, and autoBisect is probably wrong. autoBisect shows this is probably related to the following changeset: The first bad revision is: changeset: 63096:6e2ee1f3f6c6 user: Brendan Eich date: Wed Feb 23 19:38:27 2011 -0800 summary: Followup fixes and tests in wake of global |this| binding change (636364, r=luke/gal/dvander, thanks to Waldo for the newGlobal shell function).
Reporter | ||
Updated•13 years ago
|
Severity: critical → normal
Comment 1•12 years ago
|
||
WFM. The first good revision is: changeset: d90e0b3a8bb9 user: Shu-yu Guo date: Fri Jul 22 12:47:16 2011 -0700 summary: [INFER] Fix bug in previous fix for bug 673341. r=bhackett I'm not sure this was a bug either. I already changed compareJIT.py to ignore all differences when the "js_ReportOverRecursed called" message appears.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•