Adam Klein 9b51273278 Remove "calls eval" bit from ParseInfo and PreParseData ... There's no reason to keep track, for a preparsed function itself, whether that function calls eval. All that matters is that the ancestor scopes are marked as having an inner scope which calls eval. The function will have its "calls eval" bit persisted if/when it's fully parsed. The only "behavioral" change in this patch is the removal of a DCHECK. Bug: v8:6092 Change-Id: I17e396c8a265030fe0ad941707e4a97972e6650b Reviewed-on: https://chromium-review.googlesource.com/481223 Commit-Queue: Adam Klein <adamk@chromium.org> Reviewed-by: Marja Hölttä <marja@chromium.org> Cr-Commit-Position: refs/heads/master@{#44732}		2017-04-19 19:45:45 +00:00
..
compiler-dispatcher-job-unittest.cc	Remove "calls eval" bit from ParseInfo and PreParseData	2017-04-19 19:45:45 +00:00
compiler-dispatcher-tracer-unittest.cc	Use idle time to make progress on scheduled compilation jobs	2016-12-16 14:40:32 +00:00
compiler-dispatcher-unittest.cc	Remove "calls eval" bit from ParseInfo and PreParseData	2017-04-19 19:45:45 +00:00
optimizing-compile-dispatcher-unittest.cc	[parser] Move newly added cctest/test-parsing/LazyFunctionLength to unittests.	2017-04-18 14:27:32 +00:00