• mstarzinger's avatar
    [interpreter] Fix destroyed new.target register use. · 0681deb9
    mstarzinger authored
    This fixes a corner-case where the bytecode was using the <new.target>
    register directly without going through the local variable. The value
    might be clobbered because the deoptimizer doesn't properly restore the
    value. The label will causes bytecode pipeline to be flushed and hence
    ensure {BytecodeRegisterOptimizer} doesn't reuse <new.target> anymore.
    
    R=rmcilroy@chromium.org
    TEST=mjsunit/regress/regress-crbug-645103
    BUG=chromium:645103
    
    Review-Url: https://codereview.chromium.org/2325133002
    Cr-Commit-Position: refs/heads/master@{#39306}
    0681deb9
Name
Last commit
Last update
..
benchmarks Loading commit data...
cctest Loading commit data...
fuzzer Loading commit data...
inspector_protocol_parser_test 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...