mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Arnd Bergmann <arnd@kernel.org>
To: musl@lists.openwall.com
Subject: Re: [musl] Adding PowerPC SPE support
Date: Sat, 5 Jun 2021 23:15:04 +0200	[thread overview]
Message-ID: <CAK8P3a0YHW+XL7RvgMyy0UrCc=Fgz0x=27gcdDEJbBVO3ATqAg@mail.gmail.com> (raw)
In-Reply-To: <20210605171216.GA7558@brightrain.aerifal.cx>

On Sat, Jun 5, 2021 at 7:12 PM Rich Felker <dalias@libc.org> wrote:
>
> When the soft-float ABI for PowerPC was added in 2016 (commit
> 5a92dd95c77cee81755f1a441ae0b71e3ae2bcdb, mail thread "[PATCH v3] Add
> PowerPC soft-float support") with Freescale cpus having the
> alternative SPE FPU as the main use case, I noted that we could
> probably support hard float on them, but that it would involve
> determining some difficult ABI constraints. I'm now revisiting adding
> this support.

Note that regardless of the technical issues, there is a practical problem
in the long run, since gcc-8.5 was the last release with powerpcspe
support, and at some point in the future everyone will move to gcc-9
or higher.

The last e500/e500v2 based SoCs are now ten years old, and are
listed as available until 2025 but also "not recommended for new
designs". Linux kernel support for these has been marked as
"odd fixes" instead of "maintained" since early 2020, but in practice
this has been the case for much longer.

If I remember correctly, someone mentioned using musl on bare
metal e200 based microcontrollers, which is more interesting
for powerpcspe support than Linux user space, but this requires
additional patches already.

       Arnd

  reply	other threads:[~2021-06-05 21:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-05 17:12 Rich Felker
2021-06-05 21:15 ` Arnd Bergmann [this message]
2021-06-05 22:05   ` Rich Felker
2021-06-07  7:56     ` Arnd Bergmann

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='CAK8P3a0YHW+XL7RvgMyy0UrCc=Fgz0x=27gcdDEJbBVO3ATqAg@mail.gmail.com' \
    --to=arnd@kernel.org \
    --cc=musl@lists.openwall.com \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

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).