From: Jason Merrill <jason@redhat.com>
To: nick huang <nickhuang99@hotmail.com>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: *PING* [PATCH] c++: fix cases of core1001/1322 by not dropping cv-qualifier of function parameter of type of typename or decltype[PR101402,PR102033,PR102034,PR102039,PR102044]
Date: Fri, 24 Sep 2021 15:11:49 -0400 [thread overview]
Message-ID: <5757d35b-3562-5ab8-5062-8ff806d32693@redhat.com> (raw)
In-Reply-To: <DM5PR0501MB3733B7CEBDE5E578EF5244ACB5A49@DM5PR0501MB3733.namprd05.prod.outlook.com>
I already responded to this patch:
https://gcc.gnu.org/pipermail/gcc-patches/2021-September/579527.html
next prev parent reply other threads:[~2021-09-24 19:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-31 13:55 nick huang
2021-09-15 23:00 ` Jason Merrill
2021-09-24 11:14 ` *PING* " nick huang
2021-09-24 19:11 ` Jason Merrill [this message]
2021-09-25 19:15 ` nick huang
2021-09-28 14:00 ` Jason Merrill
2021-09-27 3:40 ` nick huang
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=5757d35b-3562-5ab8-5062-8ff806d32693@redhat.com \
--to=jason@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=nickhuang99@hotmail.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).