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++/96396] initializer_list in `-fconcepts -std=c++11` reports internal compiler error
Date: Tue, 26 Mar 2024 08:15:10 +0000 [thread overview]
Message-ID: <bug-96396-4-Nb6v51nSJi@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-96396-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96396
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords|needs-bisection |
--- Comment #4 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Fixed by r13-3639
c++: change -fconcepts to mean C++20 concepts
It was always weird that -fconcepts in C++17 mode meant the same thing as
-fconcepts-ts in C++20 mode; this patch harmonizes the flags so that for TS
concepts you always need to write -fconcepts-ts.
In the unlikely event anyone is still using -fconcepts in C++17 mode, they
can either fix their code to work with C++20 concepts or adjust the compiler
flag.
It still ICEs with -fconcepts-ts -std=c++11
But I'm not surprised that combination doesn't work, the Concepts TS is
supposed to be used with C++17.
prev parent reply other threads:[~2024-03-26 8:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-31 2:32 [Bug c++/96396] New: " gcc at mailinator dot com
2020-08-03 20:02 ` [Bug c++/96396] " mpolacek at gcc dot gnu.org
2021-07-22 22:38 ` pinskia at gcc dot gnu.org
2024-03-26 7:44 ` pinskia at gcc dot gnu.org
2024-03-26 8:15 ` redi 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-96396-4-Nb6v51nSJi@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).