mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Romain Naour <romain.naour@gmail.com>
To: musl@lists.openwall.com, Rich Felker <dalias@libc.org>
Subject: Re: [musl] PPC64(LE) support in musl requires ALTIVEC
Date: Mon, 3 Feb 2020 16:42:52 +0100	[thread overview]
Message-ID: <e5c5f80b-a827-08d7-7ba6-895a11dd6df0@gmail.com> (raw)
In-Reply-To: <20200203145030.GP1663@brightrain.aerifal.cx>

Hi,

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.

> We support those for ppc32 as soft-float (and AIUI the ABI for use
> with the FPU matches soft-float ABI, so in theory it could be
> supported but we were never clear on whether it's IEEE-conforming) but
> I wasn't aware of anything like that for 64-bit so it was never added.
> Assuming it's the same concept, I don't see a reason we couldn't add
> it.

I'm not sure it worth the effort, I don't have a particular interest on this
cpu. I'm fine if this case is not supported.
The issue was discovered by toolchain-builder [1] project (a Buildroot side
project for building cross toolchains) due to issue while testing the system
with Qemu.

If upcoming version of musl support this cpu, we will re-enable musl for it.

[1] https://toolchains.bootlin.com

Best regards,
Romain

> 
> Rich
> 


  reply	other threads:[~2020-02-03 15:43 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 [this message]
2020-02-03 16:02     ` Jeffrey Walton
2020-02-03 16:18       ` David Edelsohn
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=e5c5f80b-a827-08d7-7ba6-895a11dd6df0@gmail.com \
    --to=romain.naour@gmail.com \
    --cc=dalias@libc.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).