Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933748AbYCFROo (ORCPT ); Thu, 6 Mar 2008 12:14:44 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754378AbYCFROJ (ORCPT ); Thu, 6 Mar 2008 12:14:09 -0500 Received: from terminus.zytor.com ([198.137.202.10]:39621 "EHLO terminus.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752327AbYCFROH (ORCPT ); Thu, 6 Mar 2008 12:14:07 -0500 Message-ID: <47D024AA.9010300@zytor.com> Date: Thu, 06 Mar 2008 09:06:50 -0800 From: "H. Peter Anvin" User-Agent: Thunderbird 2.0.0.12 (X11/20080226) MIME-Version: 1.0 To: "H.J. Lu" CC: Jakub Jelinek , NightStrike , Olivier Galibert , Chris Lattner , Michael Matz , Richard Guenther , Joe Buck , Jan Hubicka , Aurelien Jarno , linux-kernel@vger.kernel.org, gcc@gcc.gnu.org Subject: Re: RELEASE BLOCKER: Linux doesn't follow x86/x86-64 ABI wrt direction flag References: <738B72DB-A1D6-43F8-813A-E49688D05771@apple.com> <2F47E21A-9055-4EC3-99CF-B666BBC045C3@apple.com> <47CF3F09.4080606@zytor.com> <578FCA7D-D7A6-44F6-9310-4A97C13CDCBE@apple.com> <47CF44E7.3020106@zytor.com> <20080306135139.GA5236@dspnet.fr.eu.org> <6dc9ffc80803060743h502fc96bj6117ef87a8555c3a@mail.gmail.com> <47D012B4.3020104@zytor.com> <20080306162353.GF24887@devserv.devel.redhat.com> <6dc9ffc80803060858i7d4e8b56o99ff8ad301a5cc1a@mail.gmail.com> In-Reply-To: <6dc9ffc80803060858i7d4e8b56o99ff8ad301a5cc1a@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1062 Lines: 33 H.J. Lu wrote: > On Thu, Mar 6, 2008 at 8:23 AM, Jakub Jelinek 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); >> } >> > > Icc follows the psABI. If we are saying icc/gcc 4.3 need a fix, we'd > better define > a new psABI first. > Not a fix, an (optional) workaround for a system bug. -hpa -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/