public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/102547] [11 Regression] g++ 11. ICE with NTTPs and partial specialization Date: Wed, 06 Oct 2021 14:15:57 +0000 [thread overview] Message-ID: <bug-102547-4-xgnW7gvsP2@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-102547-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102547 --- Comment #8 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-11 branch has been updated by Patrick Palka <ppalka@gcc.gnu.org>: https://gcc.gnu.org/g:1aef951f1aa0b50a8da12f6fe6e80f3fdaa4d98e commit r11-9086-g1aef951f1aa0b50a8da12f6fe6e80f3fdaa4d98e Author: Patrick Palka <ppalka@redhat.com> Date: Tue Oct 5 15:35:21 2021 -0400 c++: unifying equal NONTYPE_ARGUMENT_PACKs [PR102547] Here during partial ordering of the two partial specializations we end up in unify with parm=arg=NONTYPE_ARGUMENT_PACK<V0, V1>, and crash shortly thereafter because uses_template_parms(parms) calls potential_const_expr which doesn't handle NONTYPE_ARGUMENT_PACK. This patch fixes this by extending potential_constant_expression to handle NONTYPE_ARGUMENT_PACK appropriately. PR c++/102547 gcc/cp/ChangeLog: * constexpr.c (potential_constant_expression_1): Handle NONTYPE_ARGUMENT_PACK. gcc/testsuite/ChangeLog: * g++.dg/cpp0x/variadic-partial2.C: New test. * g++.dg/cpp0x/variadic-partial2a.C: New test. (cherry picked from commit d4c470c376b4cb82c9a0b7e8a4b88c44d5e4289d)
next prev parent reply other threads:[~2021-10-06 14:15 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-09-30 16:09 [Bug c++/102547] New: " bob.steagall.cpp at gmail dot com 2021-09-30 19:16 ` [Bug c++/102547] " ppalka at gcc dot gnu.org 2021-09-30 19:39 ` ppalka at gcc dot gnu.org 2021-09-30 19:41 ` [Bug c++/102547] [11/12 Regression] " ppalka at gcc dot gnu.org 2021-09-30 19:58 ` ppalka at gcc dot gnu.org 2021-09-30 21:35 ` bob.steagall.cpp at gmail dot com 2021-10-01 6:31 ` rguenth at gcc dot gnu.org 2021-10-05 19:36 ` cvs-commit at gcc dot gnu.org 2021-10-05 19:43 ` ppalka at gcc dot gnu.org 2021-10-05 19:44 ` [Bug c++/102547] [11 " ppalka at gcc dot gnu.org 2021-10-06 14:15 ` cvs-commit at gcc dot gnu.org [this message] 2021-10-06 14:21 ` ppalka at gcc dot gnu.org 2021-10-29 19:43 ` 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-102547-4-xgnW7gvsP2@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).