This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [warnings] tagging warnings about options themselves
> However, the new -W* thingy just exhacrebates the issue.
Huh? I've converted a couple hundred calls to warning() and only
added two new -W options. I've been trying hard to not change the
logic of when warnings are issued, and the -W* "thingy" is no
different than the logic options we had before (except now it's more
centralized). How does centralizing the logic exacerbate the testing
issue?
If anything, this centralization *helps* testing because we can (1)
put hooks in the diagnostic machinery just for dejagnu, and (2) use
the OPT_* values (or -fdiagnostics-show-option) to check coverage.