[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Mon, 4 Apr 2022 13:56:36 -0700
From: Max Filippov <jcmvbkbc@...il.com>
To: Arnd Bergmann <arnd@...db.de>
Cc: Christoph Hellwig <hch@...radead.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Yoshinori Sato <ysato@...rs.sourceforge.jp>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
linux-arch <linux-arch@...r.kernel.org>,
"moderated list:H8/300 ARCHITECTURE"
<uclinux-h8-devel@...ts.sourceforge.jp>,
"open list:TENSILICA XTENSA PORT (xtensa)"
<linux-xtensa@...ux-xtensa.org>,
Linux-sh list <linux-sh@...r.kernel.org>,
linux-m68k <linux-m68k@...ts.linux-m68k.org>,
Greg Ungerer <gerg@...ux-m68k.org>,
Damien Le Moal <damien.lemoal@....com>,
linux-riscv <linux-riscv@...ts.infradead.org>
Subject: Re: [RFC PULL] remove arch/h8300
On Mon, Apr 4, 2022 at 12:44 PM Arnd Bergmann <arnd@...db.de> wrote:
> Let me know if I need to enable additional options to get a compiler
> that works for all xtensa targets. Usually the --enable-targets=all
> is meant to be sufficient.
This is not possible with the current design of the xtensa toolchain port.
There's an effort to make switching between the core configurations easy
(without the whole toolchain rebuild:
https://github.com/jcmvbkbc/xtensa-dynconfig
https://github.com/jcmvbkbc/gcc-xtensa/tree/xtensa-dynconfig
https://github.com/jcmvbkbc/binutils-gdb-xtensa/tree/xtensa-plugin-env ),
but it still involves building plugins for the parts of the toolchain
for each new xtensa core.
--
Thanks.
-- Max
Powered by blists - more mailing lists