Re: tagging elf32-ppc objects for FP, AltiVec.

[Simon Burge <simonb at wasabisystems dot com>]

One area that comes to mind is flagging ABI differences between
soft-float and hard-float objects.  I _think_ the only change is in
varargs/stdargs handling of FP numbers, but it means you can't link
soft-float and hard-float objects together and currently there is no
way to distinguish between the two (that I know of).

I keep meaning to do something about this - thanks for the prod Matt.

Simon.
--
Simon Burge                            <simonb at wasabisystems dot com>
NetBSD Support and Service:         http://www.wasabisystems.com/

Kumar Gala wrote:

> This was what the APU sections put into binaries for spe do.It could
> be extended for the other types you mentioned.Adds a new section
> .apuinfo (or something like that).
> 
> There is some issue with the fact that opcodes between AltiVec and SPE
> overlap and its valid for an executable to have both in them, if it had
> some runtime detection to know what processor its running on.
> 
> What were you thinking you would use the functionality for?
> 
> - kumar
> 
> On Thursday, February 27, 2003, at 09:05 PM, Eric Christopher wrote:
> 
> > On Thu, 2003-02-27 at 19:06, Matt Thomas wrote:
> >> It would be nice if powerpc ELF objects could have flags set
> >> to reflect if they contain AltiVec instructions and/or what
> >> type of floating point it uses (none, std, soft, spe, etc.),
> >> include PPC64 instructions, etc.
> >>
> >
> > Sounds good to me, but hopefully a PPC person will pipe up. :)
> >
> > -eric
> >
> > --
> > o/~ Cry havoc... o/~
>