From: "H.J. Lu" <hjl.tools@gmail.com>
To: Fangrui Song <maskray@google.com>
Cc: GNU C Library <libc-alpha@sourceware.org>,
Joseph Myers <joseph@codesourcery.com>
Subject: Re: [PATCH v4 5/5] NEWS: Mention DT_RELR support
Date: Tue, 1 Mar 2022 14:37:10 -0800 [thread overview]
Message-ID: <CAMe9rOruRW4J3_TFy6DCetGsm-Bub6pABtnP+Jn6F_pv5nj+2w@mail.gmail.com> (raw)
In-Reply-To: <20220301192127.4dsqp2veoac33itc@google.com>
On Tue, Mar 1, 2022 at 11:21 AM Fangrui Song <maskray@google.com> wrote:
>
>
> On 2022-03-01, H.J. Lu wrote:
> >---
> > NEWS | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> >diff --git a/NEWS b/NEWS
> >index 626eeabf5d..2122c1e23e 100644
> >--- a/NEWS
> >+++ b/NEWS
> >@@ -9,7 +9,7 @@ Version 2.36
> >
> > Major new features:
> >
> >- [Add new features here]
> >+* Support DT_RELR relative relocation format.
> >
> > Deprecated and removed features, and other changes affecting compatibility:
> >
> >--
> >2.35.1
>
> Perhaps worth a bit more information like:
>
> The position-indepdent executable/shared object using DT_RELR needs to be linked with -z pack-relative-relocs.
How about
* Support DT_RELR relative relocation format generated with the linker
option, -z pack-relative-relocs.
> --pack-dyn-relocs=relr is pretty common but doesn't work. So worth
> calling out the supported linker option.
>
> Reviewed-by: Fangrui Song <maskray@google.com>
--
H.J.
next prev parent reply other threads:[~2022-03-01 22:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-01 16:17 [PATCH v4 0/5] Support DT_RELR relative relocation format H.J. Lu
2022-03-01 16:17 ` [PATCH v4 1/5] elf: Support DT_RELR relative relocation format [BZ #27924] H.J. Lu
2022-03-01 16:17 ` [PATCH v4 2/5] elf: Properly handle zero DT_RELA/DT_REL values H.J. Lu
2022-03-01 19:15 ` Fangrui Song
2022-03-01 16:17 ` [PATCH v4 3/5] Add GLIBC_ABI_DT_RELR for DT_RELR support H.J. Lu
2022-03-01 19:31 ` Fangrui Song
2022-03-01 22:33 ` H.J. Lu
2022-03-01 22:46 ` Fangrui Song
2022-03-01 22:56 ` H.J. Lu
2022-03-01 23:42 ` Peter O'Connor
2022-03-01 16:17 ` [PATCH v4 4/5] Add --disable-default-dt-relr H.J. Lu
2022-03-01 16:17 ` [PATCH v4 5/5] NEWS: Mention DT_RELR support H.J. Lu
2022-03-01 19:21 ` Fangrui Song
2022-03-01 22:37 ` H.J. Lu [this message]
2022-03-01 22:38 ` Fāng-ruì Sòng
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=CAMe9rOruRW4J3_TFy6DCetGsm-Bub6pABtnP+Jn6F_pv5nj+2w@mail.gmail.com \
--to=hjl.tools@gmail.com \
--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).