• 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...
build Loading commit data...
docs Loading commit data...
include Loading commit data...
infra Loading commit data...
samples Loading commit data...
src Loading commit data...
test Loading commit data...
testing Loading commit data...
third_party/binutils Loading commit data...
tools Loading commit data...
.clang-format Loading commit data...
.gitignore Loading commit data...
.ycm_extra_conf.py Loading commit data...
AUTHORS Loading commit data...
BUILD.gn Loading commit data...
ChangeLog Loading commit data...
DEPS Loading commit data...
LICENSE Loading commit data...
LICENSE.strongtalk Loading commit data...
LICENSE.v8 Loading commit data...
LICENSE.valgrind Loading commit data...
Makefile Loading commit data...
Makefile.android Loading commit data...
Makefile.nacl Loading commit data...
OWNERS Loading commit data...
PRESUBMIT.py Loading commit data...
README.md Loading commit data...
WATCHLISTS Loading commit data...
codereview.settings Loading commit data...
snapshot_toolchain.gni Loading commit data...