[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1288385260.29632.24.camel@gandalf.stny.rr.com>
Date: Fri, 29 Oct 2010 16:47:40 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: "H. Peter Anvin" <hpa@...or.com>
Cc: 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, 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 13:15 -0700, H. Peter Anvin wrote:
> I disagree with that assessment.
>
> We know that if version >= 4.5.2 the problem has been fixed, and that
> for earlier versions we can't know if it's there, so just disable it for
> gcc < 4.5.2. The fix might have been backported, but it's not a big
> deal if the users of backported compilers don't see the full benefit --
> it's only a problem during a limited time window anyway.
>
> Admittedly it would be nice to have a header file or even a
> configuration file where the gcc version is tested and workarounds are
> centralized; then the backporters could put their own overrides in there.
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.
If things turn out fine, we can have > 4.5.2 || run check option. Or
just stick with 4.5.2. But we can debate this later (or at KS if you
want ;-)
-- 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