From: "H.J. Lu" <hjl.tools@gmail.com>
To: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Cc: GNU C Library <libc-alpha@sourceware.org>
Subject: Re: [PATCH v6 5/5] NEWS: Mention DT_RELR support
Date: Tue, 29 Mar 2022 15:22:58 -0700 [thread overview]
Message-ID: <CAMe9rOrOnYWOb0Lzj1MNKnEVYVuRTZt7_Pn1+QS-bFt8kaE_6g@mail.gmail.com> (raw)
In-Reply-To: <9d64ade3-1505-9ada-7155-5b6be861ec09@linaro.org>
On Tue, Mar 29, 2022 at 10:25 AM Adhemerval Zanella via Libc-alpha
<libc-alpha@sourceware.org> wrote:
>
>
>
> On 10/03/2022 17:03, H.J. Lu via Libc-alpha wrote:
> > ---
> > NEWS | 3 ++-
> > 1 file changed, 2 insertions(+), 1 deletion(-)
> >
> > diff --git a/NEWS b/NEWS
> > index 626eeabf5d..5d64b794f1 100644
> > --- a/NEWS
> > +++ b/NEWS
> > @@ -9,7 +9,8 @@ Version 2.36
> >
> > Major new features:
> >
> > - [Add new features here]
> > +* Support DT_RELR relative relocation format generated with the linker
>
> Maybe
>
> * Support for DT_RELR relocation relocation format has been added to
> glibc. This is a new ELF section type that improves the size of relative
> relocations in shared object files and position independent
> executables (PIE). DT_RELR support requires linker support for
> -z pack-relative-relocs option, which is supported for some abi in recent
> binutils versions.
>
>
> > + option, -z pack-relative-relocs.
> >
> > Deprecated and removed features, and other changes affecting compatibility:
> >
How about this?
* 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.
--
H.J.
next prev parent reply other threads:[~2022-03-29 22:23 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
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 [this message]
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=CAMe9rOrOnYWOb0Lzj1MNKnEVYVuRTZt7_Pn1+QS-bFt8kaE_6g@mail.gmail.com \
--to=hjl.tools@gmail.com \
--cc=adhemerval.zanella@linaro.org \
--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).