https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66293
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |diagnostic
CC| |egallager at gcc dot gnu.org
See Also| |https://gcc.gnu.org/bugzill
| |a/show_bug.cgi?id=53313,
| |https://gcc.gnu.org/bugzill
| |a/show_bug.cgi?id=87656
--- Comment #6 from Eric Gallager <egallager at gcc dot gnu.org> ---
One idea I had for allowing while discouraging use of -Weverything would be for
it to always print at least 1 warning from itself ("Warning: Don't use
-Weverything [-Weverything]") in addition to all the other warnings that it
enables. That way people would be less tempted to try to use it with -Werror.
(In reply to Jean-Michaël Celerier from comment #3)
> As a Clang user, -Weverything allowed me to remove terrible bugs that would
> not crop up with -Wall -Wextra -Wfew-other-common-warnings.
>
> For instance GCC 6 brings in many new warnings it seems. Well, it is a pity
> to have to go through the manual to find the new warnings and enable them by
> hand (very few people will actually do this, while it could certainly make
> some bugs appear. Maybe it could prevent the next Heartbleed ?).
We should just move these new warnings under -Wall or -Wextra instead. See bug
87656
