------- Comment #2 from rguenth at gcc dot gnu dot org  2008-06-22 15:43 -------
I certainly belive this was uncovered by my patch for PR36345.  But I also
believe newlib is at fault here ;)  The fix simply makes strict-aliasing rules
followed even more (thus, if you build newlib with -fno-strict-aliasing the
failure should go away).


-- 


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

Reply via email to