[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <19e566510803060827u4c698f56l6c0faae71068588d@mail.gmail.com>
Date: Thu, 6 Mar 2008 18:27:15 +0200
From: "İsmail Dönmez" <ismail@...trac.org>
To: "Jakub Jelinek" <jakub@...hat.com>
Cc: "H. Peter Anvin" <hpa@...or.com>, "H.J. Lu" <hjl.tools@...il.com>,
NightStrike <nightstrike@...il.com>,
"Olivier Galibert" <galibert@...ox.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
Hi,
On Thu, Mar 6, 2008 at 6:23 PM, Jakub Jelinek <jakub@...hat.com> wrote:
> On Thu, Mar 06, 2008 at 07:50:12AM -0800, H. Peter Anvin wrote:
> > H.J. Lu wrote:
> > >I agree with it. There is no right or wrong here Let's start from
> > >scratch and figure out
> > >what is the best way to handle this, assuming we are defining a new psABI.
>
> BTW, just tested icc and icc doesn't generate cld either (so it matches the
> new gcc behavior).
> char buf1[32], buf2[32];
> void bar (void);
> void foo (void)
> {
> __builtin_memset (buf1, 0, 32);
> bar ();
> __builtin_memset (buf2, 0, 32);
> }
Also LKML discussion pointed out that Solaris gets this right too.
Regards,
ismail
--
Never learn by your mistakes, if you do you may never dare to try again.
--
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