From: Segher Boessenkool <segher@kernel.crashing.org>
To: "Pali Rohár" <pali@kernel.org>
Cc: Christophe Leroy <christophe.leroy@csgroup.eu>,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
Nicholas Piggin <npiggin@gmail.com>
Subject: Re: [PATCH v1] powerpc/64: Set default CPU in Kconfig
Date: Fri, 16 Dec 2022 17:02:03 -0600 [thread overview]
Message-ID: <20221216230203.GK25951@gate.crashing.org> (raw)
In-Reply-To: <20221216222359.74i6otxszwanf76y@pali>
On Fri, Dec 16, 2022 at 11:23:59PM +0100, Pali Rohár wrote:
> > It appears the E500MC64 never made it outside of FSL, so it is best not
> > to use it at all, imo.
>
> Yes, it really makes sense to not use e500mc64 flag. Maybe gcc
> documentation could be updated to mention this fact?
Thanks. I filed <https://gcc.gnu.org/PR108149> so that we don't forget
about this.
Segher
WARNING: multiple messages have this Message-ID (diff)
From: Segher Boessenkool <segher@kernel.crashing.org>
To: "Pali Rohár" <pali@kernel.org>
Cc: linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
Nicholas Piggin <npiggin@gmail.com>
Subject: Re: [PATCH v1] powerpc/64: Set default CPU in Kconfig
Date: Fri, 16 Dec 2022 17:02:03 -0600 [thread overview]
Message-ID: <20221216230203.GK25951@gate.crashing.org> (raw)
In-Reply-To: <20221216222359.74i6otxszwanf76y@pali>
On Fri, Dec 16, 2022 at 11:23:59PM +0100, Pali Rohár wrote:
> > It appears the E500MC64 never made it outside of FSL, so it is best not
> > to use it at all, imo.
>
> Yes, it really makes sense to not use e500mc64 flag. Maybe gcc
> documentation could be updated to mention this fact?
Thanks. I filed <https://gcc.gnu.org/PR108149> so that we don't forget
about this.
Segher
next prev parent reply other threads:[~2022-12-16 23:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-07 13:38 [PATCH v1] powerpc/64: Set default CPU in Kconfig Christophe Leroy
2022-12-07 13:38 ` Christophe Leroy
2022-12-08 19:13 ` Pali Rohár
2022-12-08 19:13 ` Pali Rohár
2022-12-15 20:42 ` Pali Rohár
2022-12-15 20:42 ` Pali Rohár
2022-12-16 19:15 ` Segher Boessenkool
2022-12-16 19:15 ` Segher Boessenkool
2022-12-16 22:23 ` Pali Rohár
2022-12-16 22:23 ` Pali Rohár
2022-12-16 23:02 ` Segher Boessenkool [this message]
2022-12-16 23:02 ` 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=20221216230203.GK25951@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=christophe.leroy@csgroup.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=npiggin@gmail.com \
--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 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.