Reviewers: Vyacheslav Egorov, fschneider, Message: Everything fixed, and I noticed that it was anyway bailouting on self-referencing named function, because of VisitVariableProxy for CONST variable in CONTEXT. Do we need this bailout anymore?
And looks like my test is failing on new test: "illegall access". This is because arm platform is using Runtime::kLoadContextSlot helper with wrong arguments, and I'm not sure if reason of that fail is my patch Description: [hydrogen] don't bailout assignments to consts If constant variable is allocated in CONTEXT BUG= TEST= [email protected] Please review this at http://codereview.chromium.org/8857001/ SVN Base: gh:v8/v8@master Affected files: M src/arm/lithium-arm.h M src/arm/lithium-codegen-arm.cc M src/hydrogen-instructions.h M src/hydrogen.cc M src/ia32/lithium-codegen-ia32.cc M src/ia32/lithium-ia32.h M src/mips/lithium-codegen-mips.cc M src/mips/lithium-mips.h M src/x64/lithium-codegen-x64.cc M src/x64/lithium-x64.h A test/mjsunit/function-named-self-reference.js -- v8-dev mailing list [email protected] http://groups.google.com/group/v8-dev
