mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Dave Jones <davej@redhat.com>, Joe Perches <joe@perches.com>,
	David Daney <ddaney@caviumnetworks.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	BorislavPetkov <bp@alien8.de>
Subject: Re: annoying new gcc 4.6.0 warnings.
Date: Thu, 21 Apr 2011 13:09:11 -0700	[thread overview]
Message-ID: <BANLkTinWV_OriM0mdoVdKWZNHhEUUmWDog@mail.gmail.com> (raw)
In-Reply-To: <20110421195801.GA15126@redhat.com>

On Thu, Apr 21, 2011 at 12:58 PM, Dave Jones <davej@redhat.com> wrote:
> @@ -359,7 +359,8 @@ KBUILD_CFLAGS   := -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs \
>                   -fno-strict-aliasing -fno-common \
>                   -Werror-implicit-function-declaration \
>                   -Wno-format-security \
> -                  -fno-delete-null-pointer-checks
> +                  -fno-delete-null-pointer-checks \
> +                  -Wno-unused-but-set-variable

Does this work ok for older gcc's? Do they understand that
-Wno-unused-by-set-variable?

gcc-4.5.1 seems to understand it, but what about much older gccs?

                 Linus

  parent reply	other threads:[~2011-04-21 20:09 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-21 19:21 Dave Jones
2011-04-21 19:24 ` Linus Torvalds
2011-04-21 19:39   ` David Daney
2011-04-21 19:44     ` Joe Perches
2011-04-21 19:58       ` Dave Jones
2011-04-21 20:08         ` Sam Ravnborg
2011-04-21 20:27           ` Dave Jones
2011-04-21 20:37             ` David Daney
2011-04-21 20:45               ` Dave Jones
2011-04-21 20:56                 ` Sam Ravnborg
2011-04-21 21:28                   ` Dave Jones
2011-04-21 21:42                     ` Sam Ravnborg
2011-04-29 15:02                     ` Michal Marek
2011-04-21 20:09         ` Linus Torvalds [this message]
2011-04-21 20:15           ` Dave Jones
2011-04-21 20:30 ` Stratos Psomadakis
2011-04-21 21:10   ` Sam Ravnborg

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=BANLkTinWV_OriM0mdoVdKWZNHhEUUmWDog@mail.gmail.com \
    --to=torvalds@linux-foundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=bp@alien8.de \
    --cc=davej@redhat.com \
    --cc=ddaney@caviumnetworks.com \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®