From: Joseph Myers <joseph@codesourcery.com>
To: Wilco Dijkstra <Wilco.Dijkstra@arm.com>
Cc: 'GNU C Library' <libc-alpha@sourceware.org>,
"tnggil@protonmail.com" <tnggil@protonmail.com>, nd <nd@arm.com>
Subject: Re: PPC64 libmvec sincos/sincosf ABI
Date: Tue, 06 Aug 2019 20:31:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.21.1908062026460.11466@digraph.polyomino.org.uk> (raw)
In-Reply-To: <VI1PR0801MB2127D8F615416EA63BBEF4E583D50@VI1PR0801MB2127.eurprd08.prod.outlook.com>
On Tue, 6 Aug 2019, Wilco Dijkstra wrote:
> I don't think it is related to the target - the fastest ABI is one that avoids
> unnecessary work. For example scalar sincos is slow due to the inefficient
> ABI which forces the results through memory (fixing that gives a 50% speedup).
At the scalar API level this is an argument for the previously discussed
idea of adding cexpi functions to <complex.h> (as a GNU extension and
potentially something proposed for standardization).
You'd then have the question of what the API and ABI should look like for
declaring to the compiler that cexpi has certain corresponding vector
functions available.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2019-08-06 20:31 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-06 17:42 Wilco Dijkstra
2019-08-06 20:31 ` Joseph Myers [this message]
2019-08-08 15:25 ` Bill Schmidt
2019-08-08 18:48 ` Bill Schmidt
2019-09-20 19:25 ` GT
2019-09-20 20:25 ` Bill Schmidt
2019-09-23 18:02 ` GT
2019-09-24 16:43 ` Bill Schmidt
-- strict thread matches above, loose matches on Subject: below --
2019-08-01 13:01 GT
2019-08-01 17:04 ` Joseph Myers
2019-08-07 21:17 ` Tulio Magno Quites Machado Filho
2019-08-08 13:34 ` Bill Schmidt
2019-08-08 15:48 ` GT
2019-08-08 15:56 ` Florian Weimer
2019-08-08 16:56 ` GT
2019-08-08 16:11 ` Bill Schmidt
2019-08-08 17:42 ` GT
2019-08-08 17:51 ` Bill Schmidt
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.1908062026460.11466@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=Wilco.Dijkstra@arm.com \
--cc=libc-alpha@sourceware.org \
--cc=nd@arm.com \
--cc=tnggil@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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).