http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36296
--- Comment #21 from Manuel López-Ibáñez <manu at gcc dot gnu.org> 2013-04-17 11:26:01 UTC --- (In reply to comment #20) > OK, so a solution would be to add a configure test for projects that don't > want > such warnings (while still using -Wall) to see whether > -Wno-maybe-uninitialized > is supported. When an unrecognized warning option is requested (e.g., -Wunknown-warning), GCC will emit a diagnostic stating that the option is not recognized. However, if the -Wno- form is used, the behavior is slightly different: No diagnostic will be produced for -Wno-unknown-warning unless other diagnostics are being produced. This allows the use of new -Wno- options with old compilers, but if something goes wrong, the compiler will warn that an unrecognized option was used.
