Fix a bug in abrupt exit from with or catch inside finally.
authorkmillikin@chromium.org <kmillikin@chromium.org@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Wed, 7 Sep 2011 09:21:44 +0000 (09:21 +0000)
committerkmillikin@chromium.org <kmillikin@chromium.org@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Wed, 7 Sep 2011 09:21:44 +0000 (09:21 +0000)
commit8b165d414f2ba3be7fdd2ff258f957721c8137f8
tree2be3187628e617044719c56a69511f771eac591b
parent85a5b6d3c4666dbb82140d976fe5bd969dfcd400
Fix a bug in abrupt exit from with or catch inside finally.

When with or catch is nested inside finally, we were not properly restoring
the context in the stack for the finally code.  Also, as a small
optimization, restore it from the handler block instead of iteratively
unwinding contexts.

R=fschneider@chromium.org
BUG=
TEST=

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

git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@9160 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
src/arm/full-codegen-arm.cc
src/full-codegen.cc
src/ia32/full-codegen-ia32.cc
src/mips/full-codegen-mips.cc
src/x64/full-codegen-x64.cc
test/mjsunit/regress/regress-95485.js [new file with mode: 0644]