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++/104291] [12 Regression] gcc accepts template argument involves template parameter(s) Date: Mon, 31 Jan 2022 19:15:36 +0000 [thread overview] Message-ID: <bug-104291-4-jYMMPwPowC@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104291-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104291 --- 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:0eb06ee9a40a09d2f492461289d69aa39f757e66 commit r12-6949-g0eb06ee9a40a09d2f492461289d69aa39f757e66 Author: Patrick Palka <ppalka@redhat.com> Date: Mon Jan 31 14:15:01 2022 -0500 c++: CONSTRUCTORs are non-deduced contexts [PR104291] PR c++/104291 gcc/cp/ChangeLog: * pt.cc (for_each_template_parm_r) <case CONSTRUCTOR>: Clear walk_subtrees if !include_nondeduced_p. Simplify given that cp_walk_subtrees already walks TYPE_PTRMEMFUNC_FN_TYPE_RAW. gcc/testsuite/ChangeLog: * g++.dg/template/partial20.C: New test.
next prev parent reply other threads:[~2022-01-31 19:15 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-30 17:20 [Bug c++/104291] New: " hewillk at gmail dot com 2022-01-30 21:27 ` [Bug c++/104291] [12 Regression] " pinskia at gcc dot gnu.org 2022-01-31 8:22 ` rguenth at gcc dot gnu.org 2022-01-31 9:04 ` redi at gcc dot gnu.org 2022-01-31 16:44 ` ppalka at gcc dot gnu.org 2022-01-31 19:15 ` cvs-commit at gcc dot gnu.org [this message] 2022-01-31 19:15 ` 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-104291-4-jYMMPwPowC@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).