• mtrofin's avatar
    When we split above an instruction (for example because of splintering), · 46878c1d
    mtrofin authored
    we may introduce moves that are redundant in the context of
    moves on subsequent instructions. Currently, we only detect such
    redundancies by allowing moves to skip over Nop instructions (true
    nops, with no input/output). We can also skip over other cases, for
    example over constant definitions (nop with an output), since whatever
    moves happen above it do not influence the instruction's outcome.
    
    We may be able to handle other cases, too - in subsequent CLs.
    
    BUG=
    
    Review URL: https://codereview.chromium.org/1422333003
    
    Cr-Commit-Position: refs/heads/master@{#31662}
    46878c1d
Name
Last commit
Last update
..
benchmarks Loading commit data...
cctest 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...
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...