[OE-core] [PATCH 09/10] x86 tune inc files: add x32 abi tune parameters

Richard Purdie richard.purdie at linuxfoundation.org
Fri Aug 5 15:44:22 UTC 2011


On Fri, 2011-08-05 at 16:41 +0100, Phil Blundell wrote:
> 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.

Equally, there are several precedents for encoding ABI into TARGET_OS,
arm-gnueabi springs to mind...

It really comes down to the formats that the various magic files accept
and whilst its the regexps are lax on arm, they are less lax on x86 and
I suspect the TARGET_OS path is the one of less resistance in this case.

Even so, it shouldn't be necessary to change the default TARGET_OS.

Cheers,

Richard





More information about the Openembedded-core mailing list