From: Jeff Law <jeffreyalaw@gmail.com>
To: 钟居哲 <juzhe.zhong@rivai.ai>, gcc-patches <gcc-patches@gcc.gnu.org>
Cc: "kito.cheng" <kito.cheng@gmail.com>,
"kito.cheng" <kito.cheng@sifive.com>,
"rdapp.gcc" <rdapp.gcc@gmail.com>
Subject: Re: [PATCH V7] RISC-V: RISC-V: Support gather_load/scatter RVV auto-vectorization
Date: Thu, 13 Jul 2023 07:58:37 -0600 [thread overview]
Message-ID: <ec105321-63e3-db34-e463-a299361ae590@gmail.com> (raw)
In-Reply-To: <B4059AF6E1067302+2023071307300014851914@rivai.ai>
On 7/12/23 17:30, 钟居哲 wrote:
> I notice vectorizable_call in Loop Vectorizer.
> It's vectorizing CALL function for example like fmax/fmin.
> From my understanding, we dont have RVV instruction for fmax/fmin?
>
> So for now, I don't need to support builtin call function vectorization
> for RVV.
> Am I right?
Yes, you are correct.
>
> I am wondering whether we do have some kind of builtin function call
> vectorization by using RVV instructions.
It can be advantageous, even if the call doesn't collapse down to a
single vector instruction. Consider libmvec which is an API to provide
things like sin, cos, exp, log, etc in vector form.
Once the library routines are written, those can then be exposed to the
compiler in turn allowing vectorization of loops with a subset of calls
such as sin, cos, pow, log, etc.
jeff
next prev parent reply other threads:[~2023-07-13 13:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-12 9:38 juzhe.zhong
[not found] ` <66564378DDCC57ED+202307121748494317959@rivai.ai>
2023-07-12 21:22 ` 回复: " 钟居哲
2023-07-12 21:48 ` Jeff Law
2023-07-12 22:17 ` 钟居哲
2023-07-12 22:25 ` Jeff Law
2023-07-12 23:30 ` 钟居哲
2023-07-13 7:47 ` Richard Biener
2023-07-13 14:01 ` Jeff Law
2023-07-13 14:05 ` Palmer Dabbelt
2023-07-13 14:32 ` Robin Dapp
2023-07-13 14:42 ` 钟居哲
2023-07-13 13:58 ` Jeff Law [this message]
2023-07-13 1:12 ` 回复: " Li, Pan2
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=ec105321-63e3-db34-e463-a299361ae590@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=juzhe.zhong@rivai.ai \
--cc=kito.cheng@gmail.com \
--cc=kito.cheng@sifive.com \
--cc=rdapp.gcc@gmail.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).