public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
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>,
	 rdapp.gcc <rdapp.gcc@gmail.com>
Subject: Re: Re: [PATCH V7] RISC-V: RISC-V: Support gather_load/scatter RVV auto-vectorization
Date: Thu, 13 Jul 2023 06:17:39 +0800	[thread overview]
Message-ID: <A2543C61996CA6E6+2023071306173875576112@rivai.ai> (raw)
In-Reply-To: <241ccf47-0579-7d7b-0dcf-7847328fe7a8@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1073 bytes --]

Thanks Jeff.
Will commit with formating the codes.

I am gonna first support COND_FMA and reduction.... first (which I think is higher priority).
Then come back support strided_load/store.

Thanks.



juzhe.zhong@rivai.ai
 
发件人： Jeff Law
发送时间： 2023-07-13 05:48
收件人： 钟居哲; gcc-patches
抄送： kito.cheng; kito.cheng; rdapp.gcc
主题： Re: 回复: Re: [PATCH V7] RISC-V: RISC-V: Support gather_load/scatter RVV auto-vectorization
 
 
On 7/12/23 15:22, 钟居哲 wrote:
> I have removed strided load/store, instead, I will support strided 
> load/store in vectorizer later.
> 
> Ok for trunk?
Assuming this removes the strided loads/stores while we figure out the 
best way to support them, OK for the trunk.  The formatting is so messed 
up that it's nearly impossible to read.
 
 
 
Note for the future, if you hit the message size limit, go ahead and 
gzip the patch.  That's better than forwarding from a failed message as 
the latter mucks up indention so bad that the result is unreadable.
 
Jeff
 

  reply	other threads:[~2023-07-12 22:17 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-12  9:38 juzhe.zhong
     [not found] ` <66564378DDCC57ED+202307121748494317959@rivai.ai>
2023-07-12 21:22   ` 回复: " 钟居哲
2023-07-12 21:48     ` Jeff Law
2023-07-12 22:17       ` 钟居哲 [this message]
2023-07-12 22:25         ` Jeff Law
2023-07-12 23:30           ` 钟居哲
2023-07-13  7:47             ` Richard Biener
2023-07-13 14:01               ` Jeff Law
2023-07-13 14:05                 ` Palmer Dabbelt
2023-07-13 14:32                   ` Robin Dapp
2023-07-13 14:42                     ` 钟居哲
2023-07-13 13:58             ` Jeff Law
2023-07-13  1:12       ` 回复: " Li, Pan2

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=A2543C61996CA6E6+2023071306173875576112@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=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).