Closed Bug 648708 Opened 13 years ago Closed 13 years ago

TI: Different output with testcase with and without -m, -a and -n

Categories

(Core :: JavaScript Engine, defect)

Product:
Core
Component:
JavaScript Engine
Platform:
x86
Linux
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED FIXED

People

(Reporter: gkw, Unassigned)

References

Details

(Keywords: regression, testcase)

Attachments

(1 file)

potential regression window
9.59 KB, text/plain
Details 
try {
    ("".x = Object.seal)
    "".x.valueOf();
    print("FOOBAR")
} catch (e) {}

prints "FOOBAR" with -m, -a and -n on JM changeset a9f916668b29, but does not print it without -m, -a and -n set. This difference in behaviour has a (not-so-small) regression window as attached.
Busted path when CALLPROP is known to push a singleton but the operand is not known to be an object.  We emitted a test to check for an object, but the sync code reflected the state *after* doing the operation itself, so that the stub call saw the singleton result of the operation rather than an undefined value, and thus didn't throw.  Should have added a test when I added this object test.

http://hg.mozilla.org/projects/jaegermonkey/rev/5469f5d077ac
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.