From: Jakub Jelinek <jakub@redhat.com>
To: Qing Zhao <qing.zhao@oracle.com>
Cc: Richard Biener <rguenther@suse.de>,
gcc-patches Nick Alcock via <gcc-patches@gcc.gnu.org>
Subject: Re: [Version 2][Patch][PR102281]do not add BUILTIN_CLEAR_PADDING for variables that are gimple registers
Date: Fri, 29 Oct 2021 18:58:15 +0200 [thread overview]
Message-ID: <20211029165815.GE304296@tucnak> (raw)
In-Reply-To: <6CCECB7B-E672-4664-98FB-BA1D3E454009@oracle.com>
On Fri, Oct 29, 2021 at 04:55:07PM +0000, Qing Zhao wrote:
> I will commit this patch the beginning of next week.
> Jakub, let me know if you have any objection on this.
No objections, sorry for the delay.
Jakub
prev parent reply other threads:[~2021-10-29 16:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-18 19:26 Qing Zhao
2021-10-20 16:29 ` Qing Zhao
2021-10-25 14:16 ` Qing Zhao
2021-10-28 14:18 ` Qing Zhao
2021-10-29 7:21 ` Richard Biener
2021-10-29 16:55 ` Qing Zhao
2021-10-29 16:58 ` Jakub Jelinek [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=20211029165815.GE304296@tucnak \
--to=jakub@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=qing.zhao@oracle.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).