From: Marc Glisse <marc.glisse@inria.fr>
To: Thomas Koenig <tkoenig@netcologne.de>
Cc: gcc mailing list <gcc@gcc.gnu.org>,
"fortran@gcc.gnu.org" <fortran@gcc.gnu.org>
Subject: Re: [RFC] -Weverything
Date: Tue, 22 Jan 2019 18:45:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.21.1901221941490.21659@stedding.saclay.inria.fr> (raw)
In-Reply-To: <80e1821d-b6da-c6b6-2bf2-29734f5fd34e@netcologne.de>
On Tue, 22 Jan 2019, Thomas Koenig wrote:
> Hi,
>
> What would people think about a -Weverything option which turns on
> every warning there is?
>
> I think that could be quite useful in some circumstances, especially
> to find potential bugs with warnings that people, for some reason
> or other, found too noisy for -Wextra.
>
> The name could be something else, of course. In the best GNU tradition,
> -Wkitchen-sink could be another option :-)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=31573 and duplicates already
list quite a few arguments. Basically, it could be useful for debugging
gcc or to discover warnings, but gcc devs fear that users will actually
use it for real.
--
Marc Glisse
next prev parent reply other threads:[~2019-01-22 18:45 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-22 18:34 Thomas Koenig
2019-01-22 18:45 ` Marc Glisse [this message]
2019-01-22 18:56 ` Jonathan Wakely
2019-01-22 19:00 ` Jonathan Wakely
2019-01-23 11:21 ` Franz Sirl
2019-01-23 11:37 ` Jonathan Wakely
2019-01-23 13:26 ` Thomas König
2019-01-23 13:53 ` Paul Richard Thomas
2019-01-27 13:56 ` N.M. Maclaren
2019-01-27 20:35 ` Jonathan Wakely
2019-01-27 20:52 ` Steve Kargl
2019-01-27 21:02 ` Thomas König
2019-01-27 21:19 ` Andrew Pinski
2019-01-27 21:28 ` Steve Kargl
2019-01-28 9:57 ` N.M. Maclaren
2019-01-28 22:53 ` Segher Boessenkool
2019-01-22 20:53 ` Jeffrey Walton
2019-01-23 0:53 ` Martin Sebor
2019-01-23 7:17 ` Thomas König
2019-01-23 7:31 ` Jakub Jelinek
2019-01-23 8:26 ` Marc Glisse
2019-01-23 9:31 ` Jonathan Wakely
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.21.1901221941490.21659@stedding.saclay.inria.fr \
--to=marc.glisse@inria.fr \
--cc=fortran@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=tkoenig@netcologne.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).