From: Christophe Leroy <christophe.leroy@csgroup.eu>
To: "Arnd Bergmann" <arnd@arndb.de>, "Pali Rohár" <pali@kernel.org>
Cc: Michael Ellerman <michael@ellerman.id.au>,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] powerpc: e500: Fix compilation with gcc e500 compiler
Date: Sat, 9 Jul 2022 09:26:11 +0000 [thread overview]
Message-ID: <d9339bb9-2410-bea5-7502-1c7839707f4e@csgroup.eu> (raw)
In-Reply-To: <CAK8P3a3YMqGEjRr+ZD4Enm4pnuNNZOaeXqpY=PDXAP7w3P7y4A@mail.gmail.com>
Le 08/07/2022 à 22:04, Arnd Bergmann a écrit :
> On Fri, Jul 8, 2022 at 7:12 PM Pali Rohár <pali@kernel.org> wrote:
>>
>> On Monday 04 July 2022 14:07:10 Arnd Bergmann wrote:
>>> Another problem I see is that a kernel that is built for both E500 and E500MC
>>> uses -mcpu=e500mc and may not actually work on the older ones either
>>> (even with your patch).
>>
>> Such configuration is not supported, see arch/powerpc/platforms/Kconfig.cputype:
>>
>> config PPC_E500MC
>> bool "e500mc Support"
>> select PPC_FPU
>> select COMMON_CLK
>> depends on E500
>> help
>> This must be enabled for running on e500mc (and derivatives
>> such as e5500/e6500), and must be disabled for running on
>> e500v1 or e500v2.
>>
>> Based on this option you can enable either support for e500v1/e500v2 or
>> for e500mc. But not both.
>
> This looks like a bad decision in Kconfig though, as there is nothing
> enforcing the rule: If you want support for E500MC, you have to select
> PPC_85xx, which implies E500 and allows selecting any combination
> of E500v1, E500v2 and E500MC based machines, but enabling
> any E500MC based one breaks all the others.
>
> If this is a hard dependency, I think it should be enforced by making
> E500MC a separate top-level option in the "Processor Type" choice
> statement. However, if they can actually coexist, the help text and
> the Makefile need to be fixed.
>
While looking at this discussion, I discovered that with GCC 12 from
https://mirrors.edge.kernel.org/pub/tools/crosstool/ I'm unable to build
a corenet64_smp_defconfig:
If I select the GENERIC_CPU or e5500 (with altivec) I get:
CC arch/powerpc/kernel/irq.o
{standard input}: Assembler messages:
{standard input}:3535: Error: unrecognized opcode: `wrteei'
{standard input}:5608: Error: unrecognized opcode: `wrteei'
CC arch/powerpc/kernel/pmc.o
{standard input}: Assembler messages:
{standard input}:42: Error: unrecognized opcode: `mfpmr'
{standard input}:53: Error: unrecognized opcode: `mtpmr'
If I select the e5500 (without altivec) or e6500 I get:
CC arch/powerpc/kernel/io.o
{standard input}: Assembler messages:
{standard input}:381: Error: unrecognized opcode: `eieio'
{standard input}:444: Error: unrecognized opcode: `eieio'
{standard input}:480: Error: unrecognized opcode: `eieio'
{standard input}:506: Error: unrecognized opcode: `eieio'
{standard input}:552: Error: unrecognized opcode: `eieio'
{standard input}:817: Error: unrecognized opcode: `eieio'
{standard input}:839: Error: unrecognized opcode: `eieio'
{standard input}:885: Error: unrecognized opcode: `eieio'
{standard input}:1106: Error: unrecognized opcode: `eieio'
{standard input}:1130: Error: unrecognized opcode: `eieio'
{standard input}:1174: Error: unrecognized opcode: `eieio'
{standard input}:1393: Error: unrecognized opcode: `eieio'
{standard input}:1417: Error: unrecognized opcode: `eieio'
{standard input}:1461: Error: unrecognized opcode: `eieio'
Christophe
next prev parent reply other threads:[~2022-07-09 9:26 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-24 9:39 Pali Rohár
2022-05-24 17:59 ` Segher Boessenkool
2022-05-24 18:12 ` Pali Rohár
2022-05-24 18:52 ` Segher Boessenkool
2022-05-24 19:16 ` Pali Rohár
2022-05-24 19:52 ` Segher Boessenkool
2022-07-02 9:39 ` Pali Rohár
2022-07-02 9:44 ` Pali Rohár
2022-07-04 10:23 ` Michael Ellerman
2022-07-04 10:39 ` Pali Rohár
2022-07-04 12:07 ` Arnd Bergmann
2022-07-04 13:13 ` Pali Rohár
2022-07-04 13:22 ` Arnd Bergmann
2022-07-04 13:29 ` Pali Rohár
2022-07-04 13:43 ` Arnd Bergmann
2022-07-07 9:56 ` Christophe Leroy
2022-07-07 9:59 ` Pali Rohár
2022-07-08 17:14 ` Pali Rohár
2022-07-08 20:06 ` Arnd Bergmann
2022-07-09 9:16 ` Christophe Leroy
2022-07-09 10:23 ` Pali Rohár
2022-07-10 17:38 ` Christophe Leroy
2022-07-10 17:57 ` Pali Rohár
2022-07-11 14:20 ` Christophe Leroy
2022-07-08 17:12 ` Pali Rohár
2022-07-08 20:04 ` Arnd Bergmann
2022-07-09 8:51 ` Christophe Leroy
2022-07-09 9:26 ` Christophe Leroy [this message]
2022-07-11 16:14 ` Segher Boessenkool
2022-07-11 17:32 ` Christophe Leroy
2022-07-11 21:48 ` Segher Boessenkool
2022-07-12 9:22 ` Christophe Leroy
2022-07-12 14:11 ` Segher Boessenkool
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=d9339bb9-2410-bea5-7502-1c7839707f4e@csgroup.eu \
--to=christophe.leroy@csgroup.eu \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=michael@ellerman.id.au \
--cc=pali@kernel.org \
/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
all inboxes | Powered by JetHome®