public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gawain.bolton at free dot fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/108104] New: ICE in unify, at cp/pt.c:24333 with template partial specialization
Date: Wed, 14 Dec 2022 16:57:53 +0000 [thread overview]
Message-ID: <bug-108104-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108104
Bug ID: 108104
Summary: ICE in unify, at cp/pt.c:24333 with template partial
specialization
Product: gcc
Version: 12.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: gawain.bolton at free dot fr
Target Milestone: ---
Created attachment 54091
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54091&action=edit
ICE with template partial specialization - No issue if WITH_STATE is 0 i.e. if
the State parameter is absent
Please see attached file which causes an internal compiler error.
Note that there is no issue if the "State" template argument is removed as can
be shown if you set WITH_STATE to 0.
No issue found with clang >= v13.0
ICE found with all versions of GCC I tried (from GCC v4.9.4 to GCC v12.2)
next reply other threads:[~2022-12-14 16:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-14 16:57 gawain.bolton at free dot fr [this message]
2022-12-14 18:39 ` [Bug c++/108104] ICE in unify, at cp/pt.c:24333 with template partial specialization and pointer to memeber function and nullptr pinskia at gcc dot gnu.org
2022-12-14 18:45 ` pinskia at gcc dot gnu.org
2022-12-14 18:50 ` pinskia at gcc dot gnu.org
2022-12-14 23:50 ` ppalka at gcc dot gnu.org
2022-12-15 20:39 ` cvs-commit at gcc dot gnu.org
2022-12-15 20:40 ` ppalka at gcc dot gnu.org
2022-12-19 16:54 ` cvs-commit at gcc dot gnu.org
2022-12-19 16:56 ` 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-108104-4@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).