dl; // 123
return 0;
--
Summary: O2 causes invalid code
Product: gcc
Version: 4.3.2
Status: UNCONFIRMED
Severity: critical
Priority: P3
Component: c++
AssignedTo: unassigned at gcc dot gnu dot org
--- Comment #1 from andrew at warnux dot com 2008-11-28 00:32 ---
I guess you want this too:
gcc -v
Using built-in specs.
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu 4.3.2-1ubuntu11'
--with-bugurl=file:///usr/share/doc/gcc-4.3/R
--- Comment #3 from andrew at warnux dot com 2008-11-28 01:59 ---
unsigned char
char and byte are the same size (1 byte), so why is there a problem?
--
andrew at warnux dot com changed:
What|Removed |Added
--- Comment #5 from andrew at warnux dot com 2008-11-28 02:33 ---
Thanks! I guess I learned something new today.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38297
--- Comment #6 from andrew at warnux dot com 2008-11-28 16:38 ---
I do have a couple concerns:
1. This one is MAJOR. Without using -Wstrict-aliasing, I never see warnings
about this change. I can't even begin to explain how bad that is. The gcc
programmers made a big change (th
--- Comment #9 from andrew at warnux dot com 2008-11-28 22:01 ---
I have another question. I want to be able to detect if fno-strict-aliasing
was used when compiling. Preferably at compile time but run time will be fine.
How can I do this?
--
andrew at warnux dot com changed
--- Comment #10 from andrew at warnux dot com 2008-11-28 22:02 ---
The shortest answer possible will be fine. I don't want to be an annoyance.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38297
