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++/108468] [11 Regression] ICE in most_specialized_partial_spec/builtin_guide_p in C++20 mode Date: Sat, 22 Apr 2023 00:22:37 +0000 [thread overview] Message-ID: <bug-108468-4-j2pAXIxdVD@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108468-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108468 --- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-11 branch has been updated by Jason Merrill <jason@gcc.gnu.org>: https://gcc.gnu.org/g:469881efc4ad365dce3db26dab7d33f95d36f92f commit r11-10640-g469881efc4ad365dce3db26dab7d33f95d36f92f Author: Jason Merrill <jason@redhat.com> Date: Tue Mar 14 16:32:31 2023 -0400 c++: variable tmpl partial specialization [PR108468] Generally we expect TPARMS_PRIMARY_TEMPLATE to be set, but sometimes it isn't for partial instantiations. This ought to be improved, but it's trivial to work around it in this case. PR c++/108468 gcc/cp/ChangeLog: * pt.c (unify_pack_expansion): Check that TPARMS_PRIMARY_TEMPLATE is non-null. gcc/testsuite/ChangeLog: * g++.dg/cpp1y/var-templ78.C: New test.
next prev parent reply other threads:[~2023-04-22 0:22 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-01-19 17:54 [Bug c++/108468] New: " ed at catmur dot uk 2023-01-19 17:58 ` [Bug c++/108468] [11/12/13 Regression] " mpolacek at gcc dot gnu.org 2023-03-14 20:30 ` jason at gcc dot gnu.org 2023-03-14 22:10 ` cvs-commit at gcc dot gnu.org 2023-03-14 22:11 ` [Bug c++/108468] [11/12 " jason at gcc dot gnu.org 2023-04-18 20:45 ` cvs-commit at gcc dot gnu.org 2023-04-22 0:22 ` cvs-commit at gcc dot gnu.org [this message] 2023-05-29 10:07 ` [Bug c++/108468] [11 " jakub at gcc dot gnu.org 2023-08-11 19:37 ` jason 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-108468-4-j2pAXIxdVD@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).