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++/99968] ICE on remove_const_t<incomplete enum type> in requires-expression
Date: Thu, 01 Sep 2022 14:48:45 +0000 [thread overview]
Message-ID: <bug-99968-4-iGWbDqk4KK@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
--- Comment #10 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jonathan Wakely <redi@gcc.gnu.org>:
https://gcc.gnu.org/g:37ff51a98583e63fb9afe83cf9f4351760149028
commit r13-2344-g37ff51a98583e63fb9afe83cf9f4351760149028
Author: Jonathan Wakely <jwakely@redhat.com>
Date: Thu Sep 1 11:52:52 2022 +0100
libstdc++: Remove FIXME for ICE with remove_cvref_t in requires-expression
PR c++/99968 is fixed since GCC 12.1 so we can remove the workaround.
libstdc++-v3/ChangeLog:
* include/std/type_traits (is_scoped_enum): Remove workaround.
prev parent reply other threads:[~2022-09-01 14:48 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 ` [Bug c++/99968] " redi at gcc dot gnu.org
2021-04-08 11:09 ` 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 [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=bug-99968-4-iGWbDqk4KK@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).