[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b609cb3b0803060737xa0c3c0byb51d51af797eb81f@mail.gmail.com>
Date: Thu, 6 Mar 2008 10:37:21 -0500
From: NightStrike <nightstrike@...il.com>
To: "Olivier Galibert" <galibert@...ox.com>,
"H. Peter Anvin" <hpa@...or.com>,
"Chris Lattner" <clattner@...le.com>,
"Michael Matz" <matz@...e.de>,
"Richard Guenther" <richard.guenther@...il.com>,
"Joe Buck" <Joe.Buck@...opsys.com>, "Jan Hubicka" <hubicka@....cz>,
"Aurelien Jarno" <aurelien@...el32.net>,
linux-kernel@...r.kernel.org, gcc@....gnu.org
Subject: Re: RELEASE BLOCKER: Linux doesn't follow x86/x86-64 ABI wrt direction flag
On 3/6/08, Olivier Galibert <galibert@...ox.com> wrote:
> On Wed, Mar 05, 2008 at 05:12:07PM -0800, H. Peter Anvin wrote:
> > It's a kernel bug, and it needs to be fixed.
>
> I'm not convinced. It's been that way for 15 years, it's that way in
> the BSD kernels, at that point it's a feature. The bug is in the
> documentation, nowhere else. And in gcc for blindly trusting the
> documentation.
The issue should not be evaluated as: "It's always been that way,
therefore, it's right." Instead, it should be: "What's the right way
to do it?"
You don't just change documentation because no existing code meets the
requirement -- UNLESS -- the non-conforming code is actually the right
way to do things.
--
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