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: ARM: Fix ld bloat introduced between binutils-2.38 and 2.39
Date: Tue, 3 Jan 2023 18:42:17 +1030	[thread overview]
Message-ID: <Y7PjYVnEMc3moqeM@squeak.grove.modra.org> (raw)
In-Reply-To: <20230103024119.12F182042C@pchp3.se.axis.com>

On Tue, Jan 03, 2023 at 03:41:19AM +0100, Hans-Peter Nilsson wrote:
> So, let's do like x86-64 in a2267dbfc9e1 "x86-64: Use only
> one default max-page-size" and set ELF_MAXPAGESIZE to 4096.

No objections here, but should be acked by one of the ARM maintainers.
> 
> bfd:
> 	* elf32-arm.c (ELF_COMMONPAGESIZE): Always set to 0x1000.
> ---
>  bfd/elf32-arm.c | 4 ----
>  1 file changed, 4 deletions(-)
> 
> diff --git a/bfd/elf32-arm.c b/bfd/elf32-arm.c
> index 0cd3aec14368..b83c43c741c9 100644
> --- a/bfd/elf32-arm.c
> +++ b/bfd/elf32-arm.c
> @@ -20261,11 +20261,7 @@ elf32_arm_backend_symbol_processing (bfd *abfd, asymbol *sym)
>  #define ELF_ARCH			bfd_arch_arm
>  #define ELF_TARGET_ID			ARM_ELF_DATA
>  #define ELF_MACHINE_CODE		EM_ARM
> -#ifdef __QNXTARGET__
>  #define ELF_MAXPAGESIZE			0x1000
> -#else
> -#define ELF_MAXPAGESIZE			0x10000
> -#endif
>  #define ELF_COMMONPAGESIZE		0x1000
>  
>  #define bfd_elf32_mkobject			elf32_arm_mkobject
> -- 
> 2.30.2
> 

-- 
Alan Modra
Australia Development Lab, IBM

  reply	other threads:[~2023-01-03  8:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-02 16:08 [PATCH] " Hans-Peter Nilsson
2023-01-03  1:35 ` Alan Modra
2023-01-03  2:41   ` ARM: " Hans-Peter Nilsson
2023-01-03  8:12     ` Alan Modra [this message]
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=Y7PjYVnEMc3moqeM@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).