Don't preparse large files to find boundaries of lazy functions.
authorlrn@chromium.org <lrn@chromium.org@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Fri, 25 Nov 2011 09:36:31 +0000 (09:36 +0000)
committerlrn@chromium.org <lrn@chromium.org@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Fri, 25 Nov 2011 09:36:31 +0000 (09:36 +0000)
commitebccde15bce879a18381fa34b61b65af4f624185
treeb0c9ae9cd6e04dbd6742d3d20c13a2f7c108b5a8
parent50e5aaa73fc15257e7cb222794d7e6f147eb1061
Don't preparse large files to find boundaries of lazy functions.

Instead use the preparser inline to parse only the lazy function
bodies.

This is still disabled for small files.
More measurements are needed to determine if lazy-compiling small
sources is worth it.

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

git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@10066 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
src/compiler.cc
src/hydrogen.cc
src/liveedit.cc
src/parser.cc
src/parser.h
src/preparser.cc
src/preparser.h
src/scanner.h
test/cctest/test-parsing.cc
test/mjsunit/regress/regress-1110.js