[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1288375386.29632.12.camel@gandalf.stny.rr.com>
Date: Fri, 29 Oct 2010 14:03:06 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: David Daney <ddaney@...iumnetworks.com>
Cc: Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca>,
Ingo Molnar <mingo@...e.hu>, Jason Baron <jbaron@...hat.com>,
rth@...hat.com, "H. Peter Anvin" <hpa@...or.com>,
tglx@...utronix.de, andi@...stfloor.org, 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 Fri, 2010-10-29 at 10:48 -0700, David Daney wrote:
> The test case is in the GCC bug report, and is quite small:
>
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46226
>
> Perhaps it could be integrated with the current checks for the presence
> of 'asm goto'
Yeah, but it's too late in the merge window to do this much hackery.
Lets slow down a bit and do it right. This test case shows that gcc is
broken, but do we really know if it wont produce a false positive
(saying gcc works when it does not)?
Adding a manual option for this release is the right thing to do. This
will let things settle down. Users that want it can enable it
themselves, and then they choose to be our testers ;-)
Once we have a better idea on things and have a test case we know shows
gcc works when it really does work and that it fails when it really does
fail, then we can add that in. Perhaps for 38.
-- 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