• clemensh's avatar
    [x64] Use smaller code sequence when pushing SMIs · 45f1bf80
    clemensh authored
    If exactly one byte in the upper half of the pushed 8-byte value is
    set, use a smaller code sequence to push this value on the stack.
    Before, we did
      movq r10,<constant>
      push r10
    Now, we do
      push 0x0
      movb [rsp+<offset>],<byte>
    
    The old sequence had 12 bytes, the new one has 7.
    Pushing such values is used a lot for stack frame markers, which are
    small numbers (1-17) encoded as SMIs.
    
    Review-Url: https://codereview.chromium.org/2685213004
    Cr-Commit-Position: refs/heads/master@{#43146}
    45f1bf80
Name
Last commit
Last update
benchmarks Loading commit data...
build_overrides Loading commit data...
docs Loading commit data...
gni Loading commit data...
gypfiles 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 Loading commit data...
tools Loading commit data...
.clang-format Loading commit data...
.gitignore Loading commit data...
.gn Loading commit data...
.ycm_extra_conf.py Loading commit data...
AUTHORS Loading commit data...
BUILD.gn Loading commit data...
CODE_OF_CONDUCT.md Loading commit data...
ChangeLog Loading commit data...
DEPS Loading commit data...
LICENSE Loading commit data...
LICENSE.fdlibm 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...
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...