Support OSR in for-in loops.

Support OSR in for-in loops.

Modify PreProcessOsrEntry to work with OSR entries that have non-empty expression stack.

Modify graph builder to take for-in state from environment instead of directly referencing emitted instructions.

Extend %OptimizeFunctionOnNextCall with an argument to force OSR to make writing OSR tests easier: %OptimizeFunctionOnNextCall(f, "osr").

R=fschneider@chromium.org
TEST=test/mjsunit/compiler/optimized-for-in.js

Committed: https://code.google.com/p/v8/source/detail?r=10796

[fschneider, 2012-02-22 15:29:59]

lgtm

https://chromiumcodereview.appspot.com/9431030/diff/1/test/mjsunit/compiler/o...
File test/mjsunit/compiler/optimized-for-in.js (right):

https://chromiumcodereview.appspot.com/9431030/diff/1/test/mjsunit/compiler/o...
test/mjsunit/compiler/optimized-for-in.js:246: // Test OSR inside for each.
s/for each/for-in/

[Vyacheslav Egorov (Chromium), 2012-02-22 16:18:04]

PTAL, I have extended OptimizeFunctionOnNextCall with an argument to force OSR
and improved coverage of OSR.

[fschneider, 2012-02-22 16:22:39]

lgtm

https://chromiumcodereview.appspot.com/9431030/diff/4001/test/mjsunit/compile...
File test/mjsunit/compiler/optimized-for-in.js (right):

https://chromiumcodereview.appspot.com/9431030/diff/4001/test/mjsunit/compile...
test/mjsunit/compiler/optimized-for-in.js:295: assertEquals("101234567",
osr_outer_and_deopt([1,2,3,4,5,6,7,8], "5"));
You could check the optimization status with %GetOptimizationStatus to assert
that the OSR succeeded.