public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Li, Pan2" <pan2.li@intel.com>
To: Kito Cheng <kito.cheng@gmail.com>,
	"juzhe.zhong@rivai.ai" <juzhe.zhong@rivai.ai>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>,
	Kito.cheng <kito.cheng@sifive.com>,
	"Wang, Yanzhang" <yanzhang.wang@intel.com>
Subject: RE: Re: [PATCH] RISC-V: Allow VMS{Compare} (V1, V1) shortcut optimization
Date: Wed, 19 Apr 2023 10:33:11 +0000	[thread overview]
Message-ID: <MW5PR11MB5908E19E11E34FA329A04D65A9629@MW5PR11MB5908.namprd11.prod.outlook.com> (raw)
In-Reply-To: <CA+yXCZA3DLkKKyWAjT_GFDzJJj59xT_dW=5=+k-jWiPaoGba2g@mail.gmail.com>

Sure thing.

For Changlog, I consider it was generated automatically in previous. LOL.

Pan

-----Original Message-----
From: Kito Cheng <kito.cheng@gmail.com> 
Sent: Wednesday, April 19, 2023 5:46 PM
To: juzhe.zhong@rivai.ai
Cc: Li, Pan2 <pan2.li@intel.com>; gcc-patches <gcc-patches@gcc.gnu.org>; Kito.cheng <kito.cheng@sifive.com>; Wang, Yanzhang <yanzhang.wang@intel.com>
Subject: Re: Re: [PATCH] RISC-V: Allow VMS{Compare} (V1, V1) shortcut optimization

HI JuZhe:

Thanks for explaining!


Hi Pan:

I think that would be helpful if JuZhe's explaining that could be written into the commit log.


> gcc/ChangeLog:
>
>        * config/riscv/riscv-v.cc (emit_pred_op):
>        * config/riscv/riscv-vector-builtins-bases.cc:
>        * config/riscv/vector.md:

And don't forgot write some thing in ChangeLog...:P

  reply	other threads:[~2023-04-19 10:33 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-19  3:21 pan2.li
2023-04-19  8:49 ` Li, Pan2
2023-04-19  9:34   ` Kito Cheng
2023-04-19  9:41     ` juzhe.zhong
2023-04-19  9:45       ` Kito Cheng
2023-04-19 10:33         ` Li, Pan2 [this message]
2023-04-19 11:26           ` Li, Pan2
2023-04-21  9:46             ` Li, Pan2
2023-04-21 10:16               ` Kito Cheng
2023-04-21 11:16                 ` Li, Pan2
2023-04-21 13:01                   ` Kito Cheng
2023-04-22  5:33                     ` Li, Pan2
2023-04-25 13:08                       ` Kito Cheng
2023-04-25 13:51                         ` Li, Pan2
2023-04-25 13:56                           ` Kito Cheng
2023-04-25 14:11                             ` Li, Pan2
2023-04-26  2:04                               ` Li, Pan2
2023-04-19 11:23 ` [PATCH v2] " pan2.li

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=MW5PR11MB5908E19E11E34FA329A04D65A9629@MW5PR11MB5908.namprd11.prod.outlook.com \
    --to=pan2.li@intel.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=juzhe.zhong@rivai.ai \
    --cc=kito.cheng@gmail.com \
    --cc=kito.cheng@sifive.com \
    --cc=yanzhang.wang@intel.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).