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>,
"tnggil@protonmail.com" <tnggil@protonmail.com>
Subject: Re: [RFC PATCH v1 1/1] PPC64: Implement POWER Architecture Vector Function ABI.
Date: Thu, 20 Aug 2020 16:19:36 +0000 [thread overview]
Message-ID: <R83P300jxESQwnfp1LHbnL7fk0ZULCN53JrLyAM10vZL2_GwQ0q5HjnoywEH2vr4KlQwzpD5PJCTKVVcJc0WSYH1opIbaoyu5tL9FrPRtnM=@protonmail.com> (raw)
In-Reply-To: <20200818213207.GN28786@gate.crashing.org>
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Tuesday, August 18, 2020 5:32 PM, Segher Boessenkool <segher@kernel.crashing.org> wrote:
> On Tue, Aug 18, 2020 at 07:14:19PM +0000, GT wrote:
>
> > > 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.
>
> Great! Please repost with what I already pointed out fixed, that
> explanation added, and working links to the documentation?
>
Are you ok with the titles of the patch and this document?
https://sourceware.org/glibc/wiki/HomePage?action=AttachFile&do=view&target=powerarchvectfuncabi.html
Bert.
next prev parent reply other threads:[~2020-08-20 16:19 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 [this message]
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='R83P300jxESQwnfp1LHbnL7fk0ZULCN53JrLyAM10vZL2_GwQ0q5HjnoywEH2vr4KlQwzpD5PJCTKVVcJc0WSYH1opIbaoyu5tL9FrPRtnM=@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).