From: Steve Kargl <sgk@troutmask.apl.washington.edu>
To: Andrew Pinski <pinskia@gmail.com>
Cc: "Thomas König" <tk@tkoenig.net>,
"Jonathan Wakely" <jwakely.gcc@gmail.com>,
"N.M. Maclaren" <nmm1@cam.ac.uk>,
"Franz Sirl" <Franz.Sirl-kernel@lauterbach.com>,
"gcc@gcc.gnu.org" <gcc@gcc.gnu.org>,
"Thomas Koenig" <tkoenig@netcologne.de>,
"fortran@gcc.gnu.org" <fortran@gcc.gnu.org>
Subject: Re: [RFC] -Weverything
Date: Sun, 27 Jan 2019 21:28:00 -0000 [thread overview]
Message-ID: <20190127212833.GA40570@troutmask.apl.washington.edu> (raw)
In-Reply-To: <CA+=Sn1kTnsn4YrtK-rnyhotNLwwjcvfk1=EjAt8xVV62jFXQLg@mail.gmail.com>
On Sun, Jan 27, 2019 at 01:19:08PM -0800, Andrew Pinski wrote:
> On Sun, Jan 27, 2019 at 1:02 PM Thomas König <tk@tkoenig.net> wrote:
> >
> > Am 27.01.19 um 21:52 schrieb Steve Kargl:
> >
> > > In fact, I would be in favor of removing -Wall, as it is misnamed,
> > > in favor of -Wlevel=0,1,2,3... -Wlevel=0 default warnings.
> > > -Wlevel=1 is equivalent to -Wall. -Wlevel=2 is -Wall -Wextra
> > > (and maybe -Wsurprising).
> >
> > ... and -Wlevel=3 could then be -Wkitchen-sink, at least from the
> > Fortran-only side. :-)
> >
> > I quite like that idea. I don't think -Wall will be deprecated soon,
> > but -Wlevel sounds like a good thing to implement.
>
> Maybe instead of -Wlevel= why not just -W0, -W1, -W2, -W3; -W would be
> -W1 (because -W already exists)? Just like -O :).
>
That would work. With -Wlevel, I'm thinking that -Wlevel=-1 would be
the kitchen-sink. This means one can add new levels for positive
levels if desired: -Wlevel=n+1 = -Wlevel=n -Wnew-opt1 -Wnew-opt2,
etc.
--
Steve
next prev parent reply other threads:[~2019-01-27 21:28 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
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 [this message]
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=20190127212833.GA40570@troutmask.apl.washington.edu \
--to=sgk@troutmask.apl.washington.edu \
--cc=Franz.Sirl-kernel@lauterbach.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=jwakely.gcc@gmail.com \
--cc=nmm1@cam.ac.uk \
--cc=pinskia@gmail.com \
--cc=tk@tkoenig.net \
--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).