From: Fangrui Song <maskray@google.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: libc-alpha@sourceware.org,
Adhemerval Zanella <adhemerval.zanella@linaro.org>
Subject: Re: [PATCH v8 6/6] NEWS: Mention DT_RELR support
Date: Wed, 13 Apr 2022 14:43:52 -0700 [thread overview]
Message-ID: <20220413214352.ov6cmuyw7i56cu7r@google.com> (raw)
In-Reply-To: <20220413182507.896862-7-hjl.tools@gmail.com>
On 2022-04-13, H.J. Lu wrote:
>---
> NEWS | 7 ++++++-
> 1 file changed, 6 insertions(+), 1 deletion(-)
>
>diff --git a/NEWS b/NEWS
>index 4b6d9de2b5..ef8ac4acd2 100644
>--- a/NEWS
>+++ b/NEWS
>@@ -9,7 +9,12 @@ Version 2.36
>
> Major new features:
>
>- [Add new features here]
>+* Support for DT_RELR relative relocation format has been added to
>+ glibc. This is a new ELF dynamic tag that improves the size of
>+ relative relocations in shared object files and position independent
>+ executables (PIE). DT_RELR generation requires linker support for
>+ -z pack-relative-relocs option, which is supported for some targets
>+ in recent binutils versions. Lazy binding doesn't apply to DT_RELR.
>
> Deprecated and removed features, and other changes affecting compatibility:
>
>--
>2.35.1
>
(inherited from v4 and v7)
Reviewed-by: Fangrui Song <maskray@google.com>
prev parent reply other threads:[~2022-04-13 21:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-13 18:25 [PATCH v8 0/6] Support DT_RELR relative relocation format H.J. Lu
2022-04-13 18:25 ` [PATCH v8 1/6] elf: Define DT_RELR related macros and types H.J. Lu
2022-04-13 21:43 ` Fangrui Song
2022-04-13 18:25 ` [PATCH v8 2/6] Add GLIBC_ABI_DT_RELR for DT_RELR support H.J. Lu
2022-04-13 22:16 ` Fangrui Song
2022-04-13 18:25 ` [PATCH v8 3/6] elf: Support DT_RELR relative relocation format [BZ #27924] H.J. Lu
2022-04-13 18:25 ` [PATCH v8 4/6] elf: Properly handle zero DT_RELA/DT_REL values H.J. Lu
2022-04-13 18:25 ` [PATCH v8 5/6] Add --disable-default-dt-relr H.J. Lu
2022-04-13 18:25 ` [PATCH v8 6/6] NEWS: Mention DT_RELR support H.J. Lu
2022-04-13 21:43 ` Fangrui Song [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=20220413214352.ov6cmuyw7i56cu7r@google.com \
--to=maskray@google.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).