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>,
kito.cheng <kito.cheng@sifive.com>, palmer <palmer@dabbelt.com>,
palmer <palmer@rivosinc.com>, rdapp.gcc <rdapp.gcc@gmail.com>
Subject: Re: Re: [PATCH V3] RISC-V: Fix bug of pre-calculated const vector mask for VNx1BI, VNx2BI and VNx4BI
Date: Thu, 29 Jun 2023 03:02:55 +0800 [thread overview]
Message-ID: <59DD619A76E2AC1A+2023062903025467496516@rivai.ai> (raw)
In-Reply-To: <b3be2525-7505-192c-ca04-141e93ab2ee7@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1575 bytes --]
Try this:
https://godbolt.org/z/x7bM5Pr84
juzhe.zhong@rivai.ai
From: Jeff Law
Date: 2023-06-29 02:11
To: Juzhe-Zhong; gcc-patches
CC: kito.cheng; kito.cheng; palmer; palmer; rdapp.gcc
Subject: Re: [PATCH V3] RISC-V: Fix bug of pre-calculated const vector mask for VNx1BI, VNx2BI and VNx4BI
On 6/28/23 03:47, Juzhe-Zhong wrote:
> This bug blocks the following patches.
>
> GCC doesn't know RVV is using compact mask model.
> Consider this following case:
>
> #define N 16
>
> int
> main ()
> {
> int8_t mask[N] = {0, 1, 0, 1, 0, 1, 0, 1, 0, 1, 0, 1, 0, 1, 0, 1};
> int8_t out[N] = {0};
> for (int8_t i = 0; i < N; ++i)
> if (mask[i])
> out[i] = i;
> for (int8_t i = 0; i < N; ++i)
> {
> if (mask[i])
> assert (out[i] == i);
> else
> assert (out[i] == 0);
> }
> }
>
> Before this patch, the pre-calculated mask in constant memory pool:
> .LC1:
> .byte 68 ====> 0b01000100
>
> This is incorrect, such case failed in execution.
>
> After this patch:
> .LC1:
> .byte 10 ====> 0b1010
So I don't get anything like this in my testing. What are the precise
arguments you're using to build the testcase?
I'm compiling the test use a trunk compiler with
-O3 --param riscv-autovec-preference=fixed-vlmax -march=rv64gcv
I get the attached code both before and after your patch. Clearly I'm
doing something different/wrong. So my request is for the precise
command line you're using and the before/after resulting assembly code.
Jeff
next prev parent reply other threads:[~2023-06-28 19:03 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-28 9:47 Juzhe-Zhong
2023-06-28 18:11 ` Jeff Law
2023-06-28 19:02 ` 钟居哲 [this message]
2023-06-28 19:12 ` Robin Dapp
2023-06-28 20:42 ` Richard Sandiford
2023-06-28 21:46 ` 钟居哲
2023-06-29 7:53 ` Richard Sandiford
2023-06-29 8:08 ` juzhe.zhong
2023-06-29 8:14 ` Robin Dapp
2023-06-29 8:18 ` juzhe.zhong
2023-06-29 8:53 ` Robin Dapp
2023-06-29 9:01 ` juzhe.zhong
2023-06-29 8:54 ` Richard Sandiford
2023-06-29 9:09 ` Robin Dapp
2023-06-29 9:23 ` juzhe.zhong
2023-06-29 11:22 ` Richard Biener
2023-06-29 11:38 ` Robin Dapp
2023-06-29 13:53 ` Kito Cheng
2023-06-29 14:04 ` Richard Sandiford
2023-06-29 14:12 ` Robin Dapp
2023-07-04 19:07 ` Robin Dapp
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=59DD619A76E2AC1A+2023062903025467496516@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).