"brian m. carlson" <sand...@crustytoothpaste.ath.cx> writes:
> I'm aware of that. My opinion remains the same: GCC should generate > POSIX-conformant code without warnings with -O2 -Wall. That can be > achieved by disabling -fstrict-aliasing at -O2, by patching glibc to > allow aliasing of the relevant types, by special-casing these types on a > POSIX system, or by something else altogether. How it is achieved is > mostly irrelevant to me, as long as it stops breaking code that is > explicitly documented by POSIX to work (and has worked for longer than > I've been alive). The definition of c99 from your earlier POSIX reference http://www.opengroup.org/onlinepubs/000095399/utilities/c99.html states that the compiler should accept code conforming to the ISO C standard. The code you are trying to compile doesn't conform. -- To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org