From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: ppc64 ABI
Date: Sun, 19 Apr 2015 11:13:11 -0400 [thread overview]
Message-ID: <20150419151311.GP6817@brightrain.aerifal.cx> (raw)
In-Reply-To: <CAK4o1Ww92T1=enK10YUwVSXsctXHhJa5gX0J7WC8M_SSssDvwg@mail.gmail.com>
On Sun, Apr 19, 2015 at 03:40:20PM +0100, Justin Cormack wrote:
> On 19 April 2015 at 14:54, Szabolcs Nagy <nsz@port70.net> wrote:
> > * Justin Cormack <justin@specialbusservice.com> [2015-04-19 12:44:15 +0100]:
> >> I am looking at doing a ppc64 port, and after some discussion on irc
> >> last night wondering which ABI to port to.
> >>
> >> ppc64 has two ABIs:
> >> v1: as documented here
> >> v2, usually known as powerpc64le, helpfully. It is not little endian
> > ...
> >>
> >> Both have 16 byte long double oddness.
> >
> > printf/scanf decimal conversion and libm are broken with ibm128
> >
> > if the toolchain could be configured to use ieee128 then that works
> > (i see -mabi=ieeelongdouble compiler option in gcc, it seems 32bit
> > powerpc sysv abi used to require ieee128 long double, but that was
> > not implemented for aix and darwin so i'm not sure who uses it)
> >
> > 64bit long double works too and that's what musl uses on 32bit powerpc
> >
> > (i dont know how much code breaks if we change long double:
> > i think on typical desktop/server it does not matter, but if you
> > want to run some ppc optimized fortran code then it might..)
>
> The Fedora ppc64 gcc accepts -mlong-double-64 it turns out.
OK. For a native toolchain we'd want to be able to make this the
default, but if there's no immediate easier way, it could be put in a
specfile for now.
Rich
next prev parent reply other threads:[~2015-04-19 15:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-19 11:44 Justin Cormack
2015-04-19 13:54 ` Szabolcs Nagy
2015-04-19 14:40 ` Justin Cormack
2015-04-19 15:13 ` Rich Felker [this message]
2015-04-19 15:12 ` Rich Felker
2015-04-19 17:01 ` Justin Cormack
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=20150419151311.GP6817@brightrain.aerifal.cx \
--to=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).