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++/99844] [9/10/11 Regression] ICE: unexpected expression 'B' of kind template_parm_index Date: Thu, 08 Apr 2021 11:46:01 +0000 [thread overview] Message-ID: <bug-99844-4-M7ofYIJ0ib@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99844-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99844 --- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Marek Polacek <mpolacek@gcc.gnu.org>: https://gcc.gnu.org/g:2cd5333d16419f596d07a830bb3f1c40fa8a7b5c commit r11-8041-g2cd5333d16419f596d07a830bb3f1c40fa8a7b5c Author: Marek Polacek <polacek@redhat.com> Date: Wed Apr 7 16:44:24 2021 -0400 c++: Fix ICE with unexpanded parameter pack [PR99844] In explicit17.C, we weren't detecting an unexpanded parameter pack in explicit(bool), so we crashed on a TEMPLATE_PARM_INDEX in constexpr. I noticed the same is true for noexcept(), but only since my patch to implement delayed parsing of noexcept. Previously, we would detect the unexpanded pack in push_template_decl but now the noexcept expression has not yet been parsed, so we need to do it a bit later. gcc/cp/ChangeLog: PR c++/99844 * decl.c (build_explicit_specifier): Call check_for_bare_parameter_packs. * except.c (build_noexcept_spec): Likewise. gcc/testsuite/ChangeLog: PR c++/99844 * g++.dg/cpp2a/explicit16.C: Use c++20. * g++.dg/cpp0x/noexcept66.C: New test. * g++.dg/cpp2a/explicit17.C: New test.
next prev parent reply other threads:[~2021-04-08 11:46 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-31 2:58 [Bug c++/99844] New: " hewillk at gmail dot com 2021-03-31 16:07 ` [Bug c++/99844] [9/10/11 Regression] " mpolacek at gcc dot gnu.org 2021-03-31 16:07 ` mpolacek at gcc dot gnu.org 2021-04-07 15:15 ` mpolacek at gcc dot gnu.org 2021-04-08 11:46 ` cvs-commit at gcc dot gnu.org [this message] 2021-04-08 11:46 ` [Bug c++/99844] [9/10 " mpolacek 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-99844-4-M7ofYIJ0ib@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).