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++/99909] The value of 'std::is_integral_v<auto>' is not usable in a constant expression Date: Tue, 28 Sep 2021 21:26:35 +0000 [thread overview] Message-ID: <bug-99909-4-Z8dT38mBwc@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99909-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99909 --- Comment #3 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:daa762f01d8cf932484b7df122a5e872439bc92c commit r12-3950-gdaa762f01d8cf932484b7df122a5e872439bc92c Author: Patrick Palka <ppalka@redhat.com> Date: Tue Sep 28 17:26:20 2021 -0400 c++: ttp matching with constrained auto parm [PR99909] Here, when unifying TT with S, processing_template_decl is unset, and this foils the dependence checks in do_auto_deduction for avoiding checking constraints on an auto when the initializer is dependent. This patch fixes this by making sure processing_template_decl is set around the call to unify from coerce_template_template_parms; this seems sensible because we're unifying one set of template parameters with another, so we're dealing with templated trees throughout. PR c++/99909 gcc/cp/ChangeLog: * pt.c (coerce_template_template_parms): Keep processing_template_decl set around the call to unify as well. gcc/testsuite/ChangeLog: * g++.dg/cpp2a/concepts-ttp3.C: New test.
next prev parent reply other threads:[~2021-09-28 21:26 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-04 18:30 [Bug c++/99909] New: " hewillk at gmail dot com 2021-04-06 18:59 ` [Bug c++/99909] " jason at gcc dot gnu.org 2021-06-29 14:23 ` giecrilj at stegny dot 2a.pl 2021-06-29 15:17 ` hewillk at gmail dot com 2021-09-27 19:38 ` ppalka at gcc dot gnu.org 2021-09-28 21:26 ` cvs-commit at gcc dot gnu.org [this message] 2021-09-28 21:27 ` 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-99909-4-Z8dT38mBwc@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).