From: "H.J. Lu" <hjl.tools@gmail.com>
To: Joseph Myers <joseph@codesourcery.com>
Cc: GNU C Library <libc-alpha@sourceware.org>,
Binutils <binutils@sourceware.org>,
LLVM Dev <llvm-dev@lists.llvm.org>,
GCC Development <gcc@gcc.gnu.org>,
GNU gABI gnu-gabi <gnu-gabi@sourceware.org>
Subject: Re: [PATCH] Add GNU_PROPERTY_1_GLIBC_2_NEEDED
Date: Thu, 28 Oct 2021 12:08:41 -0700 [thread overview]
Message-ID: <CAMe9rOofFfhE27rB9O4kn3e4fBSdBdFr0b6-cTwczWQUtbxD2g@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2110281739530.1736839@digraph.polyomino.org.uk>
On Thu, Oct 28, 2021 at 10:43 AM Joseph Myers <joseph@codesourcery.com> wrote:
>
> On Wed, 27 Oct 2021, H.J. Lu via Libc-alpha wrote:
>
> > Linker adds glibc versions in GNU_PROPERTY_1_GLIBC_2_NEEDED to the
> > .gnu.version_r section and removes GNU_PROPERTY_1_GLIBC_2_NEEDED note
> > when generating shared libraries and executables.
>
> Note that there is no guarantee that a new glibc version actually has any
> symbols in libc at the corresponding symbol version (there are no
> GLIBC_2.20 symbols in any ABI test baseline for any architecture, for
> example). If it happens not to, will the symbol version exist at all to
> satisfy this check?
>
Then we need to add a new glibc version if it happens.
--
H.J.
prev parent reply other threads:[~2021-10-28 19:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-28 0:03 H.J. Lu
2021-10-28 6:52 ` [llvm-dev] " Florian Weimer
2021-10-28 13:39 ` H.J. Lu
2021-10-28 13:43 ` Florian Weimer
2021-10-28 13:46 ` H.J. Lu
2021-10-28 17:43 ` Joseph Myers
2021-10-28 19:08 ` H.J. Lu [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=CAMe9rOofFfhE27rB9O4kn3e4fBSdBdFr0b6-cTwczWQUtbxD2g@mail.gmail.com \
--to=hjl.tools@gmail.com \
--cc=binutils@sourceware.org \
--cc=gcc@gcc.gnu.org \
--cc=gnu-gabi@sourceware.org \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=llvm-dev@lists.llvm.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).