Yocto Project Discussions
 help / color / mirror / Atom feed
From: Elinor Montmasson <elinor.montmasson@savoirfairelinux.com>
To: peter marko <Peter.Marko@siemens.com>
Cc: adrian freihofer <adrian.freihofer@siemens.com>,
	 yocto <yocto@lists.yoctoproject.org>
Subject: Re: Issues and questions regarding PowerPC 32-bits e500v2 tuning
Date: Wed, 21 Oct 2026 11:01:36 -0400 (EDT)	[thread overview]
Message-ID: <248975416.905486.1792594896595.JavaMail.zimbra@savoirfairelinux.com> (raw)
In-Reply-To: <AS8PR10MB507312025652BBCA5759F02BFD662@AS8PR10MB5073.EURPRD10.PROD.OUTLOOK.COM>

Hello Peter,

----- Original Message -----
> From: "peter marko" <Peter.Marko@siemens.com>
> To: "Elinor Montmasson" <elinor.montmasson@savoirfairelinux.com>, "adrian freihofer" <adrian.freihofer@siemens.com>
> Cc: "yocto" <yocto@lists.yoctoproject.org>
> Sent: Wednesday, 21 October, 2026 15:50:22
> Subject: RE: Issues and questions regarding PowerPC 32-bits e500v2 tuning

> Hello Elinor,
> 
> I have already checked SPE on e500 before and can confirm that it needs to be
> disabled in favor of soft-fpu with newer GCC versions.
> It of course dramatically decreases performance, but what can we do...
> 
> As usual with Yocto, only the default settings are being tested and untested
> features slowly bit rot by time.
> For now, we don't plan to extend our pipeline to all possible tunes/variations.
> So ideally, you should send patches to fix your tune configuration and spin a
> regular local pipeline with Yocto master to catch if it would break again.
> 
> Best Regards,
>  Peter

Ok, thank you for your answer, at least it confirms my analysis.

Because GCC is not an option for SPE support, I am considering using
the LLVM/Clang toolchain through meta-clang, as it seems to support
PowerPC SPE.
I know that some specific recipes will require building with GCC anyway,
in that case fpu-soft will be enabled, but most of the distribution
could build with clang.

Is it something you have tested?

Best regards,
Elinor Montmasson

  reply	other threads:[~2026-10-21 15:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-21  8:34 Issues and questions regarding PowerPC 32-bits e500v2 tuning Elinor Montmasson
2026-10-21 13:50 ` Marko, Peter
2026-10-21 15:01   ` Elinor Montmasson [this message]
2026-10-22  8:21     ` Marko, Peter
2026-10-22  9:27       ` Freihofer, Adrian
2026-10-22 20:37         ` [yocto] " Khem Raj
2026-10-23  8:27           ` Elinor Montmasson
2026-10-23 14:24             ` Khem Raj

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=248975416.905486.1792594896595.JavaMail.zimbra@savoirfairelinux.com \
    --to=elinor.montmasson@savoirfairelinux.com \
    --cc=Peter.Marko@siemens.com \
    --cc=adrian.freihofer@siemens.com \
    --cc=yocto@lists.yoctoproject.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