public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "juzhe.zhong@rivai.ai" <juzhe.zhong@rivai.ai>
To: "Robin Dapp" <rdapp.gcc@gmail.com>,  pan2.li <pan2.li@intel.com>,
	 rguenther <rguenther@suse.de>
Cc: "Robin Dapp" <rdapp.gcc@gmail.com>,
	 gcc-patches <gcc-patches@gcc.gnu.org>,
	 jeffreyalaw <jeffreyalaw@gmail.com>,
	 kito.cheng <kito.cheng@gmail.com>
Subject: Re: Re: [PATCH] Prevent TYPE_PRECISION on VECTOR_TYPEs
Date: Thu, 29 Jun 2023 18:09:31 +0800	[thread overview]
Message-ID: <AE879E728D9ED86E+2023062918093033877149@rivai.ai> (raw)
In-Reply-To: <9dd830c0-71b6-1de2-f2ab-d208dfa87197@gmail.com>

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

Yes. Thanks for taking care of it!


juzhe.zhong@rivai.ai
 
From: Robin Dapp
Date: 2023-06-29 18:07
To: juzhe.zhong@rivai.ai; pan2.li; Richard Biener
CC: rdapp.gcc; gcc-patches; jeffreyalaw; kito.cheng
Subject: Re: [PATCH] Prevent TYPE_PRECISION on VECTOR_TYPEs
Ah, the one sub-thread continued before you were CC'ed.
Sorry about that.
 
Regards
Robin
 

  reply	other threads:[~2023-06-29 10:09 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-27  9:45 Richard Biener
2023-06-27  9:47 ` Jakub Jelinek
2023-06-29  4:04   ` Li, Pan2
2023-06-29  4:18     ` Li, Pan2
2023-06-29 10:03       ` juzhe.zhong
2023-06-29 10:06         ` Robin Dapp
2023-06-29 10:07           ` Robin Dapp
2023-06-29 10:09             ` juzhe.zhong [this message]
2023-06-29  4:25     ` Jeff Law
2023-06-29  8:11       ` Richard Biener
2023-06-29  9:55         ` Robin Dapp
2023-06-29  9:56           ` Richard Biener
2023-06-29 11:07             ` Robin Dapp
2023-06-29 15:13         ` Jeff Law

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