Copied logic from autoconf/configure.ac and added support to the cmake
build to turn off uninitialized use warnings for gcc. This cleans the
build up somewhat.
Details
- Reviewers
chandlerc gribozavr doug.gregor
Diff Detail
Event Timeline
If I can jump in...
cmake/config-ix.cmake | ||
---|---|---|
320–322 | So, why not test for -Wmaybe-uninitialized? Many versions of GCC ignore -Wno-... flags they don't understand, but I think they're very rigorous about supporting a -Wno-... variant for every flag the support a -W... variant of, so test for the positive one. My expected logic here is:
|
Vast simplification based on reviewer observation that although gcc
won't complain about unsupported -Wno-* flags it *will* complain about
unsupported -W flags. Instead of testing for -Wno-maybe-uninitialized we
test for the positive.
Someone should fix up the logic in autoconf/configure.ac the same way
too.
Argh. I got my branches mixed up and now this diff contains changes for my missing field initializer change. Please ignore that hunk. I'll be sending that for review separately.
So, why not test for -Wmaybe-uninitialized?
Many versions of GCC ignore -Wno-... flags they don't understand, but I think they're very rigorous about supporting a -Wno-... variant for every flag the support a -W... variant of, so test for the positive one.
My expected logic here is: