From: Conor Dooley <conor.dooley@microchip.com>
To: Alexandre Ghiti <alex@ghiti.fr>
Cc: Randy Dunlap <rdunlap@infradead.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
linux-riscv <linux-riscv@lists.infradead.org>,
Conor Dooley <conor@kernel.org>
Subject: Re: linux-next: Tree for May 15 (several RV64 build errors)
Date: Fri, 19 May 2023 12:22:18 +0100 [thread overview]
Message-ID: <20230519-starlit-grip-ed152fb318cf@wendy> (raw)
In-Reply-To: <ee3bc2ce-5ebe-927e-5b6d-0b9490ef3875@ghiti.fr>
[-- Attachment #1: Type: text/plain, Size: 1010 bytes --]
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?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-05-19 11:22 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-15 4:12 linux-next: Tree for May 15 Stephen Rothwell
2023-05-16 2:18 ` linux-next: Tree for May 15 (drivers/dma/ti/k3-udma.c) Randy Dunlap
2023-05-16 17:35 ` Vinod Koul
2023-05-16 2:23 ` linux-next: Tree for May 15 (net/ipv4/ipconfig.c:) Randy Dunlap
2023-05-18 3:57 ` David Ahern
2023-05-16 2:26 ` linux-next: Tree for May 15 (drivers/macintosh/ams/ams-core.c) Randy Dunlap
2023-05-16 2:40 ` linux-next: Tree for May 15 (drivers/tty/serial/8250/8250_omap.c) Randy Dunlap
2023-05-17 5:51 ` Tony Lindgren
2023-05-16 2:45 ` linux-next: Tree for May 15 (several RV64 build errors) Randy Dunlap
2023-05-16 6:18 ` Alexandre Ghiti
2023-05-19 10:42 ` Alexandre Ghiti
2023-05-19 11:22 ` Conor Dooley [this message]
2023-05-19 12:09 ` Alexandre Ghiti
2023-05-23 2:28 ` Randy Dunlap
2023-05-23 13:07 ` Alexandre Ghiti
2023-05-24 0:22 ` Randy Dunlap
2023-05-24 1:29 ` Palmer Dabbelt
2023-05-24 6:23 ` Arnd Bergmann
2023-05-24 22:41 ` Randy Dunlap
2023-05-24 22:49 ` Conor Dooley
2023-05-24 23:11 ` Palmer Dabbelt
2023-05-25 12:50 ` Conor Dooley
2023-05-16 2:51 ` linux-next: Tree for May 15 (config SERIAL_CPM) Randy Dunlap
2023-05-18 5:49 ` Jiri Slaby
2023-05-18 5:50 ` Jiri Slaby
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=20230519-starlit-grip-ed152fb318cf@wendy \
--to=conor.dooley@microchip.com \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=conor@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=rdunlap@infradead.org \
--cc=sfr@canb.auug.org.au \
/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