Closed Bug 450334 Opened 16 years ago Closed 16 years ago

TM: TraceRecorder::forInLoop out of synch with js_Interpret

Categories

(Core :: JavaScript Engine, defect)

defect
Not set
normal

Tracking

()

RESOLVED FIXED
mozilla1.9.1a2

People

(Reporter: brendan, Assigned: brendan)

Details

The interpreter will find an exhausted enumerator and if its current object has a prototype, go up the proto chain in the very same cycle, possibly finding more enumerable properties. The recorder thinks an exhausted enumerator terminates the for-in loop. Testcase and fix later tonight.

/be
Fixed:

http://hg.mozilla.org/tracemonkey/index.cgi/rev/4300413499aa

Please help verify -- thanks. New probs in new bugs.

/be
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
brendan: any reason for me not to repurpose js/src/trace-test.js into a normal test in js1_8_1 somewhere?
We're gonna keep evolving trace-test, so you could snapshot it and update -- the additions should be at the end. But it's a big multi-test. Maybe track it via snapshotting for now?

/be
Checking in trace/trace-test.js;
/cvsroot/mozilla/js/tests/js1_8_1/trace/trace-test.js,v  <--  trace-test.js
initial revision: 1.1

mozilla-central: changeset:   16647:78629658ffcd
Flags: in-testsuite+
Flags: in-litmus-
You need to log in before you can comment on or make changes to this bug.