Tutorial :gcc switches to enable analysis for warnings


In gcc, certain warnings require optimization to be enabled. For example:

int foo() {      int x;      return x;  }  

In order to detect the uninitialized variable, -O must be passed.

$ gcc -W -Wall -c test.c  $ gcc -W -Wall -c test.c -O  test.c: In function ‘foo’:  test.c:3: warning: ‘x’ is used uninitialized in this function  

However, this can interfere with debugging. Is there a way to enable just the analysis phases needed for warnings (and not just this particular warning, but as many as possible), without affecting the generated code too much?

I'm using gcc version 4.3.3 (Ubuntu 4.3.3-5ubuntu4) on x86-64.


Try using -Wall instead of -W. -W is deprecated IIRC. (As Jonathan Leffler points out in a comment, -W's replacement is -Wextra, not -Wall.)


Warn whenever a local variable or non-constant static variable is unused aside from its declaration. This warning is enabled by -Wall.



This behavior has changed in GCC 4.4:

Uninitialized warnings do not require enabling optimization anymore, that is, -Wuninitialized can be used together with -O0. Nonetheless, the warnings given by -Wuninitialized will probably be more accurate if optimization is enabled.


DDD and gdb can mostly cope with code compiled with gcc -O -g. Sometimes variables aren't in scope when you expect them to be, but DDD is clever enough to say "optimized away" instead of freaking out. But there's no question it's easier to debug with -O turned offâ€"I have seen this a lot with my students' code.


This is what you have your automated build for. Let your automated build engine build with -Werror -Wall -O2, and you'll catch all the warnings triggered by higher optimization levels.

Note:If u also have question or solution just comment us below or mail us on toontricks1994@gmail.com
Next Post »