public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Darren Hart <dvhart@linux.intel.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Bruce Ashfield <bruce.ashfield@windriver.com>
Subject: Re: [PATCH] perf: fix gcc4.6 build failure with unused-but-set warning
Date: Fri, 3 Jun 2011 09:41:00 +0200	[thread overview]
Message-ID: <20110603074100.GA16694@elte.hu> (raw)
In-Reply-To: <8a0acb368eef010fd2eb2e889e2c62d91bd8a918.1307047668.git.dvhart@linux.intel.com>


* Darren Hart <dvhart@linux.intel.com> wrote:

> This patch creates a new perf/Makefile variable, LESS_WARNINGS and 
> adds -Wno-unused-but-set-variable. The new variable helps 
> distinguish between the added warnings in EXTRA_WARNINGS versus 
> those we want to remove, including the existing -Wno-system-headers 
> which I moved to LESS_WARNINGS.

Btw., while you resolved the issue, it would nevertheless nice to 
introduce a 'make WERROR=0' build method that removes -Werror.

Would you be interested in sending a patch for that?

There would be several advantages of such a patch:

 - GCC often introduces new warnings with lots of false positives - 
   breaking -Werror builds. WERROR=0 would allow one to build perf 
   without much fuss - while people would still send patches to avoid 
   the fuss of having to type WERROR=0 :-)

 - bisecting back to commits that produce a (mostly harmless) warning 
   on some compiler is more difficult. With WERROR=0 one could bisect 
   without worrying about harmless warnings.

Thanks,

	Ingo

      parent reply	other threads:[~2011-06-03  7:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-02 20:47 [PATCH] perf: fix gcc4.6 build failure with unused-but-set warning Darren Hart
2011-06-02 21:27 ` Darren Hart
2011-06-03  7:41 ` Ingo Molnar [this message]

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=20110603074100.GA16694@elte.hu \
    --to=mingo@elte.hu \
    --cc=bruce.ashfield@windriver.com \
    --cc=dvhart@linux.intel.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