This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug optimization/11440] [3.3 regression] gcc-3.3.1 miscompiles c++ code with -O2, -fno-gcse cures it
- From: "pinskia at physics dot uc dot edu" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 11 Jul 2003 00:05:33 -0000
- Subject: [Bug optimization/11440] [3.3 regression] gcc-3.3.1 miscompiles c++ code with -O2, -fno-gcse cures it
- References: <20030705100217.11440.olh@suse.de>
- 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=11440
------- Additional Comments From pinskia at physics dot uc dot edu 2003-07-11 00:05 -------
No GCSE should not put the REG_EQUAL there.
Here is the definition of zero_extract's agruments:
/* Reference to a signed bit-field of specified size and position.
Operand 0 is the memory unit (usually SImode or QImode) which
contains the field's first bit. Operand 1 is the width, in bits.
Operand 2 is the number of bits in the memory unit before the
first bit of this field.
If BITS_BIG_ENDIAN is defined, the first bit is the msb and
operand 2 counts from the msb of the memory unit.
Otherwise, the first bit is the lsb and operand 2 counts from
the lsb of the memory unit. */