This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug inline-asm/11925] New: segment violation due to incorrect operand constraints
- From: "jbeulich at novell dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 15 Aug 2003 06:42:10 -0000
- Subject: [Bug inline-asm/11925] New: segment violation due to incorrect operand constraints
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11925
Summary: segment violation due to incorrect operand constraints
Product: gcc
Version: 3.3.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: inline-asm
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: jbeulich at novell dot com
CC: gcc-bugs at gcc dot gnu dot org
GCC build triplet: i686-pc-linux-gnu
GCC host triplet: i686-pc-linux-gnu
GCC target triplet: i686-pc-linux-gnu
(i386 specific) Accessing an operand with constraint "r" through "%h0" causes a
segment violation (or other misbehavior) because print_reg() does not range
check REGNO(x) prior to indexing into the (only 4 elements long)
qi_high_reg_name array.
Interestingly the x86-64 specific code dealing with the REX registers does some
validation is that certain combinations result in error() being called.