mailing list of musl libc
 help / color / mirror / code / Atom feed
From: David Edelsohn <dje.gcc@gmail.com>
To: musl@lists.openwall.com
Subject: Re: [musl] PPC64(LE) support in musl requires ALTIVEC
Date: Mon, 3 Feb 2020 11:18:42 -0500	[thread overview]
Message-ID: <CAGWvnym0X9ouVnBG+CfKRfHG2x0LY5LfY3XCFhzmOY4_-PxmyA@mail.gmail.com> (raw)
In-Reply-To: <CAH8yC8nTc+=9Sw13z7K5hcaFd1YrQvkTPpuEBKXmnq=2-JG8WA@mail.gmail.com>

On Mon, Feb 3, 2020 at 11:04 AM Jeffrey Walton <noloader@gmail.com> wrote:
>
> On Mon, Feb 3, 2020 at 10:43 AM Romain Naour <romain.naour@gmail.com> wrote:
> >
> > Le 03/02/2020 à 15:50, Rich Felker a écrit :
> > > On Mon, Feb 03, 2020 at 03:16:17PM +0100, Romain Naour wrote:
> > >> Hi,
> > >>
> > >> We noticed that musl toolchain doesn't work on PPC64 e5500 cpus due to
> > >> Altived instructions in src/setjmp/powerpc64/setjmp.s [1].
> > >>
> > >> A patch has been sent by Vincent Fazio to the Buildroot mailing list to disable
> > >> musl for such cpus [2].
> > >>
> > >> Maybe the supported-platforms list could be updated [3].
> > >>
> > >> [1] https://git.musl-libc.org/cgit/musl/tree/src/setjmp/powerpc64/setjmp.s#n74
> > >> [2] http://patchwork.ozlabs.org/patch/1231986/
> > >> [3] https://wiki.musl-libc.org/supported-platforms.html
> > >
> > > Is this like the 32-bit Freescale things with the weird alternate FPU?
> >
> > Indeed, it seems that the only one ppc64 cpu without Altivec support.
>
> I'm not sure if it matters or how it relates here, but I believe IBM
> compilers (XL C and XL C++) do not allow Altivec until Power5. I think
> the decision was more policies and procedures, though. Power5 was the
> first ABI specification from the OpenPower group.
>
> Other compilers supported Altivec earlier then Power5. For example,
> Apple's GCC supported Altivec at least as early as Power3. And I have
> a PowerMac that is Power4 and Altivec works fine.

The PPC64LE ELFv2 ABI specifies Power8 with VSX as the minimum ISA.
Musl is free to ignore that.

The rest of the discussion above about processor support for Altivec
is wrong, but correcting that is off topic.

Thanks, David

  reply	other threads:[~2020-02-03 16:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-03 14:16 Romain Naour
2020-02-03 14:50 ` Rich Felker
2020-02-03 15:42   ` Romain Naour
2020-02-03 16:02     ` Jeffrey Walton
2020-02-03 16:18       ` David Edelsohn [this message]
2020-02-03 16:51   ` A. Wilcox
2020-02-05  1:32   ` [musl] Considering x86-64 fenv.s to C Damian McGuckin

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=CAGWvnym0X9ouVnBG+CfKRfHG2x0LY5LfY3XCFhzmOY4_-PxmyA@mail.gmail.com \
    --to=dje.gcc@gmail.com \
    --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).