public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Will Newton <will.newton@gmail.com>
To: Mike Frysinger <vapier@gentoo.org>
Cc: Ian Lance Taylor <iant@google.com>, binutils@sourceware.org
Subject: Re: version scripts and default/C language mangling
Date: Tue, 17 Aug 2010 11:11:00 -0000	[thread overview]
Message-ID: <AANLkTinywayduWsc11TF5zLWKRuuPSxB-5dHqFJtFw4d@mail.gmail.com> (raw)
In-Reply-To: <201007191931.02766.vapier@gentoo.org>

On Tue, Jul 20, 2010 at 12:31 AM, Mike Frysinger <vapier@gentoo.org> wrote:
> On Monday, July 12, 2010 04:05:02 Ian Lance Taylor wrote:
>> Mike Frysinger writes:
>> > first, i'm asking what the default language is for the version script.
>> > i'd expect the answer to be "no language" which means the symbols would
>> > be matched against any random leading char a target introduces.  i'm
>> > also OK with the answer "C language", although it does prevent working
>> > with symbols that lack the prefix char because they were created via
>> > assembly code.
>>
>> The default language is "C".  I think the right thing to do in that case
>> is strip the leading character if present, and otherwise do nothing.
>> That is what bfd_demangle does.
>
> works for me
>
>> > yes, but presumably changing ldlang.c to consider that value is
>> > unacceptable. the current parsing code is also not given the current
>> > bfd, only bfd_elf_version_expr structures, and those dont contain links
>> > back to a bfd that i can see.  unless there is a way to get the current
>> > "active" bfd ?  then it should be easy to drop in support in
>> > lang_vers_match() with the function bfd_get_symbol_leading_char() you
>> > pointed out.
>>
>> I think it would be entirely reasonable to change lang_vers_match to
>> take a BFD parameter, and change the corresponding calling code in
>> bfd/elflink.c.  Or, the output BFD is always available in
>> link_info.output_bfd.
>
> since the existing bfd_demangle user in this file is using
> link_info.output_bfd, i'm going to roll with that.
>
> how does the attached patch look ?  seems to fix things with Blackfin targets,
> and no regressions are seen with x86_64-linux-gnu and bfin-linux-uclibc.
>
> i'll do some more system wide testing in the mean time ...

Hi Mike,

Did this patch pass your testing?

I would be interested in trying it out but it would appear that the
patch you sent has been mangled by Exchange (= characters everywhere).

Cheers,

  parent reply	other threads:[~2010-08-17 10:16 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-06 20:03 Mike Frysinger
2010-07-11 11:57 ` Ian Lance Taylor
2010-07-11 22:07   ` Mike Frysinger
2010-07-12  8:05     ` Ian Lance Taylor
2010-07-19 23:34       ` Mike Frysinger
2010-07-22  2:26         ` Alan Modra
2010-08-17 11:11         ` Will Newton [this message]
2010-08-17 12:42           ` Mike Frysinger
2010-12-09 20:56 ` [PATCH] bfd/ld: handle ABI prefixes in version scripts Mike Frysinger
2010-12-09 21:43   ` Joseph S. Myers
2010-12-10  3:52     ` Mike Frysinger
2010-12-10 10:45       ` Joseph S. Myers
2010-12-10 22:04         ` Mike Frysinger
2010-12-13 19:40           ` Mike Frysinger
2010-12-13 23:15             ` Joseph S. Myers
2010-12-14  0:44               ` Mike Frysinger
2011-01-14  0:33   ` Mike Frysinger
2011-02-14  5:19     ` Mike Frysinger
2011-02-14  6:07   ` Alan Modra
2011-02-14 17:11     ` Mike Frysinger

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=AANLkTinywayduWsc11TF5zLWKRuuPSxB-5dHqFJtFw4d@mail.gmail.com \
    --to=will.newton@gmail.com \
    --cc=binutils@sourceware.org \
    --cc=iant@google.com \
    --cc=vapier@gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).