From: Rich Felker <dalias@libc.org>
To: David Edelsohn <dje.gcc@gmail.com>
Cc: musl@lists.openwall.com
Subject: Re: Re: musl libc for PPC64
Date: Mon, 8 Feb 2016 18:29:45 -0500 [thread overview]
Message-ID: <20160208232945.GE9349@brightrain.aerifal.cx> (raw)
In-Reply-To: <CAGWvny=yDtcXo9+9s535rEFqvn3=W+L7b0WsWrM5TVHi+2pA2Q@mail.gmail.com>
On Mon, Feb 08, 2016 at 06:24:27PM -0500, David Edelsohn wrote:
> You *can* use v2 ABI for BE, but there is no software to run. There
> is no software or ecosystem or operating system that runs v2 ABI BE.
> It's not a hardware limitation, but there is no environment for the
> alternate combination.
Indeed. At this point there's no musl ecosystem for ppc64 at all
though; whatever we add is a fresh start.
> >> IBM has announced that the next generation of the processor will
> >> support native IEEE128 floating point in hardware. There will be
> >> software emulation for the current processors. Support is included in
> >> the forthcoming GCC 6.
> >
> > OK. Does the existing software emulation properly update the hardware
> > floating point status (exception flags) and use the rounding mode?
>
> I'm not sure what you mean. The software emulation assumes the
> hardware support is not present. It doesn't mirror back the state to
> the processor in 64 bit mode. But the emulation is fully IEEE128
> compliant.
if fesetround(FE_DOWNWARD) succeeds but then long double math still
rounds to nearest, that's not IEEE compliant.
The big obstacle to having fenv with softfloat on fully-softfloat
archs is the lack of register state for the rounding mode and
exception flags, so it should be possible to do this right as long as
the cpu has status/mode registers for single/double, which the
soft-quad code can then access/set. If this isn't done right already
we could either try to get it fixed in libgcc or punt and go with
ld64.
Rich
next prev parent reply other threads:[~2016-02-08 23:29 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-08 14:43 David Edelsohn
2016-02-08 16:17 ` Szabolcs Nagy
2016-02-08 16:51 ` Rich Felker
2016-02-08 17:48 ` David Edelsohn
2016-02-08 20:18 ` Rich Felker
2016-02-08 20:30 ` David Edelsohn
2016-02-08 22:59 ` Rich Felker
2016-02-08 23:24 ` David Edelsohn
2016-02-08 23:29 ` Rich Felker [this message]
2016-02-08 23:48 ` Szabolcs Nagy
2016-02-09 1:03 ` Szabolcs Nagy
2016-02-09 1:16 ` David Edelsohn
2016-02-09 1:42 ` Szabolcs Nagy
2016-02-09 1:45 ` Szabolcs Nagy
2016-02-09 1:52 ` Rich Felker
2016-02-09 2:06 ` David Edelsohn
2016-02-10 22:17 ` David Edelsohn
2016-02-08 23:52 ` David Edelsohn
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=20160208232945.GE9349@brightrain.aerifal.cx \
--to=dalias@libc.org \
--cc=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).