[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1288447219.29632.53.camel@gandalf.stny.rr.com>
Date: Sat, 30 Oct 2010 10:00:19 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Andi Kleen <andi@...stfloor.org>
Cc: "H. Peter Anvin" <hpa@...or.com>,
David Daney <ddaney@...iumnetworks.com>,
Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca>,
Ingo Molnar <mingo@...e.hu>, Jason Baron <jbaron@...hat.com>,
rth@...hat.com, tglx@...utronix.de, roland@...hat.com,
masami.hiramatsu.pt@...achi.com, fweisbec@...il.com,
avi@...hat.com, davem@...emloft.net, vgoyal@...hat.com,
sam@...nborg.org, tony@...eyournoodle.com, dsd@...top.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/2] jump label: disable due to compiler bug
On Sat, 2010-10-30 at 09:47 +0200, Andi Kleen wrote:
> > Fine, but we can wait till 2.6.38 for that. For now we have a manual
> > config option. I'm not changing it until I have 4.5.2 in my distcc farm
> > and testing it out.
>
> It's probably obvious, but a manual config option still breaks
> the allyes|modconfig crowd.
Enabling the config only adds the workaround which causes the kernel to
be a bit bigger (adds -maccumulate-outgoing-args) and does not break the
kernel. When we have the test, we wont need to add this workaround if
the test passes.
This is still a new feature, and until we are sure its safe, we should
have it as an option.
There's lots of things in the kernel that will break with
all{yes,mod}config. I know, because I keep hitting them with my
randconfig tests.
-- Steve
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists