[rfc] declaring new object format "FDPIC ELF"

[Mike Frysinger]

On Monday 21 April 2008, Daniel Jacobowitz wrote:
> On Mon, Apr 21, 2008 at 06:07:03PM -0400, Mike Frysinger wrote:
> > what i'd like to do is promote FDPIC ELF as an object format so that we
> > can do the default target binding based on tuple and in the configure
> > scripts rather than having this logic in the source code.
>
> Why's this better than the way it is now?  For SH (in progress) we
> have an assembler option and linker emulation, and GCC does the right
> thing based on how it was configured; it's not particularly complicated.

the linker is a different story as it already supports the ability to select 
specific bfd targets based on tuples.  it also can analyze the incoming elf 
headers and look at the elf flags to see whether the object is FDPIC or not 
and so transparently select the appropriate bfd.  gas cannot do either of 
these things.

what i have a problem with is this:
 - bfin-uclinux-{gcc,as,ld} produces elf without users having to do anything
 - bfin-linux-uclibc-{gcc,ld} produces fdpic without users having to do 
anything
 - bfin-linux-uclibc-as produces elf if user doesnt do anything which means 
any linking steps bombs out with ugly/confusing binary format mismatches
 - if you want to execute bfin-linux-uclibc-as directly, you need to 
explicitly specify "-mfdpic"
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 827 bytes
Desc: This is a digitally signed message part.
URL: <https://sourceware.org/pipermail/binutils/attachments/20080421/28f1de58/attachment.sig>