From: Joseph Myers <joseph@codesourcery.com>
To: Daniel Kolesa <daniel@octaforge.org>
Cc: "Segher Boessenkool" <segher@kernel.crashing.org>,
musl@lists.openwall.com, "Rich Felker" <dalias@libc.org>,
"Michal Suchánek" <msuchanek@suse.de>,
libc-alpha@sourceware.org, eery@paperfox.es,
"Will Springer" <skirmisher@protonmail.com>,
"Palmer Dabbelt via binutils" <binutils@sourceware.org>,
"via libc-dev" <libc-dev@lists.llvm.org>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [musl] Re: ppc64le and 32-bit LE userland compatibility
Date: Thu, 4 Jun 2020 22:08:02 +0000 [thread overview]
Message-ID: <alpine.DEB.2.21.2006042154060.8237@digraph.polyomino.org.uk> (raw)
In-Reply-To: <60fa8bd7-2439-4403-a0eb-166a2fb49a4b@www.fastmail.com>
On Thu, 4 Jun 2020, Daniel Kolesa wrote:
> The ELFv2 document specifies things like passing of quadruple precision
> floats. Indeed, VSX is needed there, but that's not a concern if you
> *don't* use quadruple precision floats.
My understanding is that the registers used for argument passing are all
ones that exactly correspond to the Vector registers in earlier
instruction set versions. In other words, you could *in principle*
produce an object, or a whole libm shared library, that (a) passes or
receives _Float128 values in registers, (b) does not use any instructions
beyond those available with -mcpu=970, (c) would work as intended whether
executed on a 970 or on POWER8 and (d) when executed on POWER8, would
fully interoperate with objects receiving or passing _Float128 values and
compiled for POWER8 to use VSX instructions for that purpose. GCC may not
support _Float128 for older processors, but that doesn't prevent you from
maintaining patches to add such support. (But if you want to support
those 64-bit processors that don't have Vector registers at all, you
indeed can't use binary128 and interoperate with code using VSX for that
format in POWER8.)
(Cf. how the Arm hard-float ABI variant works even on processors with
single-precision-only VFP, because such processors still have the
double-precision loads and stores although not double-precision
arithmetic. When working on that ABI support in GCC some years ago, I
also made sure that GNU vector types corresponding to NEON vector types
were passed consistently for the hard-float ABI whether or not any vector
instructions were present - thus, avoiding depending on the machine modes
for those vector types because GCC could choose a different machine mode
depending on the instructions available.)
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2020-06-04 22:08 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-29 19:03 [musl] " Will Springer
2020-05-29 19:24 ` Rich Felker
2020-05-30 22:56 ` Will Springer
2020-05-30 15:37 ` [musl] " Christophe Leroy
2020-05-30 22:17 ` Will Springer
2020-06-05 23:54 ` Will Springer
2020-06-12 5:13 ` Christophe Leroy
2020-05-30 19:22 ` Segher Boessenkool
2020-05-31 0:57 ` Will Springer
2020-05-31 20:42 ` Segher Boessenkool
2020-05-31 22:29 ` Daniel Kolesa
2020-06-02 1:36 ` Segher Boessenkool
2020-06-01 21:28 ` Joseph Myers
2020-06-01 21:36 ` Rich Felker
2020-06-01 23:26 ` Daniel Kolesa
2020-06-01 23:45 ` Joseph Myers
2020-06-01 23:55 ` Joseph Myers
2020-06-02 0:13 ` Daniel Kolesa
2020-06-02 0:11 ` Daniel Kolesa
2020-06-02 13:40 ` Joseph Myers
2020-06-02 14:23 ` Michal Suchánek
2020-06-02 15:13 ` Daniel Kolesa
2020-06-02 15:27 ` Michal Suchánek
2020-06-02 15:40 ` Daniel Kolesa
2020-06-02 15:56 ` Michal Suchánek
2020-06-04 17:20 ` Segher Boessenkool
2020-06-04 17:12 ` Segher Boessenkool
2020-06-04 17:18 ` Rich Felker
2020-06-04 17:33 ` Segher Boessenkool
2020-06-04 17:46 ` Rich Felker
2020-06-04 19:00 ` David Edelsohn
2020-06-04 19:37 ` Rich Felker
2020-06-04 20:39 ` Daniel Kolesa
2020-06-04 21:10 ` Segher Boessenkool
2020-06-04 21:43 ` Daniel Kolesa
2020-06-04 22:08 ` Joseph Myers [this message]
2020-06-04 22:26 ` Daniel Kolesa
2020-06-05 0:02 ` Segher Boessenkool
2020-06-04 23:42 ` Segher Boessenkool
2020-06-04 23:35 ` Segher Boessenkool
2020-06-05 2:18 ` Daniel Kolesa
2020-06-05 17:27 ` Segher Boessenkool
2020-06-05 17:50 ` Rich Felker
2020-06-05 23:45 ` Segher Boessenkool
2020-06-05 21:59 ` Daniel Kolesa
2020-06-06 0:12 ` Segher Boessenkool
2020-06-06 2:13 ` Daniel Kolesa
2020-06-02 14:52 ` Daniel Kolesa
2020-06-02 2:12 ` Segher Boessenkool
2020-06-02 2:17 ` Daniel Kolesa
2020-06-02 13:50 ` Joseph Myers
2020-06-02 17:47 ` Segher Boessenkool
2020-06-02 1:58 ` Segher Boessenkool
2020-06-02 2:09 ` Jeffrey Walton
2020-06-02 2:12 ` Daniel Kolesa
2020-06-02 2:36 ` Segher Boessenkool
2020-06-02 2:55 ` Daniel Kolesa
2020-06-02 1:42 ` Segher Boessenkool
2020-06-02 2:03 ` Daniel Kolesa
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=alpine.DEB.2.21.2006042154060.8237@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=binutils@sourceware.org \
--cc=dalias@libc.org \
--cc=daniel@octaforge.org \
--cc=eery@paperfox.es \
--cc=libc-alpha@sourceware.org \
--cc=libc-dev@lists.llvm.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=msuchanek@suse.de \
--cc=musl@lists.openwall.com \
--cc=segher@kernel.crashing.org \
--cc=skirmisher@protonmail.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).