From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from terminus.zytor.com ([198.137.202.10]:41641 "EHLO terminus.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1762703AbXGTTa1 (ORCPT ); Fri, 20 Jul 2007 15:30:27 -0400 Message-ID: <46A10D12.5000903@zytor.com> Date: Fri, 20 Jul 2007 12:29:22 -0700 From: "H. Peter Anvin" MIME-Version: 1.0 Subject: Re: build fix for x86_64... References: <617E1C2C70743745A92448908E030B2A01FA46A9@scsmsx411.amr.corp.intel.com> <46A0F4AC.50809@zytor.com> <200707202013.03568.ak@suse.de> In-Reply-To: <200707202013.03568.ak@suse.de> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-arch-owner@vger.kernel.org To: Andi Kleen Cc: Andreas Schwab , "Luck, Tony" , Randy Dunlap , Arthur Jones , Vasily Tarasov , linux-kernel@vger.kernel.org, Jan Kara , linux-arch@vger.kernel.org List-ID: 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