From: "juzhe.zhong@rivai.ai" <juzhe.zhong@rivai.ai>
To: "Robin Dapp" <rdapp.gcc@gmail.com>, rguenther <rguenther@suse.de>
Cc: "Robin Dapp" <rdapp.gcc@gmail.com>,
gcc-patches <gcc-patches@gcc.gnu.org>,
richard.sandiford <richard.sandiford@arm.com>,
krebbel <krebbel@linux.ibm.com>, uweigand <uweigand@de.ibm.com>,
linkw <linkw@linux.ibm.com>
Subject: Re: Re: [PATCH V2] VECT: Support LEN_MASK_ LOAD/STORE to support flow control for length loop control
Date: Thu, 15 Jun 2023 17:01:02 +0800 [thread overview]
Message-ID: <6439A2EB450AD2A3+2023061517010183215980@rivai.ai> (raw)
In-Reply-To: <7e31f226-476a-75d1-6a0f-13fa9134e311@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1626 bytes --]
Ok. I will add BIAS argument too for the convenience of possible s390 needed.
Even though we (RVV) don't really need it.
Thank. Will send a small patch V3 soon.
juzhe.zhong@rivai.ai
From: Robin Dapp
Date: 2023-06-15 16:58
To: juzhe.zhong@rivai.ai; rguenther
CC: rdapp.gcc; gcc-patches; richard.sandiford; krebbel; uweigand; linkw
Subject: Re: [PATCH V2] VECT: Support LEN_MASK_ LOAD/STORE to support flow control for length loop control
>>> Can you try using the same wording for length and mask operands
>>> as for len_load and maskload? Also len_load has the "bias"
>>> operand which you omit here - IIRC that was added for s390 which
>>> for unknown reason behaves a little different than power. If
>>> len support for s390 ever extends to other ops or power or s390
>>> gain mask support for conditional code we'd likely have to adjust
>>> each optab you add. Maybe it's better to add the bias operand
>>> now.
>
> I don't know BIAS well and It seems to be a Power target dependent feature.
> I think len_mask_* in general should only need lenght and mask operand.
> Actually, the function argument is totally same as vp_load/vp_store in LLVM.
>
> Could I just keep current format (without BIAS argument)? And extend it with BIAS if
> PowerPC want to use LEN_MASK_ * ?
FYI: The only proper user of bias is s390 because the insns cannot handle a
zero length. Power doesn't actually need it. What we do is just subtract the
bias (== 1) from the length in case of n_rgroups == 1 and nothing for
bias == 0 so the actually bias support code needed is small.
Regards
Robin
next prev parent reply other threads:[~2023-06-15 9:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-12 4:14 juzhe.zhong
2023-06-15 8:06 ` Richard Biener
2023-06-15 8:47 ` juzhe.zhong
2023-06-15 8:58 ` Robin Dapp
2023-06-15 9:01 ` juzhe.zhong [this message]
2023-06-15 9:15 ` Richard Biener
2023-06-15 9:18 ` Robin Dapp
2023-06-15 9:20 ` Robin Dapp
2023-06-15 9:52 ` Richard Biener
2023-06-15 10:08 ` juzhe.zhong
2023-06-15 10:10 ` Robin Dapp
2023-06-15 11:12 ` Richard Biener
[not found] ` <2023061516473052116877@rivai.ai>
2023-06-15 8:56 ` juzhe.zhong
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=6439A2EB450AD2A3+2023061517010183215980@rivai.ai \
--to=juzhe.zhong@rivai.ai \
--cc=gcc-patches@gcc.gnu.org \
--cc=krebbel@linux.ibm.com \
--cc=linkw@linux.ibm.com \
--cc=rdapp.gcc@gmail.com \
--cc=rguenther@suse.de \
--cc=richard.sandiford@arm.com \
--cc=uweigand@de.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).