• mtrofin's avatar
    We can avoid spilling live ranges with spill ranges when we have · c3e6048c
    mtrofin authored
    sufficient physical registers for all the virtual registers.
    
    This should come in handy for frame elision. There, I noticed that even
    for very small functions (==very few virtual registers), because we spill
    the context/function marker ranges, we lose the frame elision
    opportunity.
    
    There is a subsequent change needed to fully help frame elision -
    decoupling spilling of context & function marker from prologue.
    
    BUG=
    
    Review URL: https://codereview.chromium.org/1469743002
    
    Cr-Commit-Position: refs/heads/master@{#32221}
    c3e6048c
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...