public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Simon Martin" <simon@nasilyan.com>
To: "Jason Merrill" <jason@redhat.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
	"Patrick Palka" <ppalka@redhat.com>
Subject: Re: [PATCH] PR c++/103338 - Add testcase for issue fixed by recent commit
Date: Tue, 4 Jun 2024 16:42:59 +0000	[thread overview]
Message-ID: <0102018fe421ec0f-3b197bc4-7668-4ace-a874-e2fc7de70fbd-000000@eu-west-1.amazonses.com> (raw)
In-Reply-To: <8bb3baae-bdad-4c27-8373-9511c5f35c20@redhat.com>

Hi Jason,

On 4 Jun 2024, at 18:12, Jason Merrill wrote:

> On 6/4/24 11:54, Simon Martin wrote:
>> The case in that PR used to ICE until commit f04dc89.
>
> Interesting, I don't remember expecting that patch to change behavior 
> at all.
This is the patch that git bisect identified. I have to admit that I did 
not look further.

> BTW, it looks like your recent commits and emails have had 
> non-conventional subject lines; see 
> https://gcc.gnu.org/contribute.html#patches for more guidance.
>
Thanks for the pointer and apologies for not providing great subject 
lines; I’ll fix this moving forward (starting with that patch).

> For instance, the subject for this patch could be
>
> c++: add testcase for PR103338
>
> OK with that adjustment.
Thanks again.
>
>> This patch simply adds
>> the case to the testsuite.
>>
>> Successfully tested on x86_64-pc-linux-gnu.
>>
>> 	PR c++/1033388
>>
>> gcc/testsuite/ChangeLog:
>>
>> 	* g++.dg/parse/crash73.C: New test.
>>
>> ---
>>   gcc/testsuite/g++.dg/parse/crash73.C | 19 +++++++++++++++++++
>>   1 file changed, 19 insertions(+)
>>   create mode 100644 gcc/testsuite/g++.dg/parse/crash73.C
>>
>> diff --git a/gcc/testsuite/g++.dg/parse/crash73.C 
>> b/gcc/testsuite/g++.dg/parse/crash73.C
>> new file mode 100644
>> index 00000000000..5923b98b719
>> --- /dev/null
>> +++ b/gcc/testsuite/g++.dg/parse/crash73.C
>> @@ -0,0 +1,19 @@
>> +// PR c++/1033388
>> +// { dg-do compile { target c++11 } }
>> +
>> +template<class...>
>> +struct zip_view {
>> +  struct Iterator;
>> +};
>> +
>> +template<class...>
>> +struct zip_transform_view;
>> +
>> +template<class... Views>
>> +struct zip_view<Views...>::Iterator { // { dg-error "no class 
>> template" }
>> +  template<class... Uiews>
>> +  template<bool>
>> +  friend class zip_transform_view<Uiews...>::Iterator;
>> +};
>> +
>> +zip_view<>::Iterator iter;


      parent reply	other threads:[~2024-06-04 16:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240604155436.1255-1-simon@nasilyan.com>
2024-06-04 15:54 ` Simon Martin
2024-06-04 16:12   ` Jason Merrill
     [not found]     ` <C4F9A382-D952-4703-AAFC-44D1E7980BD2@nasilyan.com>
2024-06-04 16:42       ` Simon Martin [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=0102018fe421ec0f-3b197bc4-7668-4ace-a874-e2fc7de70fbd-000000@eu-west-1.amazonses.com \
    --to=simon@nasilyan.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jason@redhat.com \
    --cc=ppalka@redhat.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).