public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "slyfox at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/114933] [15 Regression] mcfgthread-1.6.1 typecheck failure: error: explicit specializations are not permitted here
Date: Fri, 03 May 2024 09:05:05 +0000 [thread overview]
Message-ID: <bug-114933-4-7CeFbayH2P@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114933-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114933
Sergei Trofimovich <slyfox at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |lh_mouse at 126 dot com
Version|14.0 |15.0
--- Comment #1 from Sergei Trofimovich <slyfox at gcc dot gnu.org> ---
The original trigger code resides at
https://github.com/lhmouse/mcfgthread/blob/9f3c73a3651bf0cf94eef9681c5ba191d66b198b/mcfgthread/fwd.h#L131
/cc LIU Hao in case it's a new c++20 restriction and mcfgthread would need to
adapt.
next prev parent reply other threads:[~2024-05-03 9:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-03 8:54 [Bug c++/114933] New: " slyfox at gcc dot gnu.org
2024-05-03 9:05 ` slyfox at gcc dot gnu.org [this message]
2024-05-03 9:07 ` [Bug c++/114933] " pinskia at gcc dot gnu.org
2024-05-03 9:09 ` pinskia at gcc dot gnu.org
2024-05-03 9:10 ` pinskia at gcc dot gnu.org
2024-05-03 9:12 ` pinskia at gcc dot gnu.org
2024-05-03 9:14 ` lh_mouse at 126 dot com
2024-05-03 9:17 ` pinskia at gcc dot gnu.org
2024-05-03 9:50 ` lh_mouse at 126 dot com
2024-05-03 20:49 ` slyfox 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-114933-4-7CeFbayH2P@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).