[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Bug gas/31887] gas confuses an memory operand as immediate value (no di
From: |
cvs-commit at gcc dot gnu.org |
Subject: |
[Bug gas/31887] gas confuses an memory operand as immediate value (no diagnostic) for various x86 opcodes |
Date: |
Mon, 06 Jan 2025 15:02:46 +0000 |
https://sourceware.org/bugzilla/show_bug.cgi?id=31887
--- Comment #2 from Sourceware Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jan Beulich <jbeulich@sourceware.org>:
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=9d02cb7fe0d636be390e43e06f39b30b834e89e4
commit 9d02cb7fe0d636be390e43e06f39b30b834e89e4
Author: Jan Beulich <jbeulich@suse.com>
Date: Mon Jan 6 16:01:47 2025 +0100
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.
--
You are receiving this mail because:
You are on the CC list for the bug.
- [Bug gas/31887] gas confuses an memory operand as immediate value (no diagnostic) for various x86 opcodes,
cvs-commit at gcc dot gnu.org <=