On ia32 LFunctionLiteral instruction should get context from esi register instead...
authorvegorov@chromium.org <vegorov@chromium.org@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Tue, 21 Feb 2012 12:10:04 +0000 (12:10 +0000)
committervegorov@chromium.org <vegorov@chromium.org@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Tue, 21 Feb 2012 12:10:04 +0000 (12:10 +0000)
commitf5c8ac9839bc77b8e1e9d89492c53b16229a1286
treefdb0946247f38c1f401505cd51cddf6d9243656e
parent54bd4e9a76606d3a95be34fea7c518592df008c0
On ia32 LFunctionLiteral instruction should get context from esi register instead of stack slot.

This makes LFunctionLiteral safe even when it is used from inside inlined function.

All other architectures were implementing LFunctionLiteral correctly.

R=mstarzinger@chromium.org
TEST=test/mjsunit/regress/regress-inlining-function-literal-context.js

Review URL: https://chromiumcodereview.appspot.com/9425061

git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@10778 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
src/ia32/lithium-codegen-ia32.cc
test/mjsunit/regress/regress-inlining-function-literal-context.js [new file with mode: 0644]