Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
Cc: "buildroot@buildroot.org" <buildroot@buildroot.org>,
	ARC Maintainers <arc-buildroot@synopsys.com>,
	Claudiu Zissulescu <Claudiu.Zissulescu@synopsys.com>
Subject: Re: [Buildroot] [arc-buildroot] [PATCH] arch: remove support for BR2_ARC_PAGE_SIZE_4K
Date: Thu, 11 Aug 2022 22:34:40 +0200	[thread overview]
Message-ID: <20220811223440.7f672edd@windsurf> (raw)
In-Reply-To: <20220803192229.0356e729@windsurf>

Hello Alexey,

On Wed, 3 Aug 2022 19:22:29 +0200
Thomas Petazzoni <thomas.petazzoni@bootlin.com> wrote:

> > So, right, suggested change of explicit setup of "common-page-size=max-page-size"
> > is a good fix as it is compatible with older Binutils (before the change
> > referred above, i.e. before 2.38).  
> 
> Could you provide the patch?
> 
> Keep in mind that this block of code:
> 
> # Explicitly set LD's "max-page-size" instead of relying on some defaults
> ifeq ($(BR2_ARC_PAGE_SIZE_4K)$(BR2_ARM64_PAGE_SIZE_4K),y)
> ARCH_TOOLCHAIN_WRAPPER_OPTS += -Wl,-z,max-page-size=4096
> else ifeq ($(BR2_ARC_PAGE_SIZE_8K),y)
> ARCH_TOOLCHAIN_WRAPPER_OPTS += -Wl,-z,max-page-size=8192
> else ifeq ($(BR2_ARC_PAGE_SIZE_16K),y)
> ARCH_TOOLCHAIN_WRAPPER_OPTS += -Wl,-z,max-page-size=16384
> else ifeq ($(BR2_ARM64_PAGE_SIZE_64K),y)
> ARCH_TOOLCHAIN_WRAPPER_OPTS += -Wl,-z,max-page-size=65536
> endif
> 
> in arch/arch.mk, has been recently modified to be used for configurable
> page sizes on ARM64. So, if we decide to add
> -Wl,-z,common-page-size=XYZ, it also needs to work for ARM64 (I think
> it should, but I just want to warn that this code is no longer
> ARC-specific).

Do you think you will be able to provide a patch to fix support for 4K
page size support on ARC in Buildroot?

It is not really a major feature of Buildroot, and it's causing some
build failures in our autobuilders, so if no fix is provided, we'll
probably end up dropping support, as proposed by my patch posted on
July 17.

Thanks!

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2022-08-11 20:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-17 20:04 [Buildroot] [PATCH] arch: remove support for BR2_ARC_PAGE_SIZE_4K Thomas Petazzoni via buildroot
2022-07-17 21:13 ` [Buildroot] [arc-buildroot] " Alexey Brodkin via buildroot
2022-07-18  7:13   ` Thomas Petazzoni via buildroot
2022-07-19 18:20     ` Alexey Brodkin via buildroot
2022-07-26 13:21       ` Thomas Petazzoni via buildroot
     [not found]         ` <IA1PR12MB6210D4881185B436788BF05EA1969@IA1PR12MB6210.namprd12.prod.outlook.com>
2022-08-03 17:22           ` Thomas Petazzoni via buildroot
2022-08-11 20:34             ` Thomas Petazzoni via buildroot [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=20220811223440.7f672edd@windsurf \
    --to=buildroot@buildroot.org \
    --cc=Alexey.Brodkin@synopsys.com \
    --cc=Claudiu.Zissulescu@synopsys.com \
    --cc=arc-buildroot@synopsys.com \
    --cc=thomas.petazzoni@bootlin.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