public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Alan Modra <amodra@gmail.com>
To: Hans-Peter Nilsson <hp@axis.com>
Cc: binutils@sourceware.org
Subject: Re: [PATCH] Fix ld bloat introduced between binutils-2.38 and 2.39
Date: Tue, 3 Jan 2023 12:05:27 +1030	[thread overview]
Message-ID: <Y7OGX08FCfvucZFW@squeak.grove.modra.org> (raw)
In-Reply-To: <20230102160857.ABA7F2042C@pchp3.se.axis.com>

On Mon, Jan 02, 2023 at 05:08:57PM +0100, Hans-Peter Nilsson via Binutils wrote:
> That may sound like an argument for setting the bfd_arch_arm
> ELF_MAXPAGESIZE to 4 KiB, but then the obscure corner-case
> wouldn't be properly handled.

Agreed.  It's what x86 did when facing the same thing.  If anybody
cares about the obscure corner-case you identify then they can just
use -z max-page-size.  Or edit elf32-arm.c.

> Instead, I suggest simply making ELF_MAXPAGESIZE generally
> overridable by means of a --with option at linker
> configuration time.

I dislike configure time options that affect linker behaviour, but I
realise I'm flogging a dead horse since we already have a lot of them.
However, this particular option is worse than most since it affects
all ELF targets.  That can't be correct or useful with
--enable-targets=all.

-- 
Alan Modra
Australia Development Lab, IBM

  reply	other threads:[~2023-01-03  1:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-02 16:08 Hans-Peter Nilsson
2023-01-03  1:35 ` Alan Modra [this message]
2023-01-03  2:41   ` ARM: " Hans-Peter Nilsson
2023-01-03  8:12     ` Alan Modra
2023-01-03 15:16       ` Hans-Peter Nilsson
2023-01-11 16:24         ` Hans-Peter Nilsson
2023-01-12 13:48           ` Nick Clifton
2023-01-11 16:28         ` Hans-Peter Nilsson
2023-01-11 16:39           ` Hans-Peter Nilsson
2023-01-12 13:49           ` Nick Clifton

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=Y7OGX08FCfvucZFW@squeak.grove.modra.org \
    --to=amodra@gmail.com \
    --cc=binutils@sourceware.org \
    --cc=hp@axis.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).