diff options
author | Jan Beulich <jbeulich@suse.com> | 2023-02-24 14:00:11 +0100 |
---|---|---|
committer | Jan Beulich <jbeulich@suse.com> | 2023-02-24 14:00:11 +0100 |
commit | ae9a0a51e851eac3cdcd2a6791bf05480211c169 (patch) | |
tree | f648d40b9e9dfa9561d6c7cb261140155cf49f0b /ld/testsuite/ld-elf/maxpage1.d | |
parent | cafa5ef72e29d0a203d0c07cbec4e0688c26d1eb (diff) | |
download | binutils-gdb-ae9a0a51e851eac3cdcd2a6791bf05480211c169.tar.gz |
x86: allow to request ModR/M encoding
Several insns have a (typically shorter) non-ModR/M and a (typically
longer) ModR/M encoding. In most cases the former is used by default.
This isn't too dissimilar from register-only insns sometimes having two
encoding forms. In those cases {load} or {store} can be used to control
the encoding used. Extend this to ModR/M-less encodings which have a
ModR/M counterpart (note that BSWAP hasn't). For insn reading and
writing their (explicit) memory operand, both prefixes are honored;
otherwise only the applicable one is.
Note that for some forms of XCHG, {store} has already been performing
this function, apparently as an unnoticed side effect of adding D to
the template.
Diffstat (limited to 'ld/testsuite/ld-elf/maxpage1.d')
0 files changed, 0 insertions, 0 deletions