Fix lost arguments dropping in HLeaveInlined.

Fix lost arguments dropping in HLeaveInlined.

This fixes HleaveInlined to correctly drop pushed arguments on all code
paths and addresses a corner case where the arguments stack height
mismatched at an OSR entry point.

R=jkummerow@chromium.org
BUG=chromium:150545
TEST=mjsunit/regress/regress-crbug-150545

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

[Jakob Kummerow, 2012-09-19 07:51:12]

LGTM with a question.

https://chromiumcodereview.appspot.com/10938016/diff/1/test/mjsunit/regress/r...
File test/mjsunit/regress/regress-crbug-150545.js (right):

https://chromiumcodereview.appspot.com/10938016/diff/1/test/mjsunit/regress/r...
test/mjsunit/regress/regress-crbug-150545.js:46: while (--iterations > 0);
why not this:

while (%GetOptimizationStatus(outer) == 2);

That would loop exactly until the function gets optimized, and you wouldn't need
the fixed iteration count.

[Michael Starzinger, 2012-09-19 08:12:26]

Addressed comments. Landing.

https://chromiumcodereview.appspot.com/10938016/diff/1/test/mjsunit/regress/r...
File test/mjsunit/regress/regress-crbug-150545.js (right):

https://chromiumcodereview.appspot.com/10938016/diff/1/test/mjsunit/regress/r...
test/mjsunit/regress/regress-crbug-150545.js:46: while (--iterations > 0);
On 2012/09/19 07:51:12, Jakob wrote:
> why not this:
> 
> while (%GetOptimizationStatus(outer) == 2);
> 
> That would loop exactly until the function gets optimized, and you wouldn't
need
> the fixed iteration count.

Done.