• Adam Klein's avatar
    Remove "calls eval" bit from ParseInfo and PreParseData · 9b512732
    Adam Klein authored
    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: 's avatarMarja Hölttä <marja@chromium.org>
    Cr-Commit-Position: refs/heads/master@{#44732}
    9b512732
Name
Last commit
Last update
..
benchmarks Loading commit data...
cctest Loading commit data...
common Loading commit data...
debugger Loading commit data...
fuzzer Loading commit data...
inspector Loading commit data...
intl Loading commit data...
js-perf-test Loading commit data...
memory Loading commit data...
message Loading commit data...
mjsunit Loading commit data...
mozilla Loading commit data...
preparser Loading commit data...
promises-aplus Loading commit data...
simdjs Loading commit data...
test262 Loading commit data...
unittests Loading commit data...
webkit Loading commit data...
BUILD.gn Loading commit data...
bot_default.gyp Loading commit data...
bot_default.isolate Loading commit data...
default.gyp Loading commit data...
default.isolate Loading commit data...
optimize_for_size.gyp Loading commit data...
optimize_for_size.isolate Loading commit data...
perf.gyp Loading commit data...
perf.isolate Loading commit data...