This is the mail archive of the binutils@sources.redhat.com mailing list for the binutils project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

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

From: Kumar Gala <kumar dot gala at motorola dot com>
To: Eric Christopher <echristo at redhat dot com>
Cc: Matt Thomas <matt at 3am-software dot com>, <binutils at sources dot redhat dot com>
Date: Thu, 27 Feb 2003 22:04:29 -0600
Subject: Re: tagging elf32-ppc objects for FP, AltiVec.

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/~

References:
- Re: tagging elf32-ppc objects for FP, AltiVec.
  - From: Eric Christopher

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]