gcc-head bug? feature?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



[please keep me CC'd]
Hi,

Is this a user error (thus an optimisation feature) or a glitch in gcc?

$ for o in '' -O2; do echo "# o='$o'";gcc-4.1-HEAD -W -Wall -Wextra
-pedantic $o -g -Wall -I. -o bar41.$o foo.c ;./bar41.$o;done
# o=''
var1=1020308
var1=1020809
# o='-O2'
foo.c: In function 'main':
foo.c:7: warning: dereferencing type-punned pointer will break
strict-aliasing rules
var1=1020308
var1=1020308

with O2, the second assignment is "optimized out"?

gcc-4.0.1, gcc-3.4, gcc-3.3, gcc-2.95 all yield 1020308 and 1020809 for
Odefault and O2, as opposed to gcc-4.1.

$ cat foo.c 
#include <stdio.h>
int main(void)
{
	int var1 = 0x01020304;
	*(char *)&var1 = 0x08;
	printf("var1=%x\n", var1);
	*(short *)&var1 = 0x0809;
	printf("var1=%x\n", var1);
	return 0;
}


[Index of Archives]     [Linux C Programming]     [Linux Kernel]     [eCos]     [Fedora Development]     [Fedora Announce]     [Autoconf]     [The DWARVES Debugging Tools]     [Yosemite Campsites]     [Yosemite News]     [Linux GCC]

  Powered by Linux