diff options
| author | Jan Beulich <jbeulich@suse.com> | 2019-12-09 13:31:07 +0100 |
|---|---|---|
| committer | Jan Beulich <jbeulich@suse.com> | 2019-12-09 13:31:07 +0100 |
| commit | 164d49cb1c9b9f7e2914cf78f64f5f57ceb07dde (patch) | |
| tree | 571ed2970908cb24c1d784d62fec02de5fc24c10 /multilib.am | |
| parent | a8f4f6b9bc2b1273cfa94fc1f21af7bcf13012d5 (diff) | |
| download | gdb-164d49cb1c9b9f7e2914cf78f64f5f57ceb07dde.zip gdb-164d49cb1c9b9f7e2914cf78f64f5f57ceb07dde.tar.gz gdb-164d49cb1c9b9f7e2914cf78f64f5f57ceb07dde.tar.bz2 | |
x86/Intel: fix "near ptr" / "far ptr" handling
Commit dc2be329b950 ("i386: Only check suffix in instruction mnemonic")
broke rejecting of these for floating point insns. Fix this by setting
the "byte" operand attribute, which will now (again) cause an error.
Furthermore the diagnostic for the "far ptr" case in general and for the
"near ptr" case in the non-float cases became "invalid instruction
suffix" instead of the intended "operand size mismatch". Fix this by
also setting the "tbyte" operand attribute (no insn template accepts
both byte and tbyte operands).
Diffstat (limited to 'multilib.am')
0 files changed, 0 insertions, 0 deletions