From: 钟居哲 <juzhe.zhong@rivai.ai>
To: "Jeff Law" <jeffreyalaw@gmail.com>,
gcc-patches <gcc-patches@gcc.gnu.org>
Cc: kito.cheng <kito.cheng@gmail.com>, palmer <palmer@dabbelt.com>
Subject: Re: Re: [PATCH] RISC-V: Fix RVV mask mode size
Date: Sat, 17 Dec 2022 10:15:18 +0800 [thread overview]
Message-ID: <216D489F04F5C7C0+2022121710151794078881@rivai.ai> (raw)
In-Reply-To: <75eb29fd-6449-e2d1-2702-d297373cecf3@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2703 bytes --]
>> Most likely than not you end up loading a larger quantity with the high
>> bits zero'd. Interesting that we're using a packed model. I'd been
>> told it was fairly expensive to implement in hardware relative to teh
>> cost of implementing the sparse model.
>> I'm a bit confused by this. GCC can support single bit bools, though
>> ports often extend them to 8 bits or more for computational efficiency
>> purposes. At least that's the case in general. Is there something
>> particularly special about masks & bools that's causing problems?
I am not sure I am on the same page with you. I don't understand what is the
sparse model you said. The only thing I do in this patch is that we change the BYTESIZE VNx1BI for example
as the BYTESIZE of VNx1BI (Original I adjust all mask modes same size as VNx8QImode like LLVM).
And I print the GET_MODE_SIZE (VNx1BI) the value is the same as VNx1QImode so I assume because GCC model 1-bool same as 1-QI???
Actually I not sure but I am sure after this patch, VNx1BI is adjusted smaller size.
Adjusting mask modes as smaller size always beneficial, since we can use vlm && vsm in register spilling, it can reduce the memory consuming and
load store hardware bandwidth.
Unlike LLVM, LLVM make each fractional vector and mask vector same size as LMUL =1 so they use vl1r/vs1r to do the register spilling which is not
optimal.
juzhe.zhong@rivai.ai
From: Jeff Law
Date: 2022-12-17 09:53
To: 钟居哲; gcc-patches
CC: kito.cheng; palmer
Subject: Re: [PATCH] RISC-V: Fix RVV mask mode size
On 12/16/22 18:44, 钟居哲 wrote:
> Yes, VNx4DF only has 4 bit in mask mode in case of load and store.
> For example vlm or vsm we will load store 8-bit ??? (I am not sure
> hardward can load store 4bit,but I am sure it definetly not load store
> the whole register size)
Most likely than not you end up loading a larger quantity with the high
bits zero'd. Interesting that we're using a packed model. I'd been
told it was fairly expensive to implement in hardware relative to teh
cost of implementing the sparse model.
> So ideally it should be model more accurate. However, since GCC assumes
> that 1 BOOL is 1-byte, the only thing I do is to model mask mode as
> smallest as possible.
> Maybe in the future, I can support 1BOOL for 1-bit?? I am not sure since
> it will need to change GCC framework.
I'm a bit confused by this. GCC can support single bit bools, though
ports often extend them to 8 bits or more for computational efficiency
purposes. At least that's the case in general. Is there something
particularly special about masks & bools that's causing problems?
Jeff
next prev parent reply other threads:[~2022-12-17 2:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-14 6:48 juzhe.zhong
2022-12-16 20:22 ` Jeff Law
2022-12-17 1:44 ` 钟居哲
2022-12-17 1:53 ` Jeff Law
2022-12-17 2:15 ` 钟居哲 [this message]
2022-12-19 7:44 ` Richard Biener
2022-12-27 20:46 ` Jeff Law
2023-01-09 7:43 ` Richard Biener
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=216D489F04F5C7C0+2022121710151794078881@rivai.ai \
--to=juzhe.zhong@rivai.ai \
--cc=gcc-patches@gcc.gnu.org \
--cc=jeffreyalaw@gmail.com \
--cc=kito.cheng@gmail.com \
--cc=palmer@dabbelt.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).