From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from cantor.suse.de ([195.135.220.2]:59129 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1765785AbXGTRkr (ORCPT ); Fri, 20 Jul 2007 13:40:47 -0400 From: Andreas Schwab Subject: Re: build fix for x86_64... References: <617E1C2C70743745A92448908E030B2A01FA46A9@scsmsx411.amr.corp.intel.com> <46A0EAC8.9020203@zytor.com> Date: Fri, 20 Jul 2007 19:40:44 +0200 In-Reply-To: <46A0EAC8.9020203@zytor.com> (H. Peter Anvin's message of "Fri\, 20 Jul 2007 10\:03\:04 -0700") Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: linux-arch-owner@vger.kernel.org To: "H. Peter Anvin" Cc: "Luck, Tony" , Randy Dunlap , Andi Kleen , Arthur Jones , Vasily Tarasov , linux-kernel@vger.kernel.org, Jan Kara , linux-arch@vger.kernel.org List-ID: "H. Peter Anvin" writes: > No, that would be bad. If compat_u64 is used to carry 32-bit ABIs > forward into 64-bit space without needing compatibility hacks, then this > would actually introduce ABI incompatibilities depending on CONFIG_COMPAT! But without CONFIG_COMPAT there is no 32-bit ABI, thus no need for compat_u64 in the first place. Andreas. -- Andreas Schwab, SuSE Labs, schwab@suse.de SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany PGP key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different."