From: David Edelsohn <dje.gcc@gmail.com>
To: GT <tnggil@protonmail.com>
Cc: Segher Boessenkool <segher@kernel.crashing.org>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
"jakub@redhat.com" <jakub@redhat.com>,
"wschmidt@linux.ibm.com" <wschmidt@linux.ibm.com>,
"tuliom@linux.ibm.com" <tuliom@linux.ibm.com>
Subject: Re: [RFC PATCH v1 1/1] PPC64: Implement POWER Architecture Vector Function ABI.
Date: Mon, 17 Aug 2020 18:05:09 -0400 [thread overview]
Message-ID: <CAGWvnyk4Vnmhx4P4K2Nf3s+ucNgiJBJi9G931EN6pQOnvmcmsA@mail.gmail.com> (raw)
In-Reply-To: <z4hGEdjE-ZqTWgNtKAEIgnkRBKgvHrfman1HljSCRqdJW8mtD8oOv8XaKT0aORoAGFRXTfuKrEuOmGM8pyfrnu1v5KsFNtXB1hKGd3Mvij0=@protonmail.com>
The Power Vector ABI is available at
https://github.com/power8-abi-doc/vector-function-abi
It apparently did not attach correctly to the sourceware wiki or the
filename is different.
Thanks, David
On Mon, Aug 17, 2020 at 1:44 PM GT <tnggil@protonmail.com> wrote:
>
> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> On Thursday, August 13, 2020 6:49 PM, Segher Boessenkool <segher@kernel.crashing.org> wrote:
>
> > Hi!
> >
> > This is about the Power binding to some OpenMP API, right? It has
> > nothing to do with "vector" or "ABI" -- we have vectors already, and
> > we have ABIs already, more than enough of each.
> >
> > It is very very VERY hard to review this without being told the proper
> > setting here.
> >
>
> What this is about:
>
> David Edelsohn wanted to have new library functions, one for each of these 6 single-precision functions:
> sinf, cosf, sincosf, expf, logf, powf; and these 6 double-precision functions:
> sin, cos, sincos, exp, log, and pow.
>
> For the single-precision functions, the corresponding new functions would compute 4 results
> simulatneously. For the double-precision functions, the new ones would compute 2 results
> simultaneously.
>
> x86_64 has already done something very similar so I thought I would adapt as much of their
> documentation and implementation as I could for PPC64.
>
> Let's start with that. Comments so far?
>
> Bert.
next prev parent reply other threads:[~2020-08-17 22:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-07 20:35 Bert Tenjy
2020-08-07 20:59 ` Jakub Jelinek
2020-08-10 17:29 ` GT
2020-08-10 18:07 ` Jakub Jelinek
2020-08-13 20:40 ` GT
2020-08-13 21:00 ` Jakub Jelinek
2020-08-20 19:31 ` GT
2020-08-20 20:04 ` Jakub Jelinek
2020-08-20 20:29 ` Segher Boessenkool
2020-08-13 22:49 ` Segher Boessenkool
2020-08-17 17:44 ` GT
2020-08-17 21:28 ` Segher Boessenkool
2020-08-18 19:14 ` GT
2020-08-18 21:32 ` Segher Boessenkool
2020-08-20 16:19 ` GT
2020-08-20 17:48 ` Segher Boessenkool
2020-12-04 18:28 ` GT
2020-08-17 22:05 ` David Edelsohn [this message]
2020-08-17 23:06 ` Segher Boessenkool
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=CAGWvnyk4Vnmhx4P4K2Nf3s+ucNgiJBJi9G931EN6pQOnvmcmsA@mail.gmail.com \
--to=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=segher@kernel.crashing.org \
--cc=tnggil@protonmail.com \
--cc=tuliom@linux.ibm.com \
--cc=wschmidt@linux.ibm.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).