public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Sandiford <richard.sandiford@arm.com>
To: "juzhe.zhong\@rivai.ai" <juzhe.zhong@rivai.ai>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>,  rguenther <rguenther@suse.de>
Subject: Re: [PATCH V7] VECT: Add decrement IV support in Loop Vectorizer
Date: Tue, 16 May 2023 09:30:03 +0100	[thread overview]
Message-ID: <mpth6sc3chg.fsf@arm.com> (raw)
In-Reply-To: <C7BDACE93D41EA98+2023051616234703899845@rivai.ai> (juzhe's message of "Tue, 16 May 2023 16:23:47 +0800")

"juzhe.zhong@rivai.ai" <juzhe.zhong@rivai.ai> writes:
> Hi, Richard.
>
> RVV infrastructure in RISC-V backend status:
> 1. All RVV instructions pattern related to intrinsics are all finished (They will be called not only by intrinsics but also autovec in the future).
> 2. In case of autovec, we finished len_load/len_store (They are temporary used and will be removed after I support len_mask_load/len_mask_store in the middle-end).
>    binary integer autovec patterns.
>    vec_init pattern.
>    That's all we have so far.

Thanks.

> In case of testing of this patch, I have multiple rgroup testcases in local, you mean you want me to post them together with this patch?
> Since I am gonna to put them in RISC-V backend testsuite, I was planning to post them after this patch is finished and merged into trunk.
> What do you suggest ?

It would be useful to include the tests with the patch itself (as a patch
to the testsuite).  It doesn't matter that the tests are riscv-specific.

Obviously it would be more appropriate for the riscv maintainers to
review the riscv tests.  But keeping the tests with the patch helps when
reviewing the code, and also ensures that code is committed and never
later tested.

Richard

  reply	other threads:[~2023-05-16  8:30 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-15  1:28 juzhe.zhong
2023-05-15 19:44 ` Richard Sandiford
2023-05-15 21:20   ` 钟居哲
2023-05-16  4:32   ` juzhe.zhong
2023-05-16  6:57     ` Richard Sandiford
2023-05-16  7:22       ` juzhe.zhong
2023-05-16  7:35       ` juzhe.zhong
2023-05-16  7:39       ` juzhe.zhong
2023-05-16  8:16         ` Richard Sandiford
2023-05-16  8:23           ` juzhe.zhong
2023-05-16  8:30             ` Richard Sandiford [this message]
2023-05-16  9:25               ` juzhe.zhong
2023-05-16 10:25               ` juzhe.zhong
2023-05-16 11:23               ` 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=mpth6sc3chg.fsf@arm.com \
    --to=richard.sandiford@arm.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=juzhe.zhong@rivai.ai \
    --cc=rguenther@suse.de \
    /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).