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++/97412] [10/11 Regression] [concepts] ICE with requires requires and parameter packs Date: Thu, 29 Oct 2020 18:03:44 +0000 [thread overview] Message-ID: <bug-97412-4-XdqsKDw0i0@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-97412-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97412 --- Comment #2 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Patrick Palka <ppalka@gcc.gnu.org>: https://gcc.gnu.org/g:5681668765e233735b4c5e6a305e73ae1f80a328 commit r11-4544-g5681668765e233735b4c5e6a305e73ae1f80a328 Author: Patrick Palka <ppalka@redhat.com> Date: Thu Oct 29 14:02:59 2020 -0400 c++: Tolerate empty initial args during normalization [PR97412] When normalizing the constraint-expression of a nested-requirement, we pass NULL_TREE as the initial template arguments for normalization, but tsubst_argument_pack is not prepared to handle a NULL_TREE args vector. This causes us to ICE when normalizing a variadic concept as part of a nested-requirement. This patch fixes the ICE by guarding the call to tsubst_template_args in normalize_concept_check appropriately. This will also enable us to simplify many of the normalization routines to just pass NULL_TREE (instead of a set of generic template arguments) as the initial template arguments. gcc/cp/ChangeLog: PR c++/97412 * constraint.cc (normalize_concept_check): Don't call tsubst_template_args when 'args' is NULL. gcc/testsuite/ChangeLog: PR c++/97412 * g++.dg/cpp2a/concepts-variadic2.C: New test.
next prev parent reply other threads:[~2020-10-29 18:03 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-10-13 22:19 [Bug c++/97412] New: " hello at josephloser dot com 2020-10-14 20:50 ` [Bug c++/97412] [10/11 Regression] " ppalka at gcc dot gnu.org 2020-10-29 18:03 ` cvs-commit at gcc dot gnu.org [this message] 2020-10-30 13:06 ` cvs-commit at gcc dot gnu.org 2020-10-30 13:07 ` 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-97412-4-XdqsKDw0i0@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).