https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94745
--- Comment #4 from Louis Dionne ---
Thanks for your replies, all. We resolved the problem on our side by not trying
to workaround the lack of error, which means that we might end up passing
`-Wno-foo` to GCC when it's not supported. I think
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94745
Richard Biener changed:
What|Removed |Added
Resolution|--- |WONTFIX
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94745
--- Comment #2 from Jonathan Wakely ---
(In reply to Louis Dionne from comment #0)
> This makes detecting whether GCC supports a given warning flag very
> challenging in build systems.
You're doing it wrong then.
Try 'g++ -Q --help=warnings'
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94745
--- Comment #1 from Jonathan Wakely ---
This is by design. It means that makefiles written for different versions of
GCC do not trigger spurious diagnostics.
If somebody says "I don't want warnings about cat noises" and their version of
GCC
