From: "H.J. Lu" <hjl.tools@gmail.com>
To: binutils@sourceware.org
Subject: Re: [PATCH] x86-64: Allocate input section memory if needed
Date: Tue, 3 Jan 2023 13:59:44 -0800 [thread overview]
Message-ID: <CAMe9rOpLLXvqZFbAEA5fEVARr4HDv6aW8egqj2+OhbHSas-D5w@mail.gmail.com> (raw)
In-Reply-To: <20221227194756.448332-1-hjl.tools@gmail.com>
On Tue, Dec 27, 2022 at 11:47 AM H.J. Lu <hjl.tools@gmail.com> wrote:
>
> When --no-keep-memory is used, the input section memory may not be cached.
> Allocate input section memory for -z pack-relative-relocs if needed.
>
> bfd/
>
> PR ld/29939
> * elfxx-x86.c (elf_x86_size_or_finish_relative_reloc): Allocate
> input section memory if needed.
>
> ld/
>
> PR ld/29939
> * testsuite/ld-elf/dt-relr-2i.d: New test.
> ---
> bfd/elfxx-x86.c | 25 +++++++++++++++++++++++--
> ld/testsuite/ld-elf/dt-relr-2i.d | 17 +++++++++++++++++
> 2 files changed, 40 insertions(+), 2 deletions(-)
> create mode 100644 ld/testsuite/ld-elf/dt-relr-2i.d
>
> diff --git a/bfd/elfxx-x86.c b/bfd/elfxx-x86.c
> index 2ddca340473..ec86e75eba9 100644
> --- a/bfd/elfxx-x86.c
> +++ b/bfd/elfxx-x86.c
> @@ -1541,12 +1541,33 @@ elf_x86_size_or_finish_relative_reloc
> }
> else
> {
> + bfd_byte *contents;
> +
> if (rel.r_offset >= sec->size)
> abort ();
> +
> + if (elf_section_data (sec)->this_hdr.contents
> + != NULL)
> + contents
> + = elf_section_data (sec)->this_hdr.contents;
> + else
> + {
> + if (!bfd_malloc_and_get_section (sec->owner,
> + sec,
> + &contents))
> + info->callbacks->einfo
> + /* xgettext:c-format */
> + (_("%F%P: %pB: failed to allocate memory for section `%pA'\n"),
> + info->output_bfd, sec);
> +
> + /* Cache the section contents for
> + elf_link_input_bfd. */
> + elf_section_data (sec)->this_hdr.contents
> + = contents;
> + }
> htab->elf_write_addend
> (info->output_bfd, outrel->r_addend,
> - (elf_section_data (sec)->this_hdr.contents
> - + rel.r_offset));
> + contents + rel.r_offset);
> }
> }
> }
> diff --git a/ld/testsuite/ld-elf/dt-relr-2i.d b/ld/testsuite/ld-elf/dt-relr-2i.d
> new file mode 100644
> index 00000000000..ed0ef9ccded
> --- /dev/null
> +++ b/ld/testsuite/ld-elf/dt-relr-2i.d
> @@ -0,0 +1,17 @@
> +#source: dt-relr-2.s
> +#ld: -e _start -pie --no-keep-memory $DT_RELR_LDFLAGS
> +#readelf: -rW -d
> +#target: [supports_dt_relr]
> +
> +#...
> + 0x[0-9a-f]+ \(RELR\) +0x[0-9a-f]+
> + 0x[0-9a-f]+ \(RELRSZ\) +(8|16) \(bytes\)
> + 0x[0-9a-f]+ \(RELRENT\) +(4|8) \(bytes\)
> +#...
> +Relocation section '\.rel(a|)\.dyn' at offset 0x[0-9a-f]+ contains 1 entry:
> +#...
> +[0-9a-f]+ +[0-9a-f]+ +R_.*_(RELATIVE|UADDR.*) .*
> +#...
> +Relocation section '\.relr\.dyn' at offset 0x[0-9a-f]+ contains 2 entries:
> + 4 offsets
> +#pass
> --
> 2.38.1
>
I am backporting it to 2.39 branch.
--
H.J.
prev parent reply other threads:[~2023-01-03 22:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-27 19:47 H.J. Lu
2022-12-28 1:16 ` Alan Modra
2022-12-28 17:23 ` H.J. Lu
2022-12-28 22:06 ` Alan Modra
2022-12-28 23:44 ` H.J. Lu
2022-12-29 0:57 ` Alan Modra
2023-01-03 21:59 ` 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=CAMe9rOpLLXvqZFbAEA5fEVARr4HDv6aW8egqj2+OhbHSas-D5w@mail.gmail.com \
--to=hjl.tools@gmail.com \
--cc=binutils@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).