aboutsummaryrefslogtreecommitdiff
path: root/gas/literal.c
diff options
context:
space:
mode:
authorJan Beulich <jbeulich@novell.com>2016-07-01 09:03:02 +0200
committerJan Beulich <jbeulich@suse.com>2016-07-01 09:03:02 +0200
commit83b16ac69492ab493bfc87f147bf84c167bc6f30 (patch)
treeb6ddd3a6e27799f3024feb470ac135711f17ce0f /gas/literal.c
parentc07315e0c610e0e3317b4c02266f81793df253d2 (diff)
downloadgdb-83b16ac69492ab493bfc87f147bf84c167bc6f30.zip
gdb-83b16ac69492ab493bfc87f147bf84c167bc6f30.tar.gz
gdb-83b16ac69492ab493bfc87f147bf84c167bc6f30.tar.bz2
x86/Intel: don't accept bogus instructions
... due to their last byte looking like a suffix, when after its stripping a matching instruction can be found. Since memory operand size specifiers in Intel mode get converted into suffix representation internally, we need to keep track of the actual mnemonic suffix which may have got trimmed off, and check its validity while looking for a matching template. I tripper over this quite some time again after support for AMD's SSE5 instructions got removed, as at that point some of the SSE5 mnemonics, other than expected, didn't fail to assemble. But the problem affects many more instructions, namely (almost) all MMX, SSE, and AVX ones as it looks. I don't think it makes sense to add a testcase covering all of them, nor do I think it makes sense to pick out some random examples for a new test case.
Diffstat (limited to 'gas/literal.c')
0 files changed, 0 insertions, 0 deletions