public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/103631] [11/12 Regression] ICE in C++20 class NTTP + concept since r12-100-gbcd77b7b9f35bd5b
Date: Thu, 20 Jan 2022 18:12:41 +0000	[thread overview]
Message-ID: <bug-103631-4-LkWMjCZelY@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103631-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103631

--- Comment #2 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Patrick Palka <ppalka@gcc.gnu.org>:

https://gcc.gnu.org/g:2f34d7ef3d026cf7109b6e6bb2eca14c840e7c71

commit r12-6777-g2f34d7ef3d026cf7109b6e6bb2eca14c840e7c71
Author: Patrick Palka <ppalka@redhat.com>
Date:   Thu Jan 20 13:12:16 2022 -0500

    c++: add testcase for recently fixed PR [PR103631]

    We accept this testcase after r12-6773.

            PR c++/103631

    gcc/testsuite/ChangeLog:

            * g++.dg/cpp2a/nontype-class51.C: New test.

  parent reply	other threads:[~2022-01-20 18:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-09 13:51 [Bug c++/103631] New: Internal compiler error in C++20 class NTTP + concept winmikedows at hotmail dot com
2021-12-09 13:56 ` [Bug c++/103631] [12 Regression] ICE in C++20 class NTTP + concept since r12-100-gbcd77b7b9f35bd5b marxin at gcc dot gnu.org
2021-12-09 14:01 ` [Bug c++/103631] [11/12 " pinskia at gcc dot gnu.org
2022-01-04  9:05 ` rguenth at gcc dot gnu.org
2022-01-20 18:12 ` cvs-commit at gcc dot gnu.org [this message]
2022-01-20 18:15 ` [Bug c++/103631] [11 " ppalka at gcc dot gnu.org
2022-01-20 18:16 ` ppalka at gcc dot gnu.org
2022-04-21  7:50 ` rguenth at gcc dot gnu.org
2023-05-21 15:13 ` ppalka at gcc dot gnu.org

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=bug-103631-4-LkWMjCZelY@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /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).