public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: GT <tnggil@protonmail.com>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
	"dje.gcc@gmail.com" <dje.gcc@gmail.com>,
	"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: Tue, 18 Aug 2020 19:14:19 +0000	[thread overview]
Message-ID: <6U0hNAH-Hsbyqz3rSo-yD6BiTkmnYDdXXWb8S_6TkfzzkrjaQYP-kj7HZYznnu_JwaR4Kp8FqLSf7PIuOSM9r6LVYJZH-1BlHS9eewBVuwk=@protonmail.com> (raw)
In-Reply-To: <20200817212835.GE28786@gate.crashing.org>


‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Monday, August 17, 2020 5:28 PM, Segher Boessenkool <segher@kernel.crashing.org> wrote:

> On Mon, Aug 17, 2020 at 05:44:46PM +0000, GT wrote:
>
> > > 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?
>
> That sounds like libmvec?
>
> I still don't know what this is.
>

Yes, it is libmvec.

Now look at what GCC does to the code in Examples 1 and 2 at this link:
https://sourceware.org/glibc/wiki/libmvec

x86_64 added functionality to GCC so such code uses the new functions without the user
having to re-write the loops and explicitly call the new functions.

We are aiming to provide that same capability for PPC64 in GCC.

Bert.

  reply	other threads:[~2020-08-18 19:14 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 [this message]
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
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='6U0hNAH-Hsbyqz3rSo-yD6BiTkmnYDdXXWb8S_6TkfzzkrjaQYP-kj7HZYznnu_JwaR4Kp8FqLSf7PIuOSM9r6LVYJZH-1BlHS9eewBVuwk=@protonmail.com' \
    --to=tnggil@protonmail.com \
    --cc=dje.gcc@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jakub@redhat.com \
    --cc=segher@kernel.crashing.org \
    --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).