[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <46A10D12.5000903@zytor.com>
Date: Fri, 20 Jul 2007 12:29:22 -0700
From: "H. Peter Anvin" <hpa@...or.com>
To: Andi Kleen <ak@...e.de>
CC: Andreas Schwab <schwab@...e.de>,
"Luck, Tony" <tony.luck@...el.com>,
Randy Dunlap <randy.dunlap@...cle.com>,
Arthur Jones <arthur.jones@...gic.com>,
Vasily Tarasov <vtaras@...nvz.org>,
linux-kernel@...r.kernel.org, Jan Kara <jack@....cz>,
linux-arch@...r.kernel.org
Subject: Re: build fix for x86_64...
Andi Kleen wrote:
>> Obviously, this is not a panacea; if the original "struct foo" has also
>> been introduced on 64 bits before the bug is caught,
>
> That's usually the case. There is already an established 64bit ABI
>
This is true.
Kind of makes me wonder if the right thing is to introduce an
"interface" 64-bit type, call it __iu64 (__is64) defined as:
typedef __u64 __attribute__((aligned(8))) __iu64;
typedef __s64 __attribute__((aligned(8))) __is64;
... and encourage people to use it when creating new interfaces.
Don't know if that would do any good.
-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