Be more discriminating about uses of the arguments object in optimized code.
authorkmillikin@chromium.org <kmillikin@chromium.org@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Mon, 2 May 2011 11:35:51 +0000 (11:35 +0000)
committerkmillikin@chromium.org <kmillikin@chromium.org@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Mon, 2 May 2011 11:35:51 +0000 (11:35 +0000)
commit1af840ad4c8fab5ad03a1fa6631b42eee42a6b4b
treeb9ce321d40a250815a617cad2724ef65185c9c2e
parent30ef211fcf30ca8deeda3667c7e1f3d61364a50b
Be more discriminating about uses of the arguments object in optimized code.

Because we track the value of the arguments object, we need to check
values whenever plugged into a forbidden value context.  It is not
enough to check at only variable references as we did previously.

R=fschneider@chromium.org
BUG=1351
TEST=regress-1351.js

Review URL: http://codereview.chromium.org/6902202

git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@7739 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
src/hydrogen.cc
src/hydrogen.h
test/mjsunit/regress/regress-1351.js [new file with mode: 0644]