Re: armelfp: new architecture name for an armel variant

[Andrew Stubbs <ams@codesourcery.com>]

On 09/07/10 19:16, Hector Oron wrote:
>    arm-hardfloat-linux-gnueabi

This would be the path of least resistance. You can do this without 
breaking much, and without annoying anybody upstream. You might need to 
do a few hacks to various packages that want to know which ABI is in 
use, but probably somebody would have to port these anyway.

>    armhf-linux-gnueabi

This is wrong. The processor has not changed, and you'd have to handle 
armv7hf- and many others. Ugh.

It's the OS part of the triplet that indicates binary compatibility, so 
the "proper" way to do it would be something like:

   arm-linux-gnueabihf

Of course, if you want to do it "properly", you need to get upstream 
approval first, or else you'll find yourself hung out to dry.

Also, if a toolchain supports multiple ABIs (such as CodeSourcery SG++ 
does), then the correct triplet would be whichever is the default 
configuration.

Linaro are also interested in having hard-FP, so they have asked me to 
start the discussion upstream and get a name agreed.

Andrew Stubbs
CodeSourcery (currently working with Linaro)