[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230519-starlit-grip-ed152fb318cf@wendy>
Date: Fri, 19 May 2023 12:22:18 +0100
From: Conor Dooley <conor.dooley@...rochip.com>
To: Alexandre Ghiti <alex@...ti.fr>
CC: Randy Dunlap <rdunlap@...radead.org>,
Stephen Rothwell <sfr@...b.auug.org.au>,
Linux Next Mailing List <linux-next@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Paul Walmsley <paul.walmsley@...ive.com>,
Palmer Dabbelt <palmer@...belt.com>,
Albert Ou <aou@...s.berkeley.edu>,
linux-riscv <linux-riscv@...ts.infradead.org>,
Conor Dooley <conor@...nel.org>
Subject: Re: linux-next: Tree for May 15 (several RV64 build errors)
On Fri, May 19, 2023 at 12:42:55PM +0200, Alexandre Ghiti wrote:
> > > /opt/crosstool/gcc-12.2.0-nolibc/riscv64-linux/bin/riscv64-linux-ld:
> > > section .data LMA [000000000041a000,00000000075bffd7] overlaps
> > > section .text LMA [00000000000f09d4,00000000033562ab]
> > > /opt/crosstool/gcc-12.2.0-nolibc/riscv64-linux/bin/riscv64-linux-ld:
> > > section .init.pi.text LMA [00000000033562ac,0000000003359137]
> > > overlaps section .data LMA [000000000041a000,00000000075bffd7]
> >
> >
> > I'll check this one too which seems to be related to kernel/pi
> > introduction.
>
>
> Thanks to Bjorn: this is caused by XIP_KERNEL, which is known to have
> limited size, hence the overlap, so no fix for this one. Is there a way to
> exclude this config from randconfig?
What exactly is the problem? That the randconfig is too big for the max
XIP kernel size?
We already disable half the world for XIP, is turning off the pi stuff
an option? It's already turned off for 32-bit, right?
Download attachment "signature.asc" of type "application/pgp-signature" (229 bytes)
Powered by blists - more mailing lists