[Bug c/69319] Suspect compiler bug

2016-01-16 Thread pinskia at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69319 Andrew Pinski changed: What|Removed |Added Status|WAITING |RESOLVED Resolution|---

[Bug c/69319] Suspect compiler bug

2016-01-16 Thread freddy77 at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69319 --- Comment #4 from Frediano Ziglio --- -O0, -O1 or -fno-strict-aliasing all works. But I don't understand how gcc can generate such code. What am I missing?

[Bug c/69319] Suspect compiler bug

2016-01-16 Thread freddy77 at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69319 --- Comment #3 from Frediano Ziglio --- Created attachment 37376 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=37376&action=edit original file split into pure C + main I don't know if may help (I hope so). I split the file into a pure C (

[Bug c/69319] Suspect compiler bug

2016-01-16 Thread pinskia at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69319 Andrew Pinski changed: What|Removed |Added Status|UNCONFIRMED |WAITING Last reconfirmed|

[Bug c/69319] Suspect compiler bug

2016-01-16 Thread freddy77 at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69319 --- Comment #1 from Frediano Ziglio --- Created attachment 37375 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=37375&action=edit .i file of the single source program