From: "juzhe.zhong@rivai.ai" <juzhe.zhong@rivai.ai>
To: Kito.cheng <kito.cheng@sifive.com>, jeffreyalaw <jeffreyalaw@gmail.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>,
kito.cheng <kito.cheng@gmail.com>, palmer <palmer@dabbelt.com>,
palmer <palmer@rivosinc.com>,
"Robin Dapp" <rdapp.gcc@gmail.com>
Subject: Re: Re: [PATCH V2] RISC-V: Fix bug of pre-calculated const vector mask
Date: Wed, 28 Jun 2023 14:17:08 +0800 [thread overview]
Message-ID: <07788792B88C159A+202306281417079645052@rivai.ai> (raw)
In-Reply-To: <CALLt3TiPc2NXCuu_hrmP=+KWYfzUTBqe-zewnP5bcGXAU35VFQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2196 bytes --]
The difference between v1 and v2 is the compact mask generation:
v1 :
+rtx
+rvv_builder::compact_mask () const
+{
+ /* Use the container mode with SEW = 8 and LMUL = 1. */
+ unsigned container_size
+ = MAX (CEIL (npatterns (), 8), BYTES_PER_RISCV_VECTOR.to_constant () / 8);
+ machine_mode container_mode
+ = get_vector_mode (QImode, container_size).require ();...
v2:
+rtx
+rvv_builder::get_compact_mask () const
+{
+ /* If TARGET_MIN_VLEN == 32, the minimum LMUL = 1/4.
+ Otherwise, the minimum LMUL = 1/8. */
+ unsigned min_lmul = TARGET_MIN_VLEN == 32 ? 4 : 8;
+ unsigned min_container_size
+ = BYTES_PER_RISCV_VECTOR.to_constant () / min_lmul;
+ unsigned container_size = MAX (CEIL (npatterns (), 8), min_container_size);
+ machine_mode container_mode
+ = get_vector_mode (QImode, container_size).require ();...
The difference is that v1:
unsigned container_size = MAX (CEIL (npatterns (), 8), BYTES_PER_RISCV_VECTOR.to_constant () / 8);
v2:
+ /* If TARGET_MIN_VLEN == 32, the minimum LMUL = 1/4.
+ Otherwise, the minimum LMUL = 1/8. */
+ unsigned min_lmul = TARGET_MIN_VLEN == 32 ? 4 : 8;
+ unsigned min_container_size
+ = BYTES_PER_RISCV_VECTOR.to_constant () / min_lmul;
+ unsigned container_size = MAX (CEIL (npatterns (), 8), min_container_size);
juzhe.zhong@rivai.ai
From: Kito Cheng
Date: 2023-06-28 14:01
To: Jeff Law
CC: juzhe.zhong@rivai.ai; gcc-patches; kito.cheng; palmer; palmer; Robin Dapp
Subject: Re: [PATCH V2] RISC-V: Fix bug of pre-calculated const vector mask
I mean the difference between v1 and v2 patch
On Wed, Jun 28, 2023 at 12:09 PM Jeff Law <jeffreyalaw@gmail.com> wrote:
>
>
>
> On 6/27/23 21:16, Kito Cheng wrote:
> > Do you mind giving some comments about what the difference between the
> > two versions?
> And I'd like a before/after assembly code with the example in the commit
> message. I didn't see the same behavior when I tried it earlier today
> and ran out of time to dig into it further.
>
> Juzhe -- most folks wait ~1wk to ping patches, even codegen bugfixes.
> Pinging this fast runs the risk of irritating others. Please be patient.
>
> Jeff
next prev parent reply other threads:[~2023-06-28 6:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-28 1:59 Juzhe-Zhong
2023-06-28 3:14 ` juzhe.zhong
2023-06-28 3:16 ` Kito Cheng
2023-06-28 3:19 ` juzhe.zhong
2023-06-28 4:09 ` Jeff Law
2023-06-28 6:01 ` Kito Cheng
2023-06-28 6:17 ` juzhe.zhong [this message]
2023-06-28 7:17 ` Richard Biener
2023-06-28 7:38 ` juzhe.zhong
2023-06-28 8:15 ` juzhe.zhong
2023-06-28 9:50 ` 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=07788792B88C159A+202306281417079645052@rivai.ai \
--to=juzhe.zhong@rivai.ai \
--cc=gcc-patches@gcc.gnu.org \
--cc=jeffreyalaw@gmail.com \
--cc=kito.cheng@gmail.com \
--cc=kito.cheng@sifive.com \
--cc=palmer@dabbelt.com \
--cc=palmer@rivosinc.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).