diff options
author | Jan Beulich <jbeulich@suse.com> | 2025-01-06 16:01:47 +0100 |
---|---|---|
committer | Jan Beulich <jbeulich@suse.com> | 2025-01-06 16:01:47 +0100 |
commit | 9d02cb7fe0d636be390e43e06f39b30b834e89e4 (patch) | |
tree | 94917d91fc7cb3af2c5018b36b07056c3e57518c /gdb/python | |
parent | 30200464e9dd7903be8f186ea137b7982f812670 (diff) | |
download | binutils-9d02cb7fe0d636be390e43e06f39b30b834e89e4.zip binutils-9d02cb7fe0d636be390e43e06f39b30b834e89e4.tar.gz binutils-9d02cb7fe0d636be390e43e06f39b30b834e89e4.tar.bz2 |
x86/Intel: don't accept memory operands with J*CXZ and LOOP*
PR gas/31887
Like for, in particular, J<cc> such should be rejected. Simplify the
respective conditional in i386_intel_operand(), leveraging that
JumpAbsolute will never occur in the first template of a mnemonic-
specific group (thus making it unnecessary to exclude that one case).
At this occasion do the same simplification later in the function as
well: The resulting two operands will uniformly be invalid for all
mnemonics other than CALL and JMP (and their AT&T counterparts, which
we've been wrongly accepting in Intel syntax) anyway.
Diffstat (limited to 'gdb/python')
0 files changed, 0 insertions, 0 deletions