public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Li, Pan2" <pan2.li@intel.com>
To: Jeff Law <jeffreyalaw@gmail.com>,
	"juzhe.zhong@rivai.ai" <juzhe.zhong@rivai.ai>,
	gcc-patches <gcc-patches@gcc.gnu.org>
Cc: Robin Dapp <rdapp.gcc@gmail.com>,
	"Wang, Yanzhang" <yanzhang.wang@intel.com>,
	kito.cheng <kito.cheng@gmail.com>
Subject: RE: [PATCH v3] RISC-V: Bugfix for vec_init repeating auto vectorization in RV32
Date: Thu, 15 Jun 2023 01:05:55 +0000	[thread overview]
Message-ID: <MW5PR11MB5908A8D409057A9952844269A95BA@MW5PR11MB5908.namprd11.prod.outlook.com> (raw)
In-Reply-To: <de0fd473-9220-8f62-80cd-c954bdc1ddfc@gmail.com>

Committed, thanks Jeff and Juzhe.

Pan

-----Original Message-----
From: Jeff Law <jeffreyalaw@gmail.com> 
Sent: Thursday, June 15, 2023 2:56 AM
To: juzhe.zhong@rivai.ai; Li, Pan2 <pan2.li@intel.com>; gcc-patches <gcc-patches@gcc.gnu.org>
Cc: Robin Dapp <rdapp.gcc@gmail.com>; Wang, Yanzhang <yanzhang.wang@intel.com>; kito.cheng <kito.cheng@gmail.com>
Subject: Re: [PATCH v3] RISC-V: Bugfix for vec_init repeating auto vectorization in RV32



On 6/14/23 03:01, juzhe.zhong@rivai.ai wrote:
> LGTM
Agreed.  Commit when convenient.

jeff

      reply	other threads:[~2023-06-15  1:06 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-14  0:58 [PATCH v1] " pan2.li
2023-06-14  1:07 ` juzhe.zhong
2023-06-14  7:30   ` Li, Pan2
2023-06-14  7:29 ` [PATCH v2] " pan2.li
2023-06-14  7:43   ` juzhe.zhong
2023-06-14  8:27   ` Robin Dapp
2023-06-14  8:34     ` Li, Pan2
2023-06-14  9:00 ` [PATCH v3] " pan2.li
2023-06-14  9:01   ` juzhe.zhong
2023-06-14 18:56     ` Jeff Law
2023-06-15  1:05       ` Li, Pan2 [this message]

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