public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/68608] [concepts] ICE with explicit class instantiation
Date: Sat, 24 Jul 2021 01:07:30 +0000 [thread overview]
Message-ID: <bug-68608-4-tBZ3p5H8wW@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-68608-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68608
--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Jonathan Wakely from comment #1)
> Still ICEs on current trunk with -std=c++17 -fconcepts, and also with
> -std=c++2a after modernising the code:
I can't get this to crash with r12-2133.
But the funny thing is clang crashes with a similar issue as what GCC had:
<source>:6:7: error: definition with same mangled name '_ZN1AIiE1fEv' as
another definition
int f() requires (!C<T>) { return 2; }
^
<source>:5:7: note: previous definition is here
int f() requires C<T> { return 1; }
^
next parent reply other threads:[~2021-07-24 1:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-68608-4@http.gcc.gnu.org/bugzilla/>
2021-07-24 1:07 ` pinskia at gcc dot gnu.org [this message]
2023-03-08 21:07 ` pinskia at gcc dot gnu.org
2023-03-08 21:08 ` pinskia at gcc dot gnu.org
2023-03-08 21:12 ` pinskia at gcc dot gnu.org
2023-03-15 13:25 ` 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-68608-4-tBZ3p5H8wW@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).