• jarin's avatar
    [turbofan] Checking monotonicity of representation inference outputs and inputs. · ebed36ee
    jarin authored
    Monotonicity is not required at the current setup, where we do backward pass through
    the graph.  However, for bidirectinal analysis, we'd better be sure that all the
    input/use information is monotone.
    
    The checker here is quite strict - it requires monotonicity in each of: use
    representations, use truncation, output representation and output type. In future, we can
    lower the requirements and use lexicographic ordering (e.g., on use truncation and
    representation).
    
    Review URL: https://codereview.chromium.org/1473733007
    
    Cr-Commit-Position: refs/heads/master@{#32392}
    ebed36ee
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...