Re: cortex / arm-hardfloat-linux-gnueabi (was Re: armelfp: new architecture name for an armel variant)
> On 7/15/10, Loïc Minier <firstname.lastname@example.org> wrote:
> > armel can also use vfp instructions, so I personally find it confusing.
> No it can't. Any binary that contains a vfp instruction will die with
> SIGILL on any armv4t chip that has no vfp cpu, so cannot be used in
> Debian armel.
Yes, however fixing this this does not require a new port. It only requires
providing alternative packages builds within the same port. The important
point being that (assuming capable hardware) you can freely mix the two.
> > (BTW in the thread Richard Earnshaw makes the point that FPA isn't
> > leagel in EABI and that maverick is incompatible with it, so I think
> > this is another reason not to have "vfp" in our new port's name)
> You must have misunderstood what Richard said.
> I use Maverick hardlfoat in EABI and provide a repository of Maverick
> hardfloat debian packages for Debian armel. It all works fine.
Until someone makes to the effort to define proper EABI supplements for that
coprocessor, I think it's reasonable to call this "not EABI".