https://gcc.gnu.org/bugzilla/show_bug.cgi?id=44209

Eric Gallager <egallager at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |meta-bug
         Depends on|                            |67353, 7651
            Summary|Some warnings are not       |[meta-bug] Some warnings
                   |linked to diagnostics       |are not linked to
                   |options                     |diagnostics options

--- Comment #4 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Manuel López-Ibáñez from comment #3)
> There are two cases:
> 
> * Warnings that are controlled by an option (e.g., Wall) but do not show up
> in -fdiagnostics-show-option. These are obvious bugs and normally trivial to
> fix: there is already an -Wsomething option controlling them but the warning
> call is done with warning (0, "warning") instead of warning (OPT_Wsomething,
> "warning"). If you provide me a list of those that you can find, I will fix
> them.
> 
> * Warnings that are not controlled by any option and are enabled by default.
> These cases are not clear-cut because we do not want millions of options, so
> we would prefer to group related warnings under the same option. Also,
> proposing a good -Wname for the option is always controversial. I don't
> think there are many of these, but a list of the worst offenders would also
> help.

Making this a meta-bug; will add relevant bugs as dependencies to this one as I
find them. That can count as a list.


Referenced Bugs:

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=7651
[Bug 7651] Define -Wextra strictly in terms of other warning flags
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67353
[Bug 67353] [avr] Option-ize Warning "appears to be a misspelled signal /
interrupt handler"

Reply via email to