From: Jason Merrill <jason@redhat.com>
To: Nick Huang <nickhuang99@gmail.com>
Cc: nick huang <nickhuang99@hotmail.com>,
Gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] c++: Suppress error when cv-qualified reference is introduced by typedef [PR101783]
Date: Fri, 1 Oct 2021 11:45:57 -0400 [thread overview]
Message-ID: <083cc6db-55bf-3b9c-efeb-c71ed5171c09@redhat.com> (raw)
In-Reply-To: <CAP6LXBsLBAfoViCCXhTFKxO3NvDRR582hiFvCrpTfp-T1N_z1g@mail.gmail.com>
On 10/1/21 11:10, Nick Huang wrote:
>> gcc-verify still fails with this version:
>>
>>> ERR: line should start with a tab: " PR c++/101783"
>>> ERR: line should start with a tab: " * tree.c (cp_build_qualified_type_real): Excluding typedef from error"
>>> ERR: line should start with a tab: " PR c++/101783"
>>> ERR: line should start with a tab: " * g++.dg/parse/pr101783.C: New test."
>
>> It might work better to attach the output of git format-patch.
> Sorry for my clumsy copy/paste from git commit message. I now attach
> git format-patch output
> file as attachment. Also maybe for a little convenience of your work,
> I also attach the original
> commit message file when I do git commit -F.
Thanks, but that isn't necessary; it should be the same in the
format-patch output, except...
> From e592a475030d99647de736d294cb3c6a7588af49 Mon Sep 17 00:00:00 2001
> From: qingzhe huang <nickhuang99@hotmail.com>
> Date: Fri, 1 Oct 2021 10:46:35 -0400
> Subject: [PATCH] The root cause of this bug is that it considers reference
> with cv-qualifiers as an error by generating value for variable "bad_quals".
> However, this is not correct for case of typedef. Here I quote spec
> [dcl.ref]/1 : "Cv-qualified references are ill-formed except when the
> cv-qualifiers are introduced through the use of a typedef-name
> ([dcl.typedef], [temp.param]) or decltype-specifier ([dcl.type.decltype]), in
> which case the cv-qualifiers are ignored."
...the subject line for the commit should be the first line of the
commit message, followed by a blank line, followed by the description of
the patch; without the subject line, git format-patch thought your whole
description was the subject of the patch.
I've corrected this and pushed the patch, thanks!
Jason
next prev parent reply other threads:[~2021-10-01 15:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAP6LXBsdU3xULuu8B3cEDGbcpHUXxF4roCC-zboWmtpGoPdVvw@mail.gmail.com>
2021-09-27 1:31 ` nick huang
2021-09-28 19:51 ` Jason Merrill
2021-09-30 18:24 ` nick huang
2021-10-01 13:29 ` Jason Merrill
2021-10-01 15:10 ` Nick Huang
2021-10-01 15:45 ` Jason Merrill [this message]
2021-10-01 19:52 ` Nick Huang
2021-10-05 19:40 ` Jason Merrill
2021-08-10 5:36 [PATCH] c++: Fix unnecessary error when top-level cv-qualifiers is dropped [PR101783] nick huang
2021-08-28 11:54 ` [PATCH] c++: Suppress error when cv-qualified reference is introduced by typedef [PR101783] nick huang
2021-09-24 20:33 ` Jason Merrill
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=083cc6db-55bf-3b9c-efeb-c71ed5171c09@redhat.com \
--to=jason@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=nickhuang99@gmail.com \
--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).