Good advice, but compilers often issue warnings like "x may be used uninitialized" even when it cannot happen.
http://kerneltrap.org/node/6591
An unrelated example where gcc (and icc) emit needless warnings about integer types is this:
int x = foo();
unsigned y = (x == 0);
Don't get me wrong, I'm in favor of cranking up the warning levels, but there is a reason why not everything is included in -Wall (yes, "uninitialized" is included, I know).I work on SIL-4 rated systems for life-protection applications. Absolutely ZERO TOLERANCE for warnings is a requirement in this job, and every single time it has been addressed, the warning gave us a clue how to fix something. Whether it was the code that needed fixing, or the compiler - either way, the alert is there. Ignore at your own peril.