public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ppalka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/99365] [11 Regression] ICE on partial specialization with constrained placeholder NTTP
Date: Wed, 03 Mar 2021 22:55:56 +0000 [thread overview]
Message-ID: <bug-99365-4-JT0PjuDoxi@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99365-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99365
Patrick Palka <ppalka at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |rejects-valid
--- Comment #3 from Patrick Palka <ppalka at gcc dot gnu.org> ---
Another variant from PR99366 which we reject rather than ICE on:
(In reply to Johel Ernesto Guerrero Peña from comment #0)
> See https://godbolt.org/z/ETjYfP.
> ```C++
> template<class>concept C=true;
> template<class,C auto>struct A{};
> template<class T,C auto V>requires true struct A<T,V>{};
> ```
> I think CE recompiles GCC trunk daily, and this was working yesterday.
> Must be related to Bug 99365.
next prev parent reply other threads:[~2021-03-03 22:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-03 17:48 [Bug c++/99365] New: " johelegp at gmail dot com
2021-03-03 19:53 ` [Bug c++/99365] [11 Regression] " mpolacek at gcc dot gnu.org
2021-03-03 21:17 ` ppalka at gcc dot gnu.org
2021-03-03 22:54 ` ppalka at gcc dot gnu.org
2021-03-03 22:55 ` ppalka at gcc dot gnu.org [this message]
2021-03-06 5:08 ` cvs-commit at gcc dot gnu.org
2021-03-06 15:35 ` ppalka at gcc dot gnu.org
2021-03-07 17:47 ` johelegp at gmail dot com
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-99365-4-JT0PjuDoxi@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).