• Georg Neis's avatar
    [compiler] Don't assume a HeapConstant context input is a Context. · 649ab060
    Georg Neis authored
    In a generator containing loops, there are always certain control flow
    paths that are impossible, due to the way we represent generators at the
    bytecode level.  Unfortunately, the graph builder can't tell that these
    paths are impossible.  In combination with dead code, it can then happen
    that we build a subgraph (for unreachable code) whose incoming context
    is the undefined oddball.  JSContextSpecialization did not expect that.
    
    Bug: chromium:794822
    Change-Id: I259be5ae6c5f5adc8fca19c64bf71285ee922b7a
    Reviewed-on: https://chromium-review.googlesource.com/828954Reviewed-by: 's avatarBenedikt Meurer <bmeurer@chromium.org>
    Commit-Queue: Georg Neis <neis@chromium.org>
    Cr-Commit-Position: refs/heads/master@{#50129}
    649ab060
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...
mkgrokdump Loading commit data...
mozilla Loading commit data...
preparser Loading commit data...
promises-aplus Loading commit data...
test262 Loading commit data...
unittests Loading commit data...
wasm-spec-tests 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...