Closed
Bug 887544
Opened 11 years ago
Closed 11 years ago
Differential Testing: Different output message w/without --no-baseline involving eval
Categories
(Core :: JavaScript Engine, defect)
Tracking
()
RESOLVED
FIXED
Tracking | Status | |
---|---|---|
firefox22 | --- | unaffected |
firefox23 | --- | fixed |
firefox24 | --- | unaffected |
firefox25 | --- | unaffected |
People
(Reporter: gkw, Assigned: jandem)
References
Details
(Keywords: testcase)
Attachments
(1 file)
930 bytes,
patch
|
jandem
:
review+
bajaj
:
approval-mozilla-beta+
|
Details | Diff | Splinter Review |
print(eval("for(let x = 0; x < 9; ++x) { true }")) shows the following on a 64-bit deterministic threadsafe js shell on m-c rev 61c3c8b85563: undefined but shows the following with --no-baseline: true This seems to be an old bug. Setting needinfo for jandem as this may cloud other correctness bugs.
Flags: needinfo?(jdemooij)
Reporter | ||
Updated•11 years ago
|
Summary: Differential Testing: Different error message w/without --no-baseline involving eval → Differential Testing: Different output message w/without --no-baseline involving eval
Assignee | ||
Comment 2•11 years ago
|
||
Nice catch, when we OSR from the interpreter into baseline we did not copy the frame's return value. I fixed this in bug 866878, but didn't know it was also observable without try-finally. That means we only have to fix this on beta.
status-firefox22:
--- → unaffected
status-firefox23:
--- → affected
status-firefox24:
--- → unaffected
status-firefox25:
--- → unaffected
Assignee | ||
Comment 3•11 years ago
|
||
This is from the patch I landed for bug 866878, so setting r+
Assignee: general → jdemooij
Status: NEW → ASSIGNED
Attachment #768258 -
Flags: review+
Flags: needinfo?(jdemooij)
Assignee | ||
Comment 4•11 years ago
|
||
Comment on attachment 768258 [details] [diff] [review] Patch for beta [Approval Request Comment] > Bug caused by (feature/regressing bug #): Baseline compiler (23) > User impact if declined: Correctness bugs > Testing completed (on m-c, etc.): On m-c and aurora for a while > Risk to taking this patch (and alternatives if risky): Very low risk. > String or IDL/UUID changes made by this patch: None
Attachment #768258 -
Flags: approval-mozilla-beta?
Reporter | ||
Comment 5•11 years ago
|
||
> That means we only have to fix this on beta.
I'm not sure if this is entirely correct. I had reproduced the issue on m-c rev 61c3c8b85563, which means aurora and m-c are affected.
Flags: needinfo?(jdemooij)
Assignee | ||
Comment 6•11 years ago
|
||
(In reply to Gary Kwong [:gkw] [:nth10sd] from comment #5) > I'm not sure if this is entirely correct. I had reproduced the issue on m-c > rev 61c3c8b85563, which means aurora and m-c are affected. Rev 61c3c8b85563 is from June 21, bug 866878 landed June 22.
Flags: needinfo?(jdemooij)
Reporter | ||
Comment 7•11 years ago
|
||
> Rev 61c3c8b85563 is from June 21, bug 866878 landed June 22.
d'oh! You're right, then. :)
Comment 8•11 years ago
|
||
Comment on attachment 768258 [details] [diff] [review] Patch for beta Low risk, looks ok to land on beta since we still have a few more to go.
Attachment #768258 -
Flags: approval-mozilla-beta? → approval-mozilla-beta+
Reporter | ||
Updated•11 years ago
|
Keywords: checkin-needed
Assignee | ||
Comment 9•11 years ago
|
||
https://hg.mozilla.org/releases/mozilla-beta/rev/c4e9afa543f1
You need to log in
before you can comment on or make changes to this bug.
Description
•