public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Cc: libc-alpha@sourceware.org
Subject: Re: [RFC 0/2] Transparent multi-version symbol support
Date: Fri, 19 Mar 2021 20:14:54 +0100	[thread overview]
Message-ID: <87czvvj6q9.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <e3b600df-924b-aec6-f361-07f69b269e1d@linaro.org> (Adhemerval Zanella's message of "Fri, 19 Mar 2021 16:02:35 -0300")

* Adhemerval Zanella:

> The only detail I am not sure is if SYMVER_NEEDS_ALIAS does yields any
> substantial gain (and it require some refactoring and code to handle it).
> What kind of improvement do you expect?

I think it's desirable not to pollute the symbol table if we can avoid
it because debuggers occasionally show the aliases instead of the main
symbol.

Thanks,
Florian


      reply	other threads:[~2021-03-19 19:14 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-18 20:06 Florian Weimer
2021-03-18 20:07 ` [RFC 1/2] Change how the symbol_version_reference macro is defined Florian Weimer
2021-03-19 18:47   ` Adhemerval Zanella
2021-03-18 20:07 ` [RFC 2/2] Fold compat_symbol_unique functionality into compat_symbol Florian Weimer
2021-03-18 21:37   ` Joseph Myers
2021-03-19 18:59   ` Adhemerval Zanella
2021-03-19 19:13     ` Florian Weimer
2021-03-19 19:34       ` Adhemerval Zanella
2021-03-19 20:10     ` Adhemerval Zanella
2021-03-19 20:17       ` Florian Weimer
2021-03-19 20:26         ` Adhemerval Zanella
2021-03-19 20:29           ` Florian Weimer
2021-03-19 20:33             ` Adhemerval Zanella
2021-03-19 20:33             ` Adhemerval Zanella
2021-03-19 19:02 ` [RFC 0/2] Transparent multi-version symbol support Adhemerval Zanella
2021-03-19 19:14   ` Florian Weimer [this message]

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=87czvvj6q9.fsf@oldenburg.str.redhat.com \
    --to=fweimer@redhat.com \
    --cc=adhemerval.zanella@linaro.org \
    --cc=libc-alpha@sourceware.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).