• 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
..
base Loading commit data...
compiler Loading commit data...
heap Loading commit data...
interpreter Loading commit data...
libplatform Loading commit data...
runtime Loading commit data...
DEPS Loading commit data...
atomic-utils-unittest.cc Loading commit data...
char-predicates-unittest.cc Loading commit data...
counters-unittest.cc Loading commit data...
run-all-unittests.cc Loading commit data...
test-utils.cc Loading commit data...
test-utils.h Loading commit data...
unittests.gyp Loading commit data...
unittests.isolate Loading commit data...
unittests.status Loading commit data...