This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: -O2 bug in gcc 3.2, 3.3 and 3.4 with 64 bit integers on x86

From: Andreas Schwab <schwab at suse dot de>
To: Anders Torger <torger at ludd dot luth dot se>
Cc: gcc-bugs at gcc dot gnu dot org
Date: Tue, 09 Nov 2004 22:35:40 +0100
Subject: Re: -O2 bug in gcc 3.2, 3.3 and 3.4 with 64 bit integers on x86
References: <200411091642.01430.torger@ludd.luth.se><200411091715.39696.torger@ludd.luth.se><jewtwv7zu4.fsf@sykes.suse.de><200411091901.21154.torger@ludd.luth.se>

Anders Torger <torger@ludd.luth.se> writes:

> Perhaps GCC should not accept code that will result in undefined 
> behaviour

This is impossible because there is nothing wrong when the code is never
executed.

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux AG, Maxfeldstraße 5, 90409 Nürnberg, Germany
Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

References:
- -O2 bug in gcc 3.2, 3.3 and 3.4 with 64 bit integers on x86
  - From: Anders Torger
- Re: -O2 bug in gcc 3.2, 3.3 and 3.4 with 64 bit integers on x86
  - From: Anders Torger
- Re: -O2 bug in gcc 3.2, 3.3 and 3.4 with 64 bit integers on x86
  - From: Andreas Schwab
- Re: -O2 bug in gcc 3.2, 3.3 and 3.4 with 64 bit integers on x86
  - From: Anders Torger

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]