diff options
| author | Jan Beulich <jbeulich@suse.com> | 2024-05-29 10:02:01 +0200 |
|---|---|---|
| committer | Jan Beulich <jbeulich@suse.com> | 2024-05-29 10:02:01 +0200 |
| commit | 6ccf16c19d318bae09b7b405825285f7579d820f (patch) | |
| tree | 893a4e8c775b07ac972d2a7ea5b5715c152dffda /bfd | |
| parent | 7574c0c2b386efa4bd0b1735237403177e4a964e (diff) | |
| download | gdb-6ccf16c19d318bae09b7b405825285f7579d820f.zip gdb-6ccf16c19d318bae09b7b405825285f7579d820f.tar.gz gdb-6ccf16c19d318bae09b7b405825285f7579d820f.tar.bz2 | |
x86/Intel: SHLD/SHRD have dual meaning
Since we uniformly permit D suffixes in Intel mode whenever in AT&T mode
an L suffix may be used, we need to be consistent with this.
Take the easy route, despite that still leading to an anomaly which is
also visible from the new testcase:
shld eax, ecx, 1
shld eax, ecx, cl
can mean two things with APX: SHL with a D suffix in NDD EVEX encoding,
or the traditional SHLD in legacy encoding.
Diffstat (limited to 'bfd')
0 files changed, 0 insertions, 0 deletions