This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug target/33374] GCC 4.1.2 produce wrong assembler code with -O2 option enabled.
- From: "_kirpichev_ at mail dot ru" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 10 Sep 2007 08:53:54 -0000
- Subject: [Bug target/33374] GCC 4.1.2 produce wrong assembler code with -O2 option enabled.
- References: <bug-33374-15076@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #4 from _kirpichev_ at mail dot ru 2007-09-10 08:53 -------
There is no core dump with -fno-strict-aliasing.
But, our code is used by others who can not set this option.
Should code compiled without -fno-strict-aliasing produce core dump?
In my opinion, the best way is produce only compiliation warnings in this case.
Should we rewrite our code if it is not possible to set -fno-strict-aliasing
option, or it is gcc issue that fixed in other versions?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33374