[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <47D012B4.3020104@zytor.com>
Date: Thu, 06 Mar 2008 07:50:12 -0800
From: "H. Peter Anvin" <hpa@...or.com>
To: "H.J. Lu" <hjl.tools@...il.com>
CC: 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
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.
No, I believe the right way to approach this is by applying the good
old-fashioned principle from Ask Mr. Protocol:
Be liberal in what you receive, conservative in what you send
In other words:
a. Fix the kernel. Already in progress.
b. Do *not* make gcc assume DF is clean for now. Adding a
switch would be a useful thing, since if nothing else it
would benefit embedded environments. We might assume
DF is clean on 64 bits, since it appears it is rarely used
anyway, and 64 bits is more important in the long run.
c. Once fixed kernels have been out long enough, we can
flip the default of the switch, one platform at a time if
need be (e.g. there may never be another SCO OpenServer.)
-hpa
--
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