On Thu, Jul 11, 2013 at 11:11:28AM +0200, Andreas Arnez wrote:
> > On 07/10/2013 04:51 AM, Andreas Arnez wrote:
> >> OK, I may be biased, because I have *only* seen false positives with
> >> this warning so far. Others may have made better experience with it.
> > It's found numerous bugs across many projects. The reduction in bug
> > reports against GCC which turn out to be uninitialized variables in
> > the user's code has dropped dramatically over the last decade (if only
> > the same could be said for user malloc errors reported against glibc
> > :(
>
> Interesting. Upstream GCC seems to have added this option to -Wall on
> April 26th in 2011. Have those projects been using the option
> explicitly before?
You are misreading that change. On April 26th 2011 the -Wuninitialized
option was just split into -Wuninitialized and -Wmaybe-uninitialized,
to allow people to specify e.g. -Wno-error=maybe-uninitialized.
So the warning was included in -Wall before as well, for many many years.
Jakub
