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++/108960] clear tf_partial et al in instantiate_template Date: Tue, 25 Jul 2023 20:31:44 +0000 [thread overview] Message-ID: <bug-108960-4-oxkGZl8EA3@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108960-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108960 --- Comment #2 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The trunk branch has been updated by Marek Polacek <mpolacek@gcc.gnu.org>: https://gcc.gnu.org/g:39004608e79b68fe7615a026ce58dea646dba20e commit r14-2765-g39004608e79b68fe7615a026ce58dea646dba20e Author: Marek Polacek <polacek@redhat.com> Date: Tue Jul 25 14:36:47 2023 -0400 c++: clear tf_partial et al in instantiate_template [PR108960] In <https://gcc.gnu.org/pipermail/gcc-patches/2023-February/612929.html> we concluded that we might clear all flags except tf_warning_or_error when performing instantiate_template. PR c++/108960 gcc/cp/ChangeLog: * pt.cc (lookup_and_finish_template_variable): Don't clear tf_partial here. (instantiate_template): Reset all complain flags except tf_warning_or_error.
next prev parent reply other threads:[~2023-07-25 20:31 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-02-27 23:24 [Bug c++/108960] New: clear tf_partial " mpolacek at gcc dot gnu.org 2023-02-27 23:25 ` [Bug c++/108960] " mpolacek at gcc dot gnu.org 2023-07-25 20:31 ` cvs-commit at gcc dot gnu.org [this message] 2023-07-25 20:32 ` [Bug c++/108960] clear tf_partial et al " 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-108960-4-oxkGZl8EA3@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).