public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Alan Modra <amodra@gmail.com>
To: "Richard Earnshaw (lists)" <Richard.Earnshaw@arm.com>
Cc: Michael Matz <matz@suse.de>, binutils@sourceware.org
Subject: Re: [PATCH] PR30437 aarch64: make RELA relocs idempotent
Date: Thu, 25 May 2023 08:24:14 +0930	[thread overview]
Message-ID: <ZG6Vlt53cFHMk0dB@squeak.grove.modra.org> (raw)
In-Reply-To: <1ba7b2c7-b489-79af-3f2a-56450c86d955@arm.com>

On Wed, May 24, 2023 at 04:26:03PM +0100, Richard Earnshaw (lists) via Binutils wrote:
> > 	* elfnn-aarch64.c (elfNN_aarch64_howto_table): Clear src_mask
> > 	if all relocation descriptors.

> Isn't this what partial_inplace is supposed to describe?

Strictly speaking that flag describes what should be done for ld -r.
It has no effect on final link.  It does also affect what is produced
by gas (which is by far the messiest and most confusing part of libbfd
relocation processing).

>  Since that's
> false, I'd expect any value stored in the section contents to be ignored.

-- 
Alan Modra
Australia Development Lab, IBM

      parent reply	other threads:[~2023-05-24 22:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-10 14:04 Michael Matz
2023-05-17 14:35 ` Nick Clifton
2023-05-24 15:26 ` Richard Earnshaw (lists)
2023-05-24 16:03   ` Michael Matz
2023-05-25  9:35     ` Richard Earnshaw (lists)
2023-05-25 12:29       ` Michael Matz
2023-05-25 13:22         ` Richard Earnshaw (lists)
2023-05-25 14:12           ` Michael Matz
2023-05-25 15:56             ` Richard Earnshaw (lists)
2023-05-25 16:01               ` Michael Matz
2023-05-24 22:54   ` Alan Modra [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=ZG6Vlt53cFHMk0dB@squeak.grove.modra.org \
    --to=amodra@gmail.com \
    --cc=Richard.Earnshaw@arm.com \
    --cc=binutils@sourceware.org \
    --cc=matz@suse.de \
    /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).