[Bug c/54544] New: Option -Wuninitialized does not work as documented with volatile

2012-09-10 Thread jimfr06 at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54544 Bug #: 54544 Summary: Option -Wuninitialized does not work as documented with volatile Classification: Unclassified Product: gcc Version: 4.6.3 Status: UNCONFIRMED

[Bug middle-end/54544] Option -Wuninitialized does not work as documented with volatile

2012-09-10 Thread jimfr06 at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54544 Zakhar changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|

[Bug middle-end/54544] Option -Wuninitialized does not work as documented with volatile

2012-09-11 Thread jimfr06 at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54544 Zakhar changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED Resolution|INVALID

[Bug middle-end/54544] Option -Wuninitialized does not work as documented with volatile

2012-09-11 Thread jimfr06 at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54544 --- Comment #4 from Zakhar 2012-09-11 21:09:28 UTC --- MORE Unfortunately, I don't think the hypothesis of the uninitialized pointed memory hold. That should prove it if we add: /*01*/ int fct(volatile int *p); /*02*/ /*03*/ static int /*0