https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87806
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |msebor at gcc dot gnu.org
--- Comment #5 from Martin Sebor <msebor at gcc dot gnu.org> ---
I agree that focusing the warning on definitions in .c files and avoiding those
in headers would be necessary to make the fallout manageable. But I'm not sure
-Wall or even -Wextra is a good fit even for this relaxed version of the
warning. GCC (and many other GNU projects, including Glibc) has a policy of
compiling cleanly with -Wall and -Wextra so enabling such a warning by either
would likely mean a lot of work cleaning up GCC itself (and the other
projects). Building some of these projects with the warnings explicitly
enabled would give us an idea of the scope of the cleanup. I could give that a
try but I can't find any options that control warnings about unused non-local
types and enums. What are they?
