From: Joseph Myers <joseph@codesourcery.com>
To: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Cc: "H.J. Lu" <hjl.tools@gmail.com>,
GNU C Library <libc-alpha@sourceware.org>
Subject: Re: [PATCH v6 3/5] Add GLIBC_ABI_DT_RELR for DT_RELR support
Date: Wed, 30 Mar 2022 19:22:38 +0000 [thread overview]
Message-ID: <alpine.DEB.2.22.394.2203301919510.450807@digraph.polyomino.org.uk> (raw)
In-Reply-To: <5f32b52c-508b-dcba-af9b-7ff248cc3c1d@linaro.org>
On Wed, 30 Mar 2022, Adhemerval Zanella via Libc-alpha wrote:
> But it still does not fail when the architecture does not actually implement
> RELR even when static linker does:
The dynamic linker is supposed to support executing binaries using RELR
relocations on all architectures - there's not meant to be anything
architecture-specific about that support. What's architecture-specific is
the static linker support (thus, if missing in the static linker used to
build and test glibc, then (a) the dynamic linker could still run binaries
using RELR if they were built using some other static linker, but (b) none
of the glibc binaries, either installed or test, will contain any RELR
relocations themselves).
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2022-03-30 19:22 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-10 20:03 [PATCH v6 0/5] Support DT_RELR relative relocation format H.J. Lu
2022-03-10 20:03 ` [PATCH v6 1/5] elf: Support DT_RELR relative relocation format [BZ #27924] H.J. Lu
2022-03-29 16:34 ` Adhemerval Zanella
2022-03-29 22:34 ` H.J. Lu
2022-03-10 20:03 ` [PATCH v6 2/5] elf: Properly handle zero DT_RELA/DT_REL values H.J. Lu
2022-03-29 16:38 ` Adhemerval Zanella
2022-03-29 22:30 ` H.J. Lu
2022-03-10 20:03 ` [PATCH v6 3/5] Add GLIBC_ABI_DT_RELR for DT_RELR support H.J. Lu
2022-03-29 16:52 ` Adhemerval Zanella
2022-03-29 22:29 ` H.J. Lu
2022-03-30 14:18 ` Adhemerval Zanella
2022-03-30 14:41 ` H.J. Lu
2022-03-30 17:17 ` Adhemerval Zanella
2022-03-30 17:32 ` H.J. Lu
2022-03-30 17:39 ` Adhemerval Zanella
2022-03-30 19:22 ` Joseph Myers [this message]
2022-03-30 20:38 ` Adhemerval Zanella
2022-03-30 21:32 ` Fangrui Song
2022-03-10 20:03 ` [PATCH v6 4/5] Add --disable-default-dt-relr H.J. Lu
2022-03-29 17:19 ` Adhemerval Zanella
2022-03-29 22:25 ` H.J. Lu
2022-03-10 20:03 ` [PATCH v6 5/5] NEWS: Mention DT_RELR support H.J. Lu
2022-03-29 17:25 ` Adhemerval Zanella
2022-03-29 22:22 ` H.J. Lu
2022-03-29 23:34 ` Fangrui Song
2022-03-30 14:20 ` Adhemerval Zanella
2022-03-10 20:09 ` [PATCH v6 0/5] Support DT_RELR relative relocation format 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.2203301919510.450807@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=adhemerval.zanella@linaro.org \
--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).