From: Jason Merrill <jason@redhat.com>
To: Simon Martin <simon@nasilyan.com>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Add testcase for PR c++/105229: ICE in lookup_template_class_1
Date: Fri, 24 May 2024 15:04:09 -0400 [thread overview]
Message-ID: <d74d3046-82bb-457b-88ae-ad39db87f1ec@redhat.com> (raw)
In-Reply-To: <0102018faa87d215-81fbec60-4d41-44dd-b2e1-77674c9e519c-000000@eu-west-1.amazonses.com>
On 5/24/24 08:16, Simon Martin wrote:
> The test case in PR c++/105229 has been fixed since 11.4 (via PR
> c++/106024) - the attached patch simply adds the case to the test suite.
>
> Successfully tested on x86_64-pc-linux-gnu. OK for trunk?
OK, thanks.
BTW, the patch was corrupted by your mail client wrapping long lines;
can you use git send-email instead in the future?
> Thanks! Simon
>
>
> PR c++/105229
>
> gcc/testsuite/ChangeLog:
>
> * g++.dg/parse/crash72.C: New test.
>
> ---
> gcc/testsuite/g++.dg/parse/crash72.C | 12 ++++++++++++
> 1 file changed, 12 insertions(+)
> create mode 100644 gcc/testsuite/g++.dg/parse/crash72.C
>
> diff --git a/gcc/testsuite/g++.dg/parse/crash72.C
> b/gcc/testsuite/g++.dg/parse/crash72.C
> new file mode 100644
> index 00000000000..df469e20f28
> --- /dev/null
> +++ b/gcc/testsuite/g++.dg/parse/crash72.C
> @@ -0,0 +1,12 @@
> +// PR c++/105229
> +// { dg-do compile { target c++20 } }
> +// { dg-additional-options "-Wno-missing-template-keyword" }
> +
> +template <typename> void bar ()
> +{
> + [] <int> {}.operator () <> (); // { dg-error "expected
> primary-expression" }
> +}
> +void foo ()
> +{
> + bar<int> ();
> +}
> --
> 2.44.0
>
prev parent reply other threads:[~2024-05-24 19:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3DE8D973-B0A4-4137-A161-F877CF8829E3@nasilyan.com>
2024-05-24 12:16 ` Simon Martin
2024-05-24 19:04 ` Jason Merrill [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=d74d3046-82bb-457b-88ae-ad39db87f1ec@redhat.com \
--to=jason@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=simon@nasilyan.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).