From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail.pbcl.net ([88.198.119.4] helo=hetzner.pbcl.net) by linuxtogo.org with esmtp (Exim 4.72) (envelope-from ) id 1QpMb5-0001L6-P0 for openembedded-core@lists.openembedded.org; Fri, 05 Aug 2011 17:46:04 +0200 Received: from cambridge.roku.com ([81.142.160.137] helo=[172.30.1.145]) by hetzner.pbcl.net with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from ) id 1QpMWp-0005iE-IP for openembedded-core@lists.openembedded.org; Fri, 05 Aug 2011 17:41:39 +0200 From: Phil Blundell To: Patches and discussions about the oe-core layer Date: Fri, 05 Aug 2011 16:41:38 +0100 In-Reply-To: <9DA5872FEF993D41B7173F58FCF6BE94DE85F892@orsmsx504.amr.corp.intel.com> References: <2c351319afd13acfca1283104172729925cfb696.1312469790.git.nitin.a.kamble@intel.com> <1312495032.3169.6.camel@lenovo.internal.reciva.com> <9DA5872FEF993D41B7173F58FCF6BE94DE85F4F7@orsmsx504.amr.corp.intel.com> <1312530654.3169.12.camel@lenovo.internal.reciva.com> <9DA5872FEF993D41B7173F58FCF6BE94DE85F892@orsmsx504.amr.corp.intel.com> X-Mailer: Evolution 3.0.2- Message-ID: <1312558899.6733.23.camel@phil-desktop> Mime-Version: 1.0 Subject: Re: [PATCH 09/10] x86 tune inc files: add x32 abi tune parameters X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.11 Precedence: list Reply-To: Patches and discussions about the oe-core layer List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Aug 2011 15:46:04 -0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit On Fri, 2011-08-05 at 08:37 -0700, Kamble, Nitin A wrote: > Changing TARGET_ARCH is not correct way to handle it. Because HW/ARCH is > not different, the difference is in the ABI of the OS. Well, I'm not entirely sure I agree with what you're saying here. There are at least a few precedents for encoding ABI details (eg hardfloat parameter passing, endianness) into TARGET_ARCH, and it seems to me that they belong there more naturally than in TARGET_OS. p.