This is the mail archive of the binutils@sourceware.org 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] |
On Thursday, December 09, 2010 16:42:59 Joseph S. Myers wrote: > On Thu, 9 Dec 2010, Mike Frysinger wrote: > > The default language in version scripts is supposed to be C, but no > > symbol demangling is performed on the symbols by default. This makes > > targets with a symbol prefix to fail with most version scripts out > > there. So strip away this prefix by default. > > > > This fixes many tests (real world and ld's testsuite) for Blackfin > > targets and doesn't seem to cause regressions for x86_64. > > Blackfin has its own libgcc version script in GCC that duplicates the > standard script precisely because of the leading underscores. yes, i already have a patch in our local gcc copy to move Blackfin to the standard and drop most of our local changes. but i need the linker working before i can push that. > 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 ? -mike
Attachment:
signature.asc
Description: This is a digitally signed message part.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |