[Bug c/58236] -Wuninitialized doesn't report uninitialised variable as expected

2013-10-30 Thread manu at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58236 Manuel López-Ibáñez changed: What|Removed |Added CC||manu at gcc dot gnu.org Res

[Bug c/58236] -Wuninitialized doesn't report uninitialised variable as expected

2013-10-30 Thread law at redhat dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58236 Jeffrey A. Law changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC|

[Bug c/58236] -Wuninitialized doesn't report uninitialised variable as expected

2013-08-24 Thread noufal at nibrahim dot net.in
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58236 --- Comment #2 from Noufal Ibrahim --- That solves the issue although I find the relationship between the optimisations and the warnings somewhat tenuous atleast from a user perspective. Would it not be a good idea to have this warning even by def

[Bug c/58236] -Wuninitialized doesn't report uninitialised variable as expected

2013-08-24 Thread glisse at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58236 --- Comment #1 from Marc Glisse --- Note, from the documentation of -Wuninitialized: "Because these warnings depend on optimization, the exact variables or elements for which there are warnings depends on the precise optimization options and vers