public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/53313] Add warning levels
Date: Fri, 24 Apr 2015 11:59:00 -0000	[thread overview]
Message-ID: <bug-53313-4-FE8D3PETnx@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-53313-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53313

--- Comment #10 from Marc Glisse <glisse at gcc dot gnu.org> ---
Manuel, you seem to want a -Wsuper-extra that you can use everyday (maybe with
a couple -Wno-*). What some other people want with -Weverything is a way to
discover what warnings are available in the compiler. For instance, they
discover a bug or a performance issue in their code, extract a small
reproducer, and want to find if there exists a flag that would help them narrow
down the places they need to review in the rest of their code base for similar
issues. So yes, it should warn all over the place and give contradictory
advice, it should even include the warning that just tells you how large your
function is. As a bonus, this makes it obvious to users that they are not
supposed to make their code -Weverything clean. Maybe the name -Wrant would
make it more acceptable?


  parent reply	other threads:[~2015-04-24 11:59 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-10 22:00 [Bug other/53313] New: " DeusExSophismata at gmail dot com
2012-05-10 22:04 ` [Bug other/53313] " DeusExSophismata at gmail dot com
2012-08-16  3:49 ` david at doublewise dot net
2012-09-30  7:24 ` jan.kratochvil at redhat dot com
2012-09-30 13:16 ` manu at gcc dot gnu.org
2012-12-08 17:59 ` glisse at gcc dot gnu.org
2014-03-17 10:37 ` slyfox at inbox dot ru
2015-04-22 16:13 ` manu at gcc dot gnu.org
2015-04-24  1:16 ` david at doublewise dot net
2015-04-24 10:29 ` manu at gcc dot gnu.org
2015-04-24 11:59 ` glisse at gcc dot gnu.org [this message]
2015-04-24 13:53 ` david at doublewise dot net
2015-04-24 14:22 ` redi at gcc dot gnu.org
2015-04-25 15:10 ` david at doublewise dot net

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=bug-53313-4-FE8D3PETnx@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /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).