------- Comment #7 from rguenth at gcc dot gnu dot org  2008-02-20 14:47 -------
We should probably admit that we will not fix this bug for GCC 4.1 (there will
be no further release off that branch).  A workaround is to use
-fno-strict-aliasing.

Please consider moving to GCC 4.2.x or 4.3.x once it is released.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35140

Reply via email to