From: Marek Polacek <polacek@redhat.com>
To: Nicholas Krause <xerofoify@gmail.com>
Cc: jason@redhat.com, gcc-patches@gcc.gnu.org
Subject: Re: [PATCHv6] Handle TYPE_PACK_EXPANSION in cxx_incomplete_type_diagnostic
Date: Tue, 23 Jun 2020 08:27:42 -0400 [thread overview]
Message-ID: <20200623122742.GE31198@redhat.com> (raw)
In-Reply-To: <492d6701-2247-9fb7-0a26-8e65954d82fb@gmail.com>
On Mon, Jun 22, 2020 at 11:11:48PM -0400, Nicholas Krause wrote:
>
>
> On 6/22/20 10:01 PM, Marek Polacek wrote:
> > On Mon, Jun 22, 2020 at 09:42:51PM -0400, Nicholas Krause via Gcc-patches wrote:
> > > From: Nicholas Krause <xerofoify@gmail.com>
> > >
> > > This fixs the PR95672 by adding the missing TYPE_PACK_EXPANSION case in
> > > cxx_incomplete_type_diagnostic in order to avoid ICES on diagnosing
> > > incomplete template pack expansion cases. In v2, add the missing required
> > > test case for all new patches. v3 Fixes both the test case to compile in
> > > C++11 mode and the message to print out only the type. v4 fixes the testcase
> > > to only target C++11. v5 and v6 fix the test case properly.
> > >
> > > gcc/cp/ChangeLog:
> > >
> > > * typeck2.c (cxx_incomplete_type_diagnostic): Add missing TYPE_EXPANSION_PACK
> > > check for diagnosticing incomplete types in cxx_incomplete_type_diagnostic.
> >
> > It's already been pointed out to you that it's "diagnosing".
> >
> > > gcc/testsuite/ChangeLog:
> > >
> > > * g++.dg/template/PR95672.C: New test.
> > >
> > > Signed-off-by: Nicholas Krause <xerofoify@gmail.com>
> > > ---
> > > gcc/cp/typeck2.c | 6 ++++++
> > > gcc/testsuite/g++.dg/template/PR95672.C | 3 +++
> > > 2 files changed, 9 insertions(+)
> > > create mode 100644 gcc/testsuite/g++.dg/template/PR95672.C
> > >
> > > diff --git a/gcc/cp/typeck2.c b/gcc/cp/typeck2.c
> > > index 5fd3b82fa89..28b32fe0b5a 100644
> > > --- a/gcc/cp/typeck2.c
> > > +++ b/gcc/cp/typeck2.c
> > > @@ -552,6 +552,12 @@ cxx_incomplete_type_diagnostic (location_t loc, const_tree value,
> > > TYPE_NAME (type));
> > > break;
> > > + case TYPE_PACK_EXPANSION:
> > > + emit_diagnostic (diag_kind, loc, 0,
> >
> > Bad indenting.
>
> Sorry seems Jason didn't catch that.
> >
> > > + "invalid use of pack expansion %qT",
> > > + type);
> > > + break;
> > > +
> > > case TYPENAME_TYPE:
> > > case DECLTYPE_TYPE:
> > > emit_diagnostic (diag_kind, loc, 0,
> > > diff --git a/gcc/testsuite/g++.dg/template/PR95672.C b/gcc/testsuite/g++.dg/template/PR95672.C
> > > new file mode 100644
> > > index 00000000000..fcc3da0a132
> > > --- /dev/null
> > > +++ b/gcc/testsuite/g++.dg/template/PR95672.C
> > > @@ -0,0 +1,3 @@
> > > +// PR c++/96572
> > > +// { dg-do compile}
> > > +// { dg-options "-std=c++11" }
> > > +struct g_class : decltype (auto) ... { }; // { dg-error "invalid use of pack expansion" }
> >
> > No, this is completely broken. It passes only because the patch file is
> > malformed and the last line will be lost when applying the patch, so the
> > test is an empty file.
> >
> > Marek
> >
>
> Yes but now that I look at it seems the issue is that the error message was
> changed. My concern is that the test will have to be updated
> from the current every time the message changes like the current:
> error: expected primary-expression before ‘auto’
> 1 | struct g_class : decltype (auto) ... { };
>
> Is this something I should care about as seems emit_diagnostic and friends
> sometimes do this.
decltype(auto) is a C++14 feature so won't work with -std=c++11.
Marek
next prev parent reply other threads:[~2020-06-23 12:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-23 1:42 Nicholas Krause
2020-06-23 2:01 ` Marek Polacek
2020-06-23 3:11 ` Nicholas Krause
2020-06-23 12:27 ` Marek Polacek [this message]
2020-06-23 18:17 ` 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=20200623122742.GE31198@redhat.com \
--to=polacek@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jason@redhat.com \
--cc=xerofoify@gmail.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).