From: Arnd Bergmann <arnd@arndb.de>
To: Max Filippov <jcmvbkbc@gmail.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
Christoph Hellwig <hch@infradead.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Yoshinori Sato <ysato@users.sourceforge.jp>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-arch <linux-arch@vger.kernel.org>,
"moderated list:H8/300 ARCHITECTURE"
<uclinux-h8-devel@lists.sourceforge.jp>,
"open list:TENSILICA XTENSA PORT (xtensa)"
<linux-xtensa@linux-xtensa.org>,
Linux-sh list <linux-sh@vger.kernel.org>,
linux-m68k <linux-m68k@lists.linux-m68k.org>,
Greg Ungerer <gerg@linux-m68k.org>,
Damien Le Moal <damien.lemoal@wdc.com>,
linux-riscv <linux-riscv@lists.infradead.org>
Subject: Re: [RFC PULL] remove arch/h8300
Date: Mon, 4 Apr 2022 21:35:47 +0200 [thread overview]
Message-ID: <CAK8P3a3iFb+ZacZ40d8PC_xcJpLVFXT0Qc-oYEZNkFqXdsfNZw@mail.gmail.com> (raw)
In-Reply-To: <CAMo8BfLT8vMw3aGQPs1+9ry7W63SQphmDc4Tt4A3JvADHJhxiQ@mail.gmail.com>
On Mon, Apr 4, 2022 at 9:14 PM Max Filippov <jcmvbkbc@gmail.com> wrote:
> On Mon, Apr 4, 2022 at 12:01 PM Arnd Bergmann <arnd@arndb.de> wrote:
> > On Mon, Apr 4, 2022 at 7:57 PM Max Filippov <jcmvbkbc@gmail.com> wrote:
> > > Please let me know if you observe any specific build/runtime issues.
> > xtensa-linux-gcc-11.1.0 -DKCONFIG_SEED=
> ...
> > /git/arm-soc/arch/xtensa/kernel/head.S: Assembler messages:
> > /git/arm-soc/arch/xtensa/kernel/head.S:87: Error: invalid register
> > 'atomctl' for 'wsr' instruction
>
> Sure, one cannot use an arbitrary xtensa compiler for the kernel
> build, the compiler configuration must match the core variant selected
> in the linux configuration. Specifically, for the nommu_kc705_defconfig
> the following compiler can be used:
>
> https://github.com/foss-xtensa/toolchain/releases/download/2020.07/x86_64-2020.07-xtensa-de212-elf.tar.gz
>
> If you build the toolchain yourself using crosstool-ng or buildroot they
> accept the 'configuration overlay' parameter that does the compiler
> customization.
>
> Perhaps the documentation for this part is what needs to be improved.
It sounds like a bug in the kernel Makefile. On all other architectures,
you can generally just pick any (recent) compiler and build any kernel,
as the compiler arguments set the exact target machine type based
on the kernel config. You can't normally rely on the compiler defaults
for kernel builds.
Arnd
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd@arndb.de>
To: Max Filippov <jcmvbkbc@gmail.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
Christoph Hellwig <hch@infradead.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Yoshinori Sato <ysato@users.sourceforge.jp>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-arch <linux-arch@vger.kernel.org>,
"moderated list:H8/300 ARCHITECTURE"
<uclinux-h8-devel@lists.sourceforge.jp>,
"open list:TENSILICA XTENSA PORT (xtensa)"
<linux-xtensa@linux-xtensa.org>,
Linux-sh list <linux-sh@vger.kernel.org>,
linux-m68k <linux-m68k@lists.linux-m68k.org>,
Greg Ungerer <gerg@linux-m68k.org>,
Damien Le Moal <damien.lemoal@wdc.com>,
linux-riscv <linux-riscv@lists.infradead.org>
Subject: Re: [RFC PULL] remove arch/h8300
Date: Mon, 4 Apr 2022 21:35:47 +0200 [thread overview]
Message-ID: <CAK8P3a3iFb+ZacZ40d8PC_xcJpLVFXT0Qc-oYEZNkFqXdsfNZw@mail.gmail.com> (raw)
In-Reply-To: <CAMo8BfLT8vMw3aGQPs1+9ry7W63SQphmDc4Tt4A3JvADHJhxiQ@mail.gmail.com>
On Mon, Apr 4, 2022 at 9:14 PM Max Filippov <jcmvbkbc@gmail.com> wrote:
> On Mon, Apr 4, 2022 at 12:01 PM Arnd Bergmann <arnd@arndb.de> wrote:
> > On Mon, Apr 4, 2022 at 7:57 PM Max Filippov <jcmvbkbc@gmail.com> wrote:
> > > Please let me know if you observe any specific build/runtime issues.
> > xtensa-linux-gcc-11.1.0 -DKCONFIG_SEED=
> ...
> > /git/arm-soc/arch/xtensa/kernel/head.S: Assembler messages:
> > /git/arm-soc/arch/xtensa/kernel/head.S:87: Error: invalid register
> > 'atomctl' for 'wsr' instruction
>
> Sure, one cannot use an arbitrary xtensa compiler for the kernel
> build, the compiler configuration must match the core variant selected
> in the linux configuration. Specifically, for the nommu_kc705_defconfig
> the following compiler can be used:
>
> https://github.com/foss-xtensa/toolchain/releases/download/2020.07/x86_64-2020.07-xtensa-de212-elf.tar.gz
>
> If you build the toolchain yourself using crosstool-ng or buildroot they
> accept the 'configuration overlay' parameter that does the compiler
> customization.
>
> Perhaps the documentation for this part is what needs to be improved.
It sounds like a bug in the kernel Makefile. On all other architectures,
you can generally just pick any (recent) compiler and build any kernel,
as the compiler arguments set the exact target machine type based
on the kernel config. You can't normally rely on the compiler defaults
for kernel builds.
Arnd
next prev parent reply other threads:[~2022-04-04 19:36 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-08 6:52 [RFC PULL] remove arch/h8300 Christoph Hellwig
2022-03-08 8:19 ` Arnd Bergmann
2022-04-03 12:43 ` Christoph Hellwig
2022-04-04 13:07 ` Arnd Bergmann
2022-04-04 13:07 ` Arnd Bergmann
2022-04-04 13:09 ` John Paul Adrian Glaubitz
2022-04-04 13:09 ` John Paul Adrian Glaubitz
2022-04-04 13:22 ` Geert Uytterhoeven
2022-04-04 13:22 ` Geert Uytterhoeven
2022-04-04 23:34 ` Damien Le Moal
2022-04-04 23:34 ` Damien Le Moal
2022-04-06 21:25 ` Rob Landley
2022-04-06 21:25 ` Rob Landley
2022-04-07 7:17 ` Arnd Bergmann
2022-04-07 7:17 ` Arnd Bergmann
2022-04-07 7:47 ` John Paul Adrian Glaubitz
2022-04-07 7:47 ` John Paul Adrian Glaubitz
2022-04-07 7:52 ` Christoph Hellwig
2022-04-07 7:52 ` Christoph Hellwig
2022-04-07 8:34 ` Finn Thain
2022-04-07 8:34 ` Finn Thain
2022-04-04 13:41 ` Greg Ungerer
2022-04-04 13:41 ` Greg Ungerer
2022-04-05 3:23 ` Daniel Palmer
2022-04-05 3:23 ` Daniel Palmer
2022-04-05 13:07 ` Greg Ungerer
2022-04-05 13:07 ` Greg Ungerer
2022-04-09 0:24 ` Rob Landley
2022-04-09 0:24 ` Rob Landley
2022-04-09 1:59 ` Finn Thain
2022-04-09 1:59 ` Finn Thain
2022-04-09 4:18 ` Greg Ungerer
2022-04-09 4:18 ` Greg Ungerer
2022-04-10 7:26 ` Rob Landley
2022-04-10 7:26 ` Rob Landley
2022-04-10 8:08 ` Rob Landley
2022-04-10 8:08 ` Rob Landley
2022-04-14 0:49 ` Greg Ungerer
2022-04-14 0:49 ` Greg Ungerer
2022-04-09 3:37 ` Daniel Palmer
2022-04-09 3:37 ` Daniel Palmer
2022-04-10 7:13 ` Rob Landley
2022-04-10 7:13 ` Rob Landley
2022-04-09 4:14 ` Greg Ungerer
2022-04-09 4:14 ` Greg Ungerer
2022-04-04 17:57 ` Max Filippov
2022-04-04 17:57 ` Max Filippov
2022-04-04 19:01 ` Arnd Bergmann
2022-04-04 19:01 ` Arnd Bergmann
2022-04-04 19:14 ` Max Filippov
2022-04-04 19:14 ` Max Filippov
2022-04-04 19:35 ` Arnd Bergmann [this message]
2022-04-04 19:35 ` Arnd Bergmann
2022-04-04 19:44 ` Arnd Bergmann
2022-04-04 19:44 ` Arnd Bergmann
2022-04-04 20:56 ` Max Filippov
2022-04-04 20:56 ` Max Filippov
2022-04-04 20:48 ` Max Filippov
2022-04-04 20:48 ` Max Filippov
2022-04-04 23:32 ` Damien Le Moal
2022-04-04 23:32 ` Damien Le Moal
2022-04-05 21:26 ` Guenter Roeck
2022-04-05 21:26 ` Guenter Roeck
2022-04-05 22:01 ` Arnd Bergmann
2022-04-05 22:01 ` Arnd Bergmann
2022-04-06 0:12 ` Guenter Roeck
2022-04-06 0:12 ` Guenter Roeck
2022-05-06 14:07 ` Geert Uytterhoeven
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=CAK8P3a3iFb+ZacZ40d8PC_xcJpLVFXT0Qc-oYEZNkFqXdsfNZw@mail.gmail.com \
--to=arnd@arndb.de \
--cc=damien.lemoal@wdc.com \
--cc=gerg@linux-m68k.org \
--cc=hch@infradead.org \
--cc=jcmvbkbc@gmail.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-sh@vger.kernel.org \
--cc=linux-xtensa@linux-xtensa.org \
--cc=torvalds@linux-foundation.org \
--cc=uclinux-h8-devel@lists.sourceforge.jp \
--cc=ysato@users.sourceforge.jp \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.