From: Nick Clifton <nickc@redhat.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: Binutils <binutils@sourceware.org>, Alan Modra <amodra@gmail.com>,
GNU C Library <libc-alpha@sourceware.org>
Subject: Re: [PATCH v2 0/9] ld: Implement DT_RELR for x86
Date: Wed, 12 Jan 2022 12:33:19 +0000 [thread overview]
Message-ID: <0a06168a-6ca4-37c9-3d12-fc1913778b86@redhat.com> (raw)
In-Reply-To: <CAMe9rOrsm2+=PKn7Ujr+drh2UhSUUA8z1bF5kbdG0d=Z8XOGyQ@mail.gmail.com>
Hi H.J.
> Fixed in the v3 patch:
>
> https://sourceware.org/pipermail/binutils/2022-January/119292.html
>
> by
>
> Changes in v3:
>
> 1. Set DT_RELR_LDFLAGS, DT_RELR_CC_LDFLAGS, NO_DT_RELR_LDFLAGS and
> NO_DT_RELR_CC_LDFLAGS to empty for non-Linux/x86 targets.
> 2. Run x86 DT_RELR tests only for Linux/x86 targets.
Patch series approved - please apply.
Cheers
Nick
prev parent reply other threads:[~2022-01-12 12:33 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-08 18:38 H.J. Lu
2022-01-08 18:38 ` [PATCH v2 1/9] elf: Add .relr.dyn to special_sections_r H.J. Lu
2022-01-08 18:38 ` [PATCH v2 2/9] elf: Extract _bfd_elf_process_reverse_copy H.J. Lu
2022-01-08 18:38 ` [PATCH v2 3/9] elf: Pass need_layout to _bfd_elf_map_sections_to_segments H.J. Lu
2022-01-08 18:38 ` [PATCH v2 4/9] ld: Initial DT_RELR support H.J. Lu
2022-01-08 18:38 ` [PATCH v2 5/9] elf: Add size_relative_relocs and finish_relative_relocs H.J. Lu
2022-01-08 18:38 ` [PATCH v2 6/9] elf: Support DT_RELR in linker tests H.J. Lu
2022-01-08 18:38 ` [PATCH v2 7/9] x86: Add DT_RELR support H.J. Lu
2022-01-08 18:38 ` [PATCH v2 8/9] ld: Add simple DT_RELR tests H.J. Lu
2022-01-08 18:38 ` [PATCH v2 9/9] ld: Add glibc dependency for DT_RELR H.J. Lu
2022-01-10 15:31 ` Florian Weimer
2022-01-10 15:40 ` H.J. Lu
2022-01-10 15:42 ` Florian Weimer
2022-01-08 21:53 ` [PATCH v2 0/9] ld: Implement DT_RELR for x86 Fangrui Song
2022-01-09 8:13 ` Alexander Monakov
2022-01-13 2:54 ` Fangrui Song
2022-01-13 3:00 ` H.J. Lu
2022-01-11 10:13 ` Nick Clifton
2022-01-11 14:08 ` H.J. Lu
2022-01-12 12:33 ` Nick Clifton [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=0a06168a-6ca4-37c9-3d12-fc1913778b86@redhat.com \
--to=nickc@redhat.com \
--cc=amodra@gmail.com \
--cc=binutils@sourceware.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).