Fix issue 86 by keeping track of the fact that finally blocks
authorkasperl@chromium.org <kasperl@chromium.org@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Wed, 1 Oct 2008 07:43:00 +0000 (07:43 +0000)
committerkasperl@chromium.org <kasperl@chromium.org@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Wed, 1 Oct 2008 07:43:00 +0000 (07:43 +0000)
commit016fcd4affaca553ac3378edf4b7868bd79c9867
treee51290d1de561802d94e334af689ee3e22a643f7
parent3916eb38f46a1aa1c9d165a3784361fb9eb67c42
Fix issue 86 by keeping track of the fact that finally blocks
are evaluated with an extra element on the stack, which needs
to be taken into account when breaking and continuing.

I'll clean up the code and add an abstraction for manipulating
the break stack height in a future CL -- I want to try to get
rid of the separate local variable we keep around for the "state"
when running in a finally block.
Review URL: http://codereview.chromium.org/5625

git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@400 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
src/codegen-arm.cc
src/codegen-ia32.cc
test/mjsunit/regress/regress-86.js [moved from test/mjsunit/bugs/bug-86.js with 94% similarity]