public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Michael Matz <matz@suse.de>
To: Alan Modra <amodra@gmail.com>
Cc: binutils@sourceware.org
Subject: Re: PR29355, ld segfaults with -r/-q and custom-named section .rela*
Date: Tue, 12 Jul 2022 12:19:58 +0000 (UTC)	[thread overview]
Message-ID: <alpine.LSU.2.20.2207121217200.24606@wotan.suse.de> (raw)
In-Reply-To: <YszdhOgJX8oRGlKz@squeak.grove.modra.org>

Hey,

On Tue, 12 Jul 2022, Alan Modra via Binutils wrote:

> Fix that.  Note that it is arguably wrong for ld to leave the output
> .rel/.rela section type as SHT_REL/SHT_RELA when non-empty non-reloc
> sections are written to it, but I'm not going to change that since it
> might be useful to hand-craft relocs in a data section that is then
> written to a SHT_REL/SHT_RELA output section.

Much to my dismay I remember having seen exactly this in the wild, in 
recent years, but I don't remember the details anymore :-/


Ciao,
Michael.

      reply	other threads:[~2022-07-12 12:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-12  2:33 Alan Modra
2022-07-12 12:19 ` Michael Matz [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=alpine.LSU.2.20.2207121217200.24606@wotan.suse.de \
    --to=matz@suse.de \
    --cc=amodra@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).