From: Florian Weimer <fweimer@redhat.com>
To: Joseph Myers <joseph@codesourcery.com>
Cc: Fangrui Song <maskray@google.com>, <libc-alpha@sourceware.org>,
Adhemerval Zanella <adhemerval.zanella@linaro.org>
Subject: Re: [PATCH] elf: Add __libc_get_static_tls_bounds [BZ #16291]
Date: Mon, 27 Sep 2021 19:47:08 +0200 [thread overview]
Message-ID: <8735ppgbc3.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2109271736400.3687803@digraph.polyomino.org.uk> (Joseph Myers's message of "Mon, 27 Sep 2021 17:38:12 +0000")
* Joseph Myers:
> On Fri, 24 Sep 2021, Fangrui Song via Libc-alpha wrote:
>
>> This patch implements __libc_get_static_tls_bounds@@GLIBC_PRIVATE which
>> is available in Android bionic since API level 31. This API allows the
>> sanitizer code to be more robust. _dl_get_tls_static_info@@GLIBC_PRIVATE
>> can probably be removed when Clang/GCC sanitizers drop reliance on it.
>> I am unclear whether the version should be GLIBC_2.*.
>
> Any interface intended to be used outside of code distributed with glibc
> should use a symbol version GLIBC_2.* not GLIBC_PRIVATE.
This interface will not be supportable indefinitely, though. It's still
extremely tied to glibc implementation details. So making it a public
symbol doesn't seem the right choice at this point.
Thanks,
Florian
prev parent reply other threads:[~2021-09-27 17:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-25 0:42 Fangrui Song
2021-09-27 13:02 ` Florian Weimer
2021-09-27 17:59 ` Fangrui Song
2021-10-06 20:23 ` Fangrui Song
2021-10-15 0:13 ` Fangrui Song
2021-10-19 19:37 ` Fāng-ruì Sòng
2021-10-28 5:16 ` Fāng-ruì Sòng
2021-11-29 19:30 ` Florian Weimer
2021-12-21 2:55 ` Fāng-ruì Sòng
2021-12-21 6:08 ` Florian Weimer
2021-09-27 17:38 ` Joseph Myers
2021-09-27 17:47 ` 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=8735ppgbc3.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--cc=adhemerval.zanella@linaro.org \
--cc=joseph@codesourcery.com \
--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).