[Bug c++/31573] -Wall-all to enable all warnings

2021-10-19 Thread egallager at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=31573 Eric Gallager changed: What|Removed |Added CC||egallager at gcc dot gnu.org --- Comment

[Bug c++/31573] -Wall-all to enable all warnings

2021-10-19 Thread gabravier at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=31573 --- Comment #11 from Gabriel Ravier --- Well, that does help, although it is still a significant annoyance that would take more than its fair share of time to handle. (Also, is it still really that much of a concern anymore that users would thin

[Bug c++/31573] -Wall-all to enable all warnings

2021-10-19 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=31573 --- Comment #10 from Jonathan Wakely --- You're doing it wrong. gcc -Q --help=warnings

[Bug c++/31573] -Wall-all to enable all warnings

2021-10-19 Thread gabravier at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=31573 Gabriel Ravier changed: What|Removed |Added CC||gabravier at gmail dot com --- Comment

[Bug c++/31573] -Wall-all to enable all warnings

2016-02-15 Thread manu at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=31573 Manuel López-Ibáñez changed: What|Removed |Added CC||manu at gcc dot gnu.org --- Commen

[Bug c++/31573] -Wall-all to enable all warnings

2016-02-15 Thread manu at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=31573 Manuel López-Ibáñez changed: What|Removed |Added CC||david at doublewise dot net --- Co

[Bug c++/31573] -Wall-all to enable all warnings

2015-05-26 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=31573 Jonathan Wakely changed: What|Removed |Added CC||sverd.johnsen at googlemail dot co

[Bug c++/31573] -Wall-all to enable all warnings

2011-02-21 Thread jakub at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31573 --- Comment #5 from Jakub Jelinek 2011-02-21 12:55:51 UTC --- *** Bug 47824 has been marked as a duplicate of this bug. ***

[Bug c++/31573] -Wall-all to enable all warnings

2011-02-20 Thread pinskia at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31573 Andrew Pinski changed: What|Removed |Added CC||olafvdspek at gmail dot com --- Comment #

[Bug c++/31573] -Wall-all to enable all warnings

2007-04-14 Thread fang at csl dot cornell dot edu
--- Comment #3 from fang at csl dot cornell dot edu 2007-04-14 22:24 --- Subject: Re: -Wall-all to enable all warnings > --- Comment #2 from pinskia at gcc dot gnu dot org 2007-04-14 21:18 > --- > Actually more than that, there are new warnings options each release so really

[Bug c++/31573] -Wall-all to enable all warnings

2007-04-14 Thread pinskia at gcc dot gnu dot org
--- Comment #2 from pinskia at gcc dot gnu dot org 2007-04-14 21:18 --- Actually more than that, there are new warnings options each release so really if we have this we will get complaints about warnings options get added. so I am going to close this as won't fix. -- pinskia at gcc

[Bug c++/31573] -Wall-all to enable all warnings

2007-04-14 Thread fang at csl dot cornell dot edu
--- Comment #1 from fang at csl dot cornell dot edu 2007-04-14 20:27 --- That begs the question: what's *not* covered by -W -Wall -Wextra [-ansi -pedantic-errors -Werror]? There are also some warning flags that are parameterized (-Wstrict-aliasing=#, -Wformat=#), should those be maxed