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++/108104] ICE in unify, at cp/pt.c:24333 with template partial specialization and pointer to memeber function and nullptr Date: Wed, 14 Dec 2022 18:39:29 +0000 [thread overview] Message-ID: <bug-108104-4-a0U7gogVaf@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108104-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108104 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |ice-on-valid-code Summary|ICE in unify, at |ICE in unify, at |cp/pt.c:24333 with template |cp/pt.c:24333 with template |partial specialization |partial specialization and | |pointer to memeber function | |and nullptr --- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Reduced testcase: ``` struct ss { void h(); }; template <int, void (ss::*m)()> struct Fred {}; template <int state> struct Fred<state, nullptr> {}; Fred<1, &ss::h> f1; ```
next prev parent reply other threads:[~2022-12-14 18:39 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-12-14 16:57 [Bug c++/108104] New: ICE in unify, at cp/pt.c:24333 with template partial specialization gawain.bolton at free dot fr 2022-12-14 18:39 ` pinskia at gcc dot gnu.org [this message] 2022-12-14 18:45 ` [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: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-a0U7gogVaf@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: linkBe 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).