GCC -Wuninitialized / -Wmaybe-uninitialized issues

by

Indeed this is a known problem in gcc.
gcc is notorious for reporting incorrect uninitialized variables.
The shortcomings have been duly noted and there is a initiative to overcome the shortcomings:
Better Uninitialized Warnings:

The GNU Compiler Collection warns about the use of uninitialized variables with the option -Wuninitialized. However, the current implementation has some perceived shortcomings. On one hand, some users would like more verbose and consistent warnings. On the other hand, some users would like to get as few warnings as possible. The goal of this project is to implement both possibilities while at the same time improving the current capabilities.

The initiative aims at providing better warnings and it quotes a example case similar as your case. The relevant portion being:

What an user understands as a false positive may be different for the particular user. Some users are interested in cases that are hidden because of actions of the optimizers combined with the current environment. However, many users aren’t, since that case is hidden because it cannot arise in the compiled code. The canonical example is

int x;
if (f ())
     x = 3;
return x;

where ‘f’ always return non-zero for the current environment, and thus, it may be optimized away. Here, a group of users would like to get an uninitialized warning since ‘f’ may return zero when compiled elsewhere. Yet, other group of users would consider spurious a warning about a situation that cannot arise in the executable being compiled.

More Related Contents:

  1. How to remove “noise” from GCC/clang assembly output?
  2. How do I best silence a warning about unused variables?
  3. gcc optimization flag -O3 makes code slower than -O2
  4. How to turn on (literally) ALL of GCC’s warnings?
  5. Why does GCC generate 15-20% faster code if I optimize for size instead of speed?
  6. Why does the enhanced GCC 6 optimizer break practical C++ code?
  7. Preventing compiler optimizations while benchmarking
  8. How can I turn on (literally) ALL of GCC’s warnings?
  9. GCC: Difference between -O3 and -Os
  10. How do you get assembler output from C/C++ source in gcc?
  11. Is cout synchronized/thread-safe?
  12. c++ virtual inheritance
  13. GCC and Precompiled Headers
  14. Explicit specialization in non-namespace scope [duplicate]
  15. experimental::filesystem linker error
  16. How to recompile with -fPIC
  17. C++ compilation bug?
  18. Labels in GCC inline assembly
  19. Efficient 128-bit addition using carry flag
  20. Is auto as a parameter in a regular function a GCC 4.9 extension?
  21. Is there a compiler hint for GCC to force branch prediction to always go a certain way?
  22. 😃 (and other Unicode characters) in identifiers not allowed by g++
  23. Inherit interfaces which share a method name
  24. Compile a DLL in C/C++, then call it from another program
  25. Linking to MSVC DLL from MinGW
  26. Where does gcc look for C and C++ header files?
  27. Referencing memory operands in .intel_syntax GNU C inline assembly
  28. Can I hint the optimizer by giving the range of an integer?
  29. What does exactly the warning mean about hidden symbol being referenced by DSO?
  30. C++ static initialization vs __attribute__((constructor))

Leave a Comment