Fix a bug in scope analysis.
authorkmillikin@chromium.org <kmillikin@chromium.org@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Tue, 2 Aug 2011 15:04:31 +0000 (15:04 +0000)
committerkmillikin@chromium.org <kmillikin@chromium.org@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Tue, 2 Aug 2011 15:04:31 +0000 (15:04 +0000)
commitf37f6e88ca24c59d1c6527c425aed2a1fb75a03c
tree70c21d655d2067308b78c6d6b90772294d411877
parentb3337196070a2af57e88753d76b9127d52d0a2d5
Fix a bug in scope analysis.

Function declarations inside catch are hoisted to the nearest enclosing
function scope, but we compiled their bodies as if occurring inside the
catch scope.

BUG=chrome:91120
TEST=regress/regress-91120 attached

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

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