[PATCH] bfd/ld: handle ABI prefixes in version scripts

[Mike Frysinger]

On Friday, December 10, 2010 18:03:52 Mike Frysinger wrote:
> On Friday, December 10, 2010 05:43:47 Joseph S. Myers wrote:
> > On Thu, 9 Dec 2010, Mike Frysinger wrote:
> > > > So it would seem you need to coordinate this change in some way with
> > > > GCC, if I understand it correctly - possibly making GCC 4.6 for
> > > > Blackfin require a new linker and replacing the duplicate version
> > > > script with one just defining the two Blackfin-specific symbols. 
> > > > That doesn't solve the problem with old GCC and new linkers, though
> > > > you could add a configure test to 4.3/4.4/4.5 release branches to
> > > > reject new linkers for Blackfin.
> > > 
> > > are there any examples of binutils version checking that i can look at
> > > basing the work on ?
> > 
> > There are lots of assembler checks that deal with various combinations of
> > checking a version number (possibly for a unified tree build) and
> > checking for features; see gcc_GAS_CHECK_FEATURE.
> 
> seems like gcc_GAS_VERSION_GTE_IFELSE should do what i want.  these checks
> ok to put into gcc/config.gcc ?  that's where all the blackfin-specific
> logic is found currently, but doesnt seem like any other targets run any
> sort of tests in that file -- they seem to be in configure.ac.

i found the right place in configure.ac (there's a "target specific checks" 
section), but i dont think these gas m4 macros are useful.  the version 
checking only works when the gas used is in tree, and this functionality cant 
be detected at the assembler level.  my fixes are only at the linker level, 
but there doesnt appear to be any linker helper checks that i can see.  so i'd 
have to do a link test with a custom version script (and hardcoded -Wl flags), 
and then do a review of the output (via readelf or nm).  which makes me think 
adding a configure test isnt really worth all the effort.
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
URL: <https://sourceware.org/pipermail/binutils/attachments/20101213/a3921b9e/attachment.sig>