Hi, there are lots of bugs concerning the issue that uninitialized local variable uses are not always reported. See 10539 or 19099.
I think the restriction to optimized builds is particularly unfortunate, since a dev is more likely to actually look at a debug build. I'm not everybody, but assuming -Wall to catch the dumbest oversights seems natural to me. Probably that's why it got reported as a bug. I understand that optimization helps getting data in shape for this check, but it would be much better to have a few definitely-wrong cases checked by -Wall without -O, and more precise warnings with optimization. Or something like that. -- Summary: Warning about uninitialized local variable use Product: gcc Version: 4.3.2 Status: UNCONFIRMED Severity: enhancement Priority: P3 Component: c AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: simon dot thum at gmx dot de http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39693