public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Russ Allbery <rra@stanford.edu>
To: gcc@gcc.gnu.org
Subject: Re: comparisons..
Date: Thu, 13 Jul 2000 15:14:00 -0000	[thread overview]
Message-ID: <yllmz5ad9j.fsf@windlord.stanford.edu> (raw)
In-Reply-To: <200007131609.JAA17272@racerx.synopsys.com>

Joe Buck <jbuck@racerx.synopsys.com> writes:
> Andrew Morton wrote:

>> Please, give us more granular control over the -W warnings!!

> Could you be more specific?  Which warnings do you want to enable and
> suppress?  There's already a large set of -Wxxx and -Wno-xxx flags.
> What's missing?

The one that I've specifically noticed is the following:  I want most of
the -W warnings and I want all of the -Wall warnings, but I specifically
don't want warnings about unused function parameters for some code
(particularly code that uses a large table of functions to handle
commands, some of which don't care about their arguments) since it's often
too much bother to tag all the unused parameters with gcc-specific
attributes.  I *do* want warnings about unused variables.

-Wall -W gives warnings about both unused variables and unused function
parameters.  -Wall -W -Wno-unused suppresses both.  I can't find a more
finely grained knob to turn.

(Apologies if this is already fixed in the mainline.)

-- 
Russ Allbery (rra@stanford.edu)             < http://www.eyrie.org/~eagle/ >

  parent reply	other threads:[~2000-07-13 15:14 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-12 22:58 comparisons Andrew Morton
2000-07-12 23:35 ` comparisons Michael Meissner
2000-07-12 23:48   ` comparisons Andrew Morton
2000-07-12 23:57     ` comparisons Michael Meissner
2000-07-13  0:24       ` comparisons Andrew Morton
2000-07-13  1:05         ` comparisons Nick Burrett
2000-07-13  1:47           ` comparisons Andrew Morton
2000-07-13  9:12             ` comparisons Joe Buck
2000-07-13 14:48               ` comparisons Andi Kleen
2000-07-13 21:46               ` comparisons Andrew Morton
2000-07-13  0:24     ` comparisons Martin v. Loewis
2000-07-13  1:09       ` comparisons Andrew Morton
2000-07-13  1:36         ` comparisons Nick Burrett
2000-07-13  1:47           ` comparisons Andrew Morton
2000-07-13  6:39         ` comparisons Andrew Morton
2000-07-13  9:11           ` comparisons Joe Buck
2000-07-13  9:45             ` comparisons Bruce Korb
2000-07-13 10:32               ` comparisons Joe Buck
2000-07-13 15:14             ` Russ Allbery [this message]
2000-07-13 17:11               ` comparisons Philipp Thomas
2000-07-28  5:48           ` comparisons Nix
2000-07-13  9:44         ` comparisons Gerald Pfeifer
2000-07-13 17:12           ` comparisons Andrew Morton
2000-07-13 17:30             ` comparisons Russ Allbery
2000-07-13 17:48               ` comparisons Michael Meissner
2000-07-14  4:22             ` comparisons Toon Moene
2000-07-14 10:57               ` comparisons Richard Henderson
2000-07-14 12:43                 ` comparisons Toon Moene
2000-07-14 12:52                   ` comparisons Richard Henderson
2000-07-14 13:53                     ` comparisons Toon Moene
2000-07-14 14:00               ` comparisons Martin v. Loewis
2000-07-15 17:35               ` comparisons Joe Buck
2000-07-12 23:54 ` comparisons Martin v. Loewis
2000-07-13 10:09 comparisons Phil Edwards
2000-07-13 11:18 ` comparisons Michael Meissner

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=yllmz5ad9j.fsf@windlord.stanford.edu \
    --to=rra@stanford.edu \
    --cc=gcc@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).