public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: "H.J. Lu" <hjl.tools@gmail.com>
To: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Cc: GNU C Library <libc-alpha@sourceware.org>,
	Fangrui Song <maskray@google.com>,
	"Carlos O'Donell" <carlos@redhat.com>
Subject: Re: [PATCH v11 0/7] Support DT_RELR relative relocation format
Date: Tue, 26 Apr 2022 08:39:53 -0700	[thread overview]
Message-ID: <CAMe9rOojQPHavZ8T3sYa+vU=jz=B_30eiYyYrJfUQkbhYyguVQ@mail.gmail.com> (raw)
In-Reply-To: <24b4ea75-f160-12d8-26e7-6a7069f77665@linaro.org>

On Mon, Apr 25, 2022 at 10:23 AM Adhemerval Zanella
<adhemerval.zanella@linaro.org> wrote:
>
>
>
> On 22/04/2022 16:01, H.J. Lu wrote:
> > Changes in v11:
> >
> > 1. Replace
> >
> > if (!(map)->l_info[DT_RELR])
> >
> > with
> >
> > if ((map)->l_info[DT_RELR] == NULL)
> >
> > 2. Add a space to --disable-default-dt-relr option.
> > 3. Compile extra DT_RELR tests with $(no-stack-protector).
> > 4. Add DT_RELR related macros to scripts/glibcelf.py.
> >
> > Changes in v10:
> >
> > 1. Don't check GLIBC_PRIVATE definition for DT_RELR in ld.so since ld.so
> > has no DT_NEEDED entry.
> >
> > Changes in v9:
> >
> > 1. A DT_RELR shared library without DT_NEEDED works.
> > 2. A DT_RELR shared library without DT_VERNEED works.
> > 3. A DT_RELR shared library without libc.so on DT_NEEDED works.
> >
> > Changes in v8:
> >
> > 1. Remove the out-of-date comments in _dl_check_map_versions.
> > 2. Change "long" to "long int".
> > 3. Update the DT_RELR NEWS entry.
> >
> > Changes in v7:
> >
> > 1. Add GLIBC_ABI_DT_RELR support before adding DT_RELR support.
> > 2. Update the DT_RELR NEWS entry.
> > 3. Misc fixes.
> >
> > Changes in v6:
> >
> > 1. Move ELF_DYNAMIC_DO_RELR before ELF_DYNAMIC_DO_REL.
> >
> > Changes in v5:
> >
> > 1. Update NEWS entry with the linker option, -z pack-relative-relocs.
> > 2. Remove elf/libc-abi-version.exp and use $(READELF) to check
> > GLIBC_ABI_DT_RELR.
> >
> > Changes in v4:
> >
> > 1. Always enable GLIBC_ABI_DT_RELR check.
> > 2. Use $(OBJDUMP) instead of $(NM) for GLIBC_ABI_DT_RELR check.
> >
> > Changes in v3:
> >
> > 1. Don't define SUPPORT_DT_RELR.
> > 2. Enable DT_RELR in glibc shared libraries and position independent
> > executables (PIE) automatically if linker supports -z pack-relative-relocs.
> >
> > Changes in v2:
> >
> > 1. Enable DT_RELR for all targets.
> > 2. Issue an error if there is a DT_RELR entry without GLIBC_ABI_DT_RELR
> > dependency nor GLIBC_PRIVATE definition.
> >
> > Fangrui Song (1):
> >   elf: Support DT_RELR relative relocation format [BZ #27924]
>
> The patchset looks ok, the only piece that I think it does not add much and
> it would be better to be dropped is the '--disable-default-dt-relr' support.
>
> As we discussed in the weekly patchset call, having less configure switches
> is desirable and this specific option will most likely not be used.

I will drop the -disable-default-dt-relr patch, rebase and check them in.

Thanks.

-- 
H.J.

      reply	other threads:[~2022-04-26 15:40 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-22 19:01 H.J. Lu
2022-04-22 19:01 ` [PATCH v11 1/7] elf: Define DT_RELR related macros and types H.J. Lu
2022-04-22 22:36   ` Fangrui Song
2022-04-22 19:01 ` [PATCH v11 2/7] Add GLIBC_ABI_DT_RELR for DT_RELR support H.J. Lu
2022-04-22 22:37   ` Fangrui Song
2022-04-22 19:01 ` [PATCH v11 3/7] elf: Support DT_RELR relative relocation format [BZ #27924] H.J. Lu
2022-04-22 19:01 ` [PATCH v11 4/7] elf: Properly handle zero DT_RELA/DT_REL values H.J. Lu
2022-04-22 22:39   ` Fangrui Song
2022-04-22 19:01 ` [PATCH v11 5/7] elf: Add more DT_RELR tests H.J. Lu
2022-04-22 19:01 ` [PATCH v11 6/7] Add --disable-default-dt-relr H.J. Lu
2022-04-22 22:43   ` Fangrui Song
2022-04-22 19:01 ` [PATCH v11 7/7] NEWS: Mention DT_RELR support H.J. Lu
2022-04-22 22:40   ` Fangrui Song
2022-04-25 17:23 ` [PATCH v11 0/7] Support DT_RELR relative relocation format Adhemerval Zanella
2022-04-26 15:39   ` H.J. Lu [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='CAMe9rOojQPHavZ8T3sYa+vU=jz=B_30eiYyYrJfUQkbhYyguVQ@mail.gmail.com' \
    --to=hjl.tools@gmail.com \
    --cc=adhemerval.zanella@linaro.org \
    --cc=carlos@redhat.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).