[Bug other/44209] [meta-bug] Some warnings are not linked to diagnostics options
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=44209 Bug 44209 depends on bug 106537, which changed state. Bug 106537 Summary: GCC doesn't support -W[no-]compare-distinct-pointer-types https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106537 What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED
[Bug other/44209] [meta-bug] Some warnings are not linked to diagnostics options
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=44209 --- Comment #12 from GCC Commits --- The master branch has been updated by Florian Weimer : https://gcc.gnu.org/g:ff9efa3fc48baa1dee7ed376c25ecfcfbc28d35c commit r14-6038-gff9efa3fc48baa1dee7ed376c25ecfcfbc28d35c Author: Florian Weimer Date: Fri Dec 1 08:10:13 2023 +0100 c: Add new -Wdeclaration-missing-parameter-type permerror This used to be a warning, enabled by default, without its own option. A subsequent change could improve diagnostics and provide spelling hints for declarations like âvoid function (int32t);â. gcc/c-family/ * c.opt (Wdeclaration-missing-parameter-type): New. gcc/c/ChangeLog: PR other/44209 * c-decl.cc (grokparms): Issue permerror for OPT_Wdeclaration_missing_parameter_type instead of a pedwarn. gcc/ChangeLog: * doc/invoke.texi (Warning Options): Document -Wdeclaration-missing-parameter-type. gcc/testsuite/ChangeLog: * gcc.dg/permerror-default.c (missing_parameter_type): Expect error. * gcc.dg/permerror-fpermissive.c (missing_parameter_type): Expect -Wdeclaration-missing-parameter-type warning. * gcc.dg/permerror-gnu89-nopermissive.c (missing_parameter_type): Expect -Wdeclaration-missing-parameter-type error. * gcc.dg/permerror-gnu89-pedantic.c (missing_parameter_type): Likewise. * gcc.dg/permerror-gnu89.c (missing_parameter_type): Expect -Wdeclaration-missing-parameter-type warning. * gcc.dg/permerror-noerror.c: Add -Wno-error=declaration-missing-parameter-type to build flags. (missing_parameter_type): Expect -Wdeclaration-missing-parameter-type warning. * gcc.dg/permerror-nowarning.c: Build with -Wno-declaration-missing-parameter-type. Remove previously expected warning. * gcc.dg/permerror-fpermissive-nowarning.c: Likewise. * gcc.dg/permerror-pedantic.c (missing_parameter_type): Expect -Wdeclaration-missing-parameter-type error. * gcc.dg/permerror-system.c (missing_parameter_type): Likewise.
[Bug other/44209] [meta-bug] Some warnings are not linked to diagnostics options
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=44209 Bug 44209 depends on bug 109827, which changed state. Bug 109827 Summary: Pointer/integer mismatch in ?: not covered by -Wint-conversion https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109827 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED
[Bug other/44209] [meta-bug] Some warnings are not linked to diagnostics options
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=44209 Bug 44209 depends on bug 109826, which changed state. Bug 109826 Summary: Incompatible pointer types in ?: not covered by -Wincompatible-pointer-types https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109826 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED
[Bug other/44209] [meta-bug] Some warnings are not linked to diagnostics options
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=44209 --- Comment #10 from CVS Commits --- The master branch has been updated by Florian Weimer : https://gcc.gnu.org/g:857a6ee25ff5cbb97715de4dd97e1641285c6085 commit r14-4804-g857a6ee25ff5cbb97715de4dd97e1641285c6085 Author: Florian Weimer Date: Fri Oct 20 21:27:52 2023 +0200 c: -Wincompatible-pointer-types should cover mismatches in ?: gcc/c/ PR c/109826 PR other/44209 * c-typeck.cc (build_conditional_expr): Use OPT_Wincompatible_pointer_types for pointer mismatches. Emit location information for the operand. gcc/testsuite/ * gcc.dg/Wincompatible-pointer-types-2.c: New. * gcc.dg/Wincompatible-pointer-types-3.c: New. * gcc.dg/Wincompatible-pointer-types-4.c: New.
[Bug other/44209] [meta-bug] Some warnings are not linked to diagnostics options
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=44209 --- Comment #11 from CVS Commits --- The master branch has been updated by Florian Weimer : https://gcc.gnu.org/g:7069ea909f5292a17d22e5e68218373186820d29 commit r14-4805-g7069ea909f5292a17d22e5e68218373186820d29 Author: Florian Weimer Date: Fri Oct 20 21:27:52 2023 +0200 c: -Wint-conversion should cover pointer/integer mismatches in ?: gcc/c/ PR c/109827 PR other/44209 * c-typeck.cc (build_conditional_expr): Use OPT_Wint_conversion for pointer/integer mismatch warnings. gcc/testsuite/ * gcc.dg/Wint-conversion-3.c: New.
[Bug other/44209] [meta-bug] Some warnings are not linked to diagnostics options
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=44209 --- Comment #9 from Manuel López-Ibáñez --- For the sake of other potential readers: Patches should be submitted to gcc-patc...@gcc.gnu.org and reviewers do not review patches in bugzilla. Nevertheless, it is a good idea to add the link to the mailing list archive here in bugzilla so the patch is not forgotten. For more details, please read: https://gcc.gnu.org/wiki/GettingStarted#Basics:_Contributing_to_GCC_in_10_easy_steps How to submit and ping patches: https://gcc.gnu.org/contribute.html#patches See other suggestions on how to interact with the GCC community here: https://gcc.gnu.org/wiki/Community
[Bug other/44209] [meta-bug] Some warnings are not linked to diagnostics options
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=44209 Julian Waters changed: What|Removed |Added CC||tanksherman27 at gmail dot com --- Comment #8 from Julian Waters --- I have a patch ready for the noreturn warning at https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111654, is anyone willing to help review and push it?
[Bug other/44209] [meta-bug] Some warnings are not linked to diagnostics options
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=44209 Bug 44209 depends on bug 106537, which changed state. Bug 106537 Summary: GCC doesn't support -W[no-]compare-distinct-pointer-types https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106537 What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |---
[Bug other/44209] [meta-bug] Some warnings are not linked to diagnostics options
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=44209 Bug 44209 depends on bug 106537, which changed state. Bug 106537 Summary: GCC doesn't support -W[no-]compare-distinct-pointer-types https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106537 What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED
[Bug other/44209] [meta-bug] Some warnings are not linked to diagnostics options
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=44209 --- Comment #7 from Eric Gallager --- additional example raised on gcc mailing list: https://gcc.gnu.org/pipermail/gcc/2023-July/241970.html
[Bug other/44209] [meta-bug] Some warnings are not linked to diagnostics options
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=44209 Bug 44209 depends on bug 61414, which changed state. Bug 61414 Summary: enum class bitfield size-checking needs a separate warning flag controlling it https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61414 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED
[Bug other/44209] [meta-bug] Some warnings are not linked to diagnostics options
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=44209 Bug 44209 depends on bug 92182, which changed state. Bug 92182 Summary: No way to silence ''A::TKind' is too small to hold all values of 'enum Kind'' https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92182 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |DUPLICATE
[Bug other/44209] [meta-bug] Some warnings are not linked to diagnostics options
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=44209 Bug 44209 depends on bug 90875, which changed state. Bug 90875 Summary: warnings about switch values outside range don't have associated option https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90875 What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED
[Bug other/44209] [meta-bug] Some warnings are not linked to diagnostics options
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=44209 Bug 44209 depends on bug 90875, which changed state. Bug 90875 Summary: warnings about switch values outside range don't have associated option https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90875 What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |---
[Bug other/44209] [meta-bug] Some warnings are not linked to diagnostics options
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=44209 Bug 44209 depends on bug 90875, which changed state. Bug 90875 Summary: warnings about switch values outside range don't have associated option https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90875 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED
[Bug other/44209] [meta-bug] Some warnings are not linked to diagnostics options
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=44209 Bug 44209 depends on bug 90449, which changed state. Bug 90449 Summary: No way to turn off warning about inaccessible base https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90449 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED
[Bug other/44209] [meta-bug] Some warnings are not linked to diagnostics options
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=44209 --- Comment #6 from Eric Gallager --- (In reply to Will Hawkins from comment #5) > I am using this as a jumping-off point to get involved with contributing > code to gcc. I have nothing to offer yet, but I wanted to note here that I > am going to start looking into this. > > Will OK cool, do you want to be the assignee then?
[Bug other/44209] [meta-bug] Some warnings are not linked to diagnostics options
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=44209 Will Hawkins changed: What|Removed |Added CC||whh8b at virginia dot edu --- Comment #5 from Will Hawkins --- I am using this as a jumping-off point to get involved with contributing code to gcc. I have nothing to offer yet, but I wanted to note here that I am going to start looking into this. Will
[Bug other/44209] [meta-bug] Some warnings are not linked to diagnostics options
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=44209 Eric Gallager 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 --- (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"
