From: "Pali Rohár" <pali@kernel.org>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: Paul Mackerras <paulus@samba.org>,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] powerpc: e500: Fix compilation with gcc e500 compiler
Date: Sat, 2 Jul 2022 11:39:52 +0200 [thread overview]
Message-ID: <20220702093952.ir7ctqsianztocik@pali> (raw)
In-Reply-To: <20220524195216.GL25951@gate.crashing.org>
On Tuesday 24 May 2022 14:52:16 Segher Boessenkool wrote:
> On Tue, May 24, 2022 at 09:16:10PM +0200, Pali Rohár wrote:
> > On Tuesday 24 May 2022 13:52:47 Segher Boessenkool wrote:
> > > Aha. Right, because this config forces -mspe it requires one of these
> > > CPUs.
> > >
> > > You can use a powerpc-linux compiler instead, and everything will just
> > > work. These CPUs are still supported, in all of GCC 9 .. GCC 12 :-)
> >
> > Ok. I can use different "generic" powerpc compiler (It should work fine
> > as you said, as it has also -mcpu=8540 option). But I think that
> > compilation of kernel should be supported also by that gcc 8.5.0 e500
> > compiler.
>
> That linuxspe compiler you mean. Sure, why not, the more the merrier,
> as long as it doesn't get in the way of other stuff, I won't protest.
>
> But please don't confuse people: you are talking about a
> powerpc-linuxspe compiler, not e500, which is supported just fine by
> current GCC trunk still, and does not have such limitations :-)
>
>
> Segher
I think the confusion is the calling "generic" or "stripped" compiler
without SPE support as e500 compiler.
The "true" e500 compiler has support for both both integer and floating
point ISA and not just subset or just one type.
next prev parent reply other threads:[~2022-07-02 9:40 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-24 9:39 [PATCH] powerpc: e500: Fix compilation with gcc e500 compiler 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 [this message]
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
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=20220702093952.ir7ctqsianztocik@pali \
--to=pali@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=paulus@samba.org \
--cc=segher@kernel.crashing.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;
as well as URLs for NNTP newsgroup(s).