From: Michael Collison <collison@rivosinc.com>
To: juzhe.zhong@rivai.ai, "kito.cheng" <kito.cheng@gmail.com>,
"richard.guenther" <richard.guenther@gmail.com>,
Jeff Law <jeffreyalaw@gmail.com>, palmer <palmer@dabbelt.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH v4 07/10] vect: Verify that GET_MODE_NUNITS is a multiple of 2.
Date: Tue, 18 Apr 2023 19:19:47 -0400 [thread overview]
Message-ID: <d03122b6-fc9d-c521-fce9-51fcd304f7ea@rivosinc.com> (raw)
In-Reply-To: <FF8B40A3142277E8+202304190648511512504@rivai.ai>
[-- Attachment #1: Type: text/plain, Size: 6185 bytes --]
Juzhe and Kito,
Thank you for the clarification.
On 4/18/23 18:48, juzhe.zhong@rivai.ai wrote:
> Yes, like kito said.
> We won't enable VNx1DImode in auto-vectorization so it's meaningless
> to fix it here.
> We dynamic adjust the minimum vector-length for different '-march'
> according to RVV ISA specification.
> So we strongly suggest that we should drop this fix.
>
> Thanks.
> ------------------------------------------------------------------------
> juzhe.zhong@rivai.ai
>
> *From:* Kito Cheng <mailto:kito.cheng@gmail.com>
> *Date:* 2023-04-19 02:21
> *To:* Richard Biener <mailto:richard.guenther@gmail.com>; Jeff Law
> <mailto:jeffreyalaw@gmail.com>; Palmer Dabbelt
> <mailto:palmer@dabbelt.com>
> *CC:* Michael Collison <mailto:collison@rivosinc.com>; gcc-patches
> <mailto:gcc-patches@gcc.gnu.org>; 钟居哲 <mailto:juzhe.zhong@rivai.ai>
> *Subject:* Re: [PATCH v4 07/10] vect: Verify that GET_MODE_NUNITS
> is a multiple of 2.
> Few more background about RVV:
> RISC-V has provide different VLEN configuration by different ISA
> extension like `zve32x`, `zve64x` and `v`
> zve32x just guarantee the minimal VLEN is 32 bits,
> zve64x guarantee the minimal VLEN is 64 bits,
> and v guarantee the minimal VLEN is 128 bits,
> Current status (without that patch):
> Zve32x: Mode for one vector register mode is VNx1SImode and VNx1DImode
> is invalid mode
> - one vector register could hold 1 + 1x SImode where x is 0~n, so it
> might hold just one SI
> Zve64x: Mode for one vector register mode is VNx1DImode or VNx2SImode
> - one vector register could hold 1 + 1x DImode where x is 0~n, so it
> might hold just one DI
> - one vector register could hold 2 + 2x SImode where x is 0~n, so it
> might hold just two SI
> So what I want to say here is VNx1DImode is really NOT safe to assume
> to have more than two DI in theory.
> However `v` extension guarantees the minimal VLEN is 128 bits.
> We are trying to introduce another type/mode mapping for this
> configure:
> v: Mode for one vector register mode is VNx2DImode or VNx4SImode
> - one vector register could hold 2 + 2x DImode where x is 0~n, so it
> will hold at least two DI
> - one vector register could hold 4 + 4x SImode where x is 0~n, so it
> will hold at least four DI
> So GET_MODE_NUNITS for a single vector register with DI mode will
> become 2 (VNx2DImode) if it is really possible, which is a more
> precise way to model the vector extension for RISC-V .
> On Tue, Apr 18, 2023 at 10:28 PM Kito Cheng <kito.cheng@gmail.com>
> wrote:
> >
> > Wait, VNx1DImode can be really evaluate to just one element if
> > -march=rv64g_zve64x,
> >
> > I thinks this should be just fixed on backend by this patch:
> >
> >
> https://patchwork.ozlabs.org/project/gcc/patch/20230414014518.15458-1-juzhe.zhong@rivai.ai/
> >
> > On Tue, Apr 18, 2023 at 2:12 PM Richard Biener via Gcc-patches
> > <gcc-patches@gcc.gnu.org> wrote:
> > >
> > > On Mon, Apr 17, 2023 at 8:42 PM Michael Collison
> <collison@rivosinc.com> wrote:
> > > >
> > > > While working on autovectorizing for the RISCV port I
> encountered an issue
> > > > where can_duplicate_and_interleave_p assumes that
> GET_MODE_NUNITS is a
> > > > evenly divisible by two. The RISC-V target has vector modes
> (e.g. VNx1DImode),
> > > > where GET_MODE_NUNITS is equal to one.
> > > >
> > > > Tested on RISCV and x86_64-linux-gnu. Okay?
> > >
> > > OK.
> > >
> > > > 2023-03-09 Michael Collison <collison@rivosinc.com>
> > > >
> > > > * tree-vect-slp.cc (can_duplicate_and_interleave_p):
> > > > Check that GET_MODE_NUNITS is a multiple of 2.
> > > > ---
> > > > gcc/tree-vect-slp.cc | 7 +++++--
> > > > 1 file changed, 5 insertions(+), 2 deletions(-)
> > > >
> > > > diff --git a/gcc/tree-vect-slp.cc b/gcc/tree-vect-slp.cc
> > > > index d73deaecce0..a64fe454e19 100644
> > > > --- a/gcc/tree-vect-slp.cc
> > > > +++ b/gcc/tree-vect-slp.cc
> > > > @@ -423,10 +423,13 @@ can_duplicate_and_interleave_p
> (vec_info *vinfo, unsigned int count,
> > > > (GET_MODE_BITSIZE (int_mode), 1);
> > > > tree vector_type
> > > > = get_vectype_for_scalar_type (vinfo, int_type,
> count);
> > > > + poly_int64 half_nelts;
> > > > if (vector_type
> > > > && VECTOR_MODE_P (TYPE_MODE (vector_type))
> > > > && known_eq (GET_MODE_SIZE (TYPE_MODE
> (vector_type)),
> > > > - GET_MODE_SIZE (base_vector_mode)))
> > > > + GET_MODE_SIZE (base_vector_mode))
> > > > + && multiple_p (GET_MODE_NUNITS (TYPE_MODE
> (vector_type)),
> > > > + 2, &half_nelts))
> > > > {
> > > > /* Try fusing consecutive sequences of COUNT /
> NVECTORS elements
> > > > together into elements of type INT_TYPE and
> using the result
> > > > @@ -434,7 +437,7 @@ can_duplicate_and_interleave_p (vec_info
> *vinfo, unsigned int count,
> > > > poly_uint64 nelts = GET_MODE_NUNITS (TYPE_MODE
> (vector_type));
> > > > vec_perm_builder sel1 (nelts, 2, 3);
> > > > vec_perm_builder sel2 (nelts, 2, 3);
> > > > - poly_int64 half_nelts = exact_div (nelts, 2);
> > > > +
> > > > for (unsigned int i = 0; i < 3; ++i)
> > > > {
> > > > sel1.quick_push (i);
> > > > --
> > > > 2.34.1
> > > >
>
next prev parent reply other threads:[~2023-04-18 23:19 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-17 18:36 [PATCH v4 00/10] RISC-V: Add autovec support Michael Collison
2023-04-17 18:36 ` [PATCH v4 01/10] RISC-V: Add new predicates and function prototypes Michael Collison
2023-04-19 0:54 ` Kito Cheng
2023-04-26 2:50 ` Jeff Law
2023-04-17 18:36 ` [PATCH v4 02/10] RISC-V: autovec: Export policy functions to global scope Michael Collison
2023-04-17 18:36 ` [PATCH v4 03/10] RISC-V:autovec: Add auto-vectorization support functions Michael Collison
2023-04-19 1:15 ` Kito Cheng
2023-04-20 2:19 ` juzhe.zhong
2023-04-17 18:36 ` [PATCH v4 04/10] RISC-V:autovec: Add target vectorization hooks Michael Collison
2023-04-19 1:04 ` Kito Cheng
2023-04-20 2:11 ` juzhe.zhong
2023-04-17 18:36 ` [PATCH v4 05/10] RISC-V:autovec: Add autovectorization patterns for binary integer operations Michael Collison
2023-04-18 23:14 ` Jeff Law
2023-04-19 1:19 ` Kito Cheng
2023-04-20 20:21 ` Michael Collison
2023-04-20 2:24 ` juzhe.zhong
2023-04-26 18:15 ` Robin Dapp
[not found] ` <3DF5ADD87A33EE11+BA2E4625-72A4-421A-B9D3-6DCA48E402BD@rivai.ai>
2023-04-27 0:04 ` [PATCH v4 05/10] RISC-V: autovec: " Michael Collison
2023-04-27 16:20 ` Palmer Dabbelt
2023-04-17 18:36 ` [PATCH v4 06/10] RISC-V:autovec: Add autovectorization tests for add & sub Michael Collison
2023-04-17 18:36 ` [PATCH v4 07/10] vect: Verify that GET_MODE_NUNITS is a multiple of 2 Michael Collison
2023-04-18 6:11 ` Richard Biener
2023-04-18 14:28 ` Kito Cheng
2023-04-18 18:21 ` Kito Cheng
2023-04-18 22:48 ` juzhe.zhong
2023-04-18 23:19 ` Michael Collison [this message]
2023-04-20 10:01 ` Richard Sandiford
2023-04-17 18:36 ` [PATCH v4 08/10] RISC-V:autovec: Add autovectorization tests for binary integer Michael Collison
2023-04-17 18:37 ` [PATCH v4 09/10] This patch adds a guard for VNx1 vectors that are present in ports like riscv Michael Collison
2023-04-18 14:26 ` Kito Cheng
2023-04-18 18:10 ` Michael Collison
2023-04-17 18:37 ` [PATCH v4 10/10] This patch supports 8 bit auto-vectorization in riscv Michael Collison
2023-04-17 19:26 ` [PATCH v4 00/10] RISC-V: Add autovec support Palmer Dabbelt
2023-04-18 6:22 ` Richard Biener
2023-04-25 15:26 ` Palmer Dabbelt
2023-04-26 2:52 ` Jeff Law
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=d03122b6-fc9d-c521-fce9-51fcd304f7ea@rivosinc.com \
--to=collison@rivosinc.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jeffreyalaw@gmail.com \
--cc=juzhe.zhong@rivai.ai \
--cc=kito.cheng@gmail.com \
--cc=palmer@dabbelt.com \
--cc=richard.guenther@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).