diff options
author | Jan Beulich <jbeulich@suse.com> | 2022-05-27 08:48:58 +0200 |
---|---|---|
committer | Jan Beulich <jbeulich@suse.com> | 2022-05-27 08:48:58 +0200 |
commit | 7063667edb6a663163c2adba754b5abbbe67dc46 (patch) | |
tree | 915694f647592bf8fe74d4b68b781efaf88f30dd /config | |
parent | cf665fee1d6c9efa2e59af496cd132393732306d (diff) | |
download | fsf-binutils-gdb-7063667edb6a663163c2adba754b5abbbe67dc46.zip fsf-binutils-gdb-7063667edb6a663163c2adba754b5abbbe67dc46.tar.gz fsf-binutils-gdb-7063667edb6a663163c2adba754b5abbbe67dc46.tar.bz2 |
x86/Intel: allow MASM representation of embedded rounding / SAE
MASM doesn't support the separate operand form; the modifier belongs
after the instruction instead. Accept this form alongside the original
(now legacy) one. Short of having access to a MASM version to actually
check in how far "after the instruction" is a precise statement in their
documentation, allow both that and the SDM mandated form where the
modifier is on the last register operand (with a possible immediate
operand following).
Sadly the split out function, at least for the time being, needs to cast
away constness at some point, as the two callers disagree in this
regard.
Adjust some, but not all of the testcases.
Diffstat (limited to 'config')
0 files changed, 0 insertions, 0 deletions