Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1760887AbYCEUwk (ORCPT ); Wed, 5 Mar 2008 15:52:40 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1759891AbYCEUw0 (ORCPT ); Wed, 5 Mar 2008 15:52:26 -0500 Received: from hall.aurel32.net ([88.191.38.19]:46629 "EHLO hall.aurel32.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755177AbYCEUwZ (ORCPT ); Wed, 5 Mar 2008 15:52:25 -0500 Message-ID: <47CF07FE.10200@aurel32.net> Date: Wed, 05 Mar 2008 21:52:14 +0100 From: Aurelien Jarno User-Agent: Mozilla-Thunderbird 2.0.0.9 (X11/20080109) MIME-Version: 1.0 To: "H. Peter Anvin" CC: Michael Matz , Joe Buck , linux-kernel@vger.kernel.org, gcc@gcc.gnu.org Subject: Re: Linux doesn't follow x86/x86-64 ABI wrt direction flag References: <20080305153020.GA24631@volta.aurel32.net> <47CEC3AA.6080709@zytor.com> <20080305195834.GA17267@synopsys.com> <20080305202319.GA17053@volta.aurel32.net> <47CF0627.2070200@zytor.com> In-Reply-To: <47CF0627.2070200@zytor.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1789 Lines: 46 H. Peter Anvin a ?crit : > Michael Matz wrote: >> Hi, >> >> On Wed, 5 Mar 2008, Aurelien Jarno wrote: >> >>>> So I think gcc at least needs an *option* to revert to the old >>>> behavior, >>>> and there's a good argument to make it the default for now, at least >>>> for >>>> x86/x86-64 on Linux. >>> And for other kernels. I tested OpenBSD 4.1, FreeBSD 6.3, NetBSD 4.0, >>> they have the same behaviour as Linux, that is they don't clear DF >>> before calling the signal handler. >> >> Sigh. We could perhaps insert a cld for all functions which can be >> recognized as possible signal handlers and call other unknown or >> string functions. But it's probably even faster to emit cld in front >> of the inline copies of mem functions again :-( >> > > Well, there is a (slight) difference: you know that a called function > will not clobber your DF state; it's only the entry condition which is > imprecise. > > The best would be if this could be controlled by a flag, which we can > flip once kernel fixes has been around for long enough. I have to agree there. Whatever the decision that gcc will take, distributions will reenable the old behaviour for some time for to allow upgrades from a previous version. Providing a flag to switch the behaviour (whatever the default behaviour) will help a lot. -- .''`. Aurelien Jarno | GPG: 1024D/F1BCDB73 : :' : Debian developer | Electrical Engineer `. `' aurel32@debian.org | aurelien@aurel32.net `- people.debian.org/~aurel32 | www.aurel32.net -- 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/