From: Michael Ellerman <michael@ellerman.id.au>
To: Tony Breeds <tony@bakeyournoodle.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] Quieten arch/powerpc in a allmodconfig build.
Date: Wed, 08 Apr 2009 16:23:02 +1000 [thread overview]
Message-ID: <1239171783.10104.31.camel@localhost> (raw)
In-Reply-To: <20090408061352.GH16602@bilbo.ozlabs.org>
[-- Attachment #1: Type: text/plain, Size: 847 bytes --]
On Wed, 2009-04-08 at 16:13 +1000, Tony Breeds wrote:
> On Wed, Apr 08, 2009 at 03:51:26PM +1000, Tony Breeds wrote:
>
> > Hmm actually I think you're right. I dont want to push my luck with the gcc
> > hackers though
>
> Replying to myself.
>
> Yes this is a gcc bug but one introduced by CONFIG_TRACE_ALL_BRANCHES (or
> whatever that's called).
CONFIG_MAKE_MY_KERNEL_SUCK I think it is.
In that case I don't blame gcc.
If people want to use that option I think they can just deal with the
warnings, we can make -Werror depend on !CONFIG_PROFILE_ALL_BRANCHES.
cheers
--
Michael Ellerman
OzLabs, IBM Australia Development Lab
wwweb: http://michael.ellerman.id.au
phone: +61 2 6212 1183 (tie line 70 21183)
We do not inherit the earth from our ancestors,
we borrow it from our children. - S.M.A.R.T Person
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-04-08 6:23 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-08 4:36 [PATCH] Quieten arch/powerpc in a allmodconfig build Tony Breeds
2009-04-08 5:08 ` Michael Ellerman
2009-04-08 5:51 ` Tony Breeds
2009-04-08 6:13 ` Tony Breeds
2009-04-08 6:23 ` Michael Ellerman [this message]
2009-04-08 6:48 ` Michael Ellerman
2009-04-08 7:42 ` Geert Uytterhoeven
2009-04-08 18:47 ` Nathan Lynch
2009-04-09 0:01 ` Tony Breeds
2009-04-10 4:21 ` Nathan Lynch
2009-04-10 17:19 ` Segher Boessenkool
2009-04-09 22:46 ` Segher Boessenkool
2009-04-09 22:45 ` Tony Breeds
2009-04-09 23:11 ` Stephen Rothwell
2009-04-09 23:23 ` Segher Boessenkool
2009-04-10 18:03 ` Scott Wood
2009-04-10 18:35 ` Andreas Schwab
2009-04-10 18:43 ` Scott Wood
2009-04-10 20:28 ` Segher Boessenkool
2009-04-10 20:45 ` Segher Boessenkool
2009-04-10 21:51 ` Scott Wood
2009-04-09 23:18 ` Segher Boessenkool
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=1239171783.10104.31.camel@localhost \
--to=michael@ellerman.id.au \
--cc=linuxppc-dev@ozlabs.org \
--cc=tony@bakeyournoodle.com \
/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 NNTP newsgroup(s).