This is the mail archive of the gcc@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: optimization/7799: [3.2/3.3 regression] Loop bug withoptimization flag -Os in gcc


On Fri, Dec 13, 2002 at 09:09:15PM -0000, Morten Welinder wrote:
> 1. sizeof(int) == sizeof(char) == 1.  int is four bytes wide.

Eh?  1 == 4?

> 2. NULL represented as address 0.
> 3. OS support to read/write unaligned.
> 4. OS support to read/write wrapped, e.g., read four bytes at 0xffffffff.

You're trying too hard.  We do not care about theory so much as
practice.  Are you seriously suggesting that there exists an OS
that is this broken?

The signed/unsigned wrap at 0x80000000 as exemplified by loop-3.c
is a real bug, distilled from a real test case on a real os.  The
situation you are describing is absurd.


r~


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