From: Joseph Myers <joseph@codesourcery.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: <libc-alpha@sourceware.org>
Subject: Re: [PATCH 3/7] Add GLIBC_ABI_DT_RELR for DT_RELR support
Date: Fri, 4 Feb 2022 19:53:37 +0000 [thread overview]
Message-ID: <alpine.DEB.2.22.394.2202041950570.244210@digraph.polyomino.org.uk> (raw)
In-Reply-To: <20220203180948.2744-4-hjl.tools@gmail.com>
On Thu, 3 Feb 2022, H.J. Lu via Libc-alpha wrote:
> +%if HAVE_DT_RELR
> + GLIBC_ABI_DT_RELR {
> + # This symbol is used only for empty version map and will be removed
> + # by scripts/versions.awk.
> + __placeholder_only_for_empty_version_map;
> + }
My understanding is that HAVE_DT_RELR describes a property of the linker
used to build glibc, not a property of what features glibc itself
supports.
The symbol versions provided by glibc, and whether glibc supports binaries
using RELR relocations, should be independent of whether the linker
version used to build glibc supports such relocations. A given glibc
version should either always support RELR relocations (for a given glibc
ABI) or never support them (for that ABI), independent of linker features,
and likewise the symbol versions provided by glibc should be independent
of linker features.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2022-02-04 19:53 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-03 18:09 [PATCH 0/7] Support DT_RELR relative relocation format H.J. Lu
2022-02-03 18:09 ` [PATCH 1/7] elf: Support DT_RELR relative relocation format [BZ #27924] H.J. Lu
2022-02-03 18:09 ` [PATCH 2/7] elf: Properly handle zero DT_RELA/DT_REL values H.J. Lu
2022-02-03 18:09 ` [PATCH 3/7] Add GLIBC_ABI_DT_RELR for DT_RELR support H.J. Lu
2022-02-04 19:53 ` Joseph Myers [this message]
2022-02-04 20:04 ` H.J. Lu
2022-02-04 20:10 ` Joseph Myers
2022-02-04 20:40 ` H.J. Lu
2022-02-04 21:01 ` Joseph Myers
2022-02-04 21:08 ` H.J. Lu
2022-02-04 23:58 ` Joseph Myers
2022-02-05 17:24 ` H.J. Lu
2022-02-03 18:09 ` [PATCH 4/7] x86/configure.ac: Define PI_STATIC_AND_HIDDEN/SUPPORT_STATIC_PIE H.J. Lu
2022-02-03 18:09 ` [PATCH 5/7] x86: Define SUPPORT_DT_RELR H.J. Lu
2022-02-03 18:09 ` [PATCH 6/7] Add --disable-default-dt-relr H.J. Lu
2022-02-03 18:09 ` [PATCH 7/7] NEWS: Mention DT_RELR support H.J. Lu
2022-02-04 20:00 ` [PATCH 0/7] Support DT_RELR relative relocation format Joseph Myers
2022-02-04 20:08 ` H.J. Lu
2022-02-04 20:12 ` Joseph Myers
2022-02-04 20:32 ` Fangrui Song
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=alpine.DEB.2.22.394.2202041950570.244210@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=hjl.tools@gmail.com \
--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).