public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/99968] ICE on remove_const_t<incomplete enum type> in requires-expression
Date: Thu, 08 Apr 2021 11:06:55 +0000 [thread overview]
Message-ID: <bug-99968-4-BloyeBnkIR@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99968-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99968
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|[10/11 Regression] ICE on |ICE on
|remove_const_t<incomplete |remove_const_t<incomplete
|enum type> in |enum type> in
|requires-expression |requires-expression
Known to work|10.2.1 |
Blocks| |67491
Known to fail|11.0 |
--- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> ---
I get an ICE with gcc 8 and 9 and -std=gnu++2a -fconcepts -g -fchecking=1 so
not a regression.
Referenced Bugs:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67491
[Bug 67491] [meta-bug] concepts issues
next prev parent reply other threads:[~2021-04-08 11:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-08 10:37 [Bug c++/99968] New: [11 Regression] " redi at gcc dot gnu.org
2021-04-08 10:38 ` [Bug c++/99968] " redi at gcc dot gnu.org
2021-04-08 10:58 ` redi at gcc dot gnu.org
2021-04-08 11:00 ` [Bug c++/99968] [10/11 " mpolacek at gcc dot gnu.org
2021-04-08 11:06 ` redi at gcc dot gnu.org [this message]
2021-04-08 11:09 ` [Bug c++/99968] " cvs-commit at gcc dot gnu.org
2021-04-08 11:11 ` mpolacek at gcc dot gnu.org
2021-04-09 13:59 ` ppalka at gcc dot gnu.org
2021-04-09 14:01 ` ppalka at gcc dot gnu.org
2021-12-12 6:39 ` pinskia at gcc dot gnu.org
2021-12-28 4:52 ` jason at gcc dot gnu.org
2021-12-28 17:46 ` cvs-commit at gcc dot gnu.org
2022-09-01 10:50 ` redi at gcc dot gnu.org
2022-09-01 14:48 ` cvs-commit 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-99968-4-BloyeBnkIR@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).