public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Li, Pan2" <pan2.li@intel.com>
To: Richard Sandiford <richard.sandiford@arm.com>,
	"juzhe.zhong@rivai.ai" <juzhe.zhong@rivai.ai>
Cc: rguenther <rguenther@suse.de>, gcc-patches <gcc-patches@gcc.gnu.org>
Subject: RE: [PATCH V6] VECT: Add SELECT_VL support
Date: Fri, 9 Jun 2023 23:54:24 +0000	[thread overview]
Message-ID: <MW5PR11MB5908B4C8181A9B9C5DF3C6EDA951A@MW5PR11MB5908.namprd11.prod.outlook.com> (raw)
In-Reply-To: <mptwn0cjztg.fsf@arm.com>

Committed with bootstrap and regression test passed, thanks all.

Pan

-----Original Message-----
From: Gcc-patches <gcc-patches-bounces+pan2.li=intel.com@gcc.gnu.org> On Behalf Of Richard Sandiford via Gcc-patches
Sent: Saturday, June 10, 2023 1:44 AM
To: juzhe.zhong@rivai.ai
Cc: rguenther <rguenther@suse.de>; gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH V6] VECT: Add SELECT_VL support

"juzhe.zhong@rivai.ai" <juzhe.zhong@rivai.ai> writes:
> Thanks, Richi.
>
> Should I wait for Richard ACK gain ? 
> Since the last email of this patch, he just asked me to adjust comment no codes change.
> I am not sure whether he is ok.

Yeah, OK from my POV too, thanks.

Richard

  reply	other threads:[~2023-06-09 23:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-09  8:39 juzhe.zhong
2023-06-09  9:20 ` juzhe.zhong
2023-06-09 11:02 ` Richard Biener
2023-06-09 11:16   ` juzhe.zhong
2023-06-09 17:44     ` Richard Sandiford
2023-06-09 23:54       ` Li, Pan2 [this message]
2023-06-09 11:32   ` juzhe.zhong
2023-06-09 14:42     ` Jeff Law
2023-06-09 14:43       ` 钟居哲

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=MW5PR11MB5908B4C8181A9B9C5DF3C6EDA951A@MW5PR11MB5908.namprd11.prod.outlook.com \
    --to=pan2.li@intel.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=juzhe.zhong@rivai.ai \
    --cc=rguenther@suse.de \
    --cc=richard.sandiford@arm.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).