From: Siddhesh Poyarekar <siddhesh@gotplt.org>
To: Fangrui Song <maskray@google.com>, libc-alpha@sourceware.org
Subject: Re: [PATCH 0/3] Allow LLD 13.0.0 and improve compatibility with gold and clang
Date: Mon, 2 Aug 2021 09:53:34 +0530 [thread overview]
Message-ID: <59f951bb-3772-535b-e605-35958dbd27f4@gotplt.org> (raw)
In-Reply-To: <a465b8a2-2f1b-cd6e-01ce-dd5936887265@gotplt.org>
On 8/2/21 9:32 AM, Siddhesh Poyarekar wrote:
> The entire point of link time deprecation is to not emit a @@ symbol. If
> lld emits __free_hook@@GLIBC_2.2.5 in this case then this needs to be
> resolved. How does one do symbol deprecation in lld?
Sorry I just realized that you may have implied that having a .globl in
the object file ought to be sufficient to indicate that the symbol needs
to be exported. The glibc linker script however overrides this with
{local: *} and if the linker doesn't honour that then ISTM that this
ought to be a bug in the linker. ld.bfd always gives preference to the
linker script over symbol definitions in source and it seems like a
simpler and more consistent rule.
Siddhesh
next prev parent reply other threads:[~2021-08-02 4:23 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-26 3:57 Fangrui Song
2021-07-26 3:58 ` [PATCH 1/3] elf: Replace .tls_common with .tbss definition Fangrui Song
2021-07-29 14:26 ` H.J. Lu
2021-07-29 16:21 ` Fangrui Song
2021-07-26 3:58 ` [PATCH 2/3] elf: Skip tst-auditlogmod-* if the linker doesn't support --depaudit Fangrui Song
2021-07-29 14:23 ` H.J. Lu
2021-07-29 16:28 ` Fangrui Song
2021-07-26 3:58 ` [PATCH 3/3] configure: Allow LD to be LLD 13.0.0 or above Fangrui Song
2021-07-28 18:02 ` [PATCH 0/3] Allow LLD 13.0.0 and improve compatibility with gold and clang H.J. Lu
2021-07-28 21:52 ` Fangrui Song
2021-07-29 14:45 ` H.J. Lu
2021-07-30 7:57 ` Florian Weimer
2021-07-31 6:34 ` Fāng-ruì Sòng
2021-07-31 6:41 ` Florian Weimer
2021-08-02 20:55 ` Fāng-ruì Sòng
2021-08-02 4:02 ` Siddhesh Poyarekar
2021-08-02 4:23 ` Siddhesh Poyarekar [this message]
2021-08-08 16:50 ` Fāng-ruì Sòng
2021-08-08 2:54 ` Fāng-ruì Sòng
2021-08-08 16:45 ` Siddhesh Poyarekar
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=59f951bb-3772-535b-e605-35958dbd27f4@gotplt.org \
--to=siddhesh@gotplt.org \
--cc=libc-alpha@sourceware.org \
--cc=maskray@google.com \
/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).