• Clemens Hammacher's avatar
    [Liftoff] Don't force unrelated stack slots into registers · 1cec66d3
    Clemens Hammacher authored
    When initializing the stack state at a merge point, don't force all
    stack slots into registers. Allow constants to stay constants as long
    as they are not part of the merge. Otherwise we might break assumptions
    of outer blocks which then try to merge a register into a constant and
    fail.
    Also, add some documentation to {InitMergeStackSlot} to document the
    intent of the implementation.
    
    R=titzer@chromium.org
    
    Bug: v8:784050, v8:6600
    Change-Id: I3a4c83b446909027be075d3207cb7c748a6b1aad
    Reviewed-on: https://chromium-review.googlesource.com/766353Reviewed-by: 's avatarBen Titzer <titzer@chromium.org>
    Commit-Queue: Clemens Hammacher <clemensh@chromium.org>
    Cr-Commit-Position: refs/heads/master@{#49423}
    1cec66d3
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...