[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080306141221.GC5236@dspnet.fr.eu.org>
Date: Thu, 6 Mar 2008 15:12:21 +0100
From: Olivier Galibert <galibert@...ox.com>
To: Paolo Bonzini <bonzini@....org>
Cc: "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 Thu, Mar 06, 2008 at 03:03:15PM +0100, Paolo Bonzini wrote:
> Olivier Galibert 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.
>
> No, the bug *in the kernel* was already present (if you had a signal
> raised during a call to memmove). It's just more visible with GCC 4.3.
I'm curious, since when paper documentation became the Truth and
reality became a bug?
OG.
--
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