public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Jason Merrill <jason@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r12-8534] c++: tweak resolve_args change Date: Fri, 1 Jul 2022 14:55:45 +0000 (GMT) [thread overview] Message-ID: <20220701145545.95A16385C40D@sourceware.org> (raw) https://gcc.gnu.org/g:d9130880f77c7f9ffd5deaabda605bc151521be5 commit r12-8534-gd9130880f77c7f9ffd5deaabda605bc151521be5 Author: Jason Merrill <jason@redhat.com> Date: Fri Jul 1 00:37:10 2022 -0400 c++: tweak resolve_args change I don't know why I used tf_error instead of complain here. PR c++/105779 gcc/cp/ChangeLog: * call.cc (resolve_args): Use complain. Diff: --- gcc/cp/call.cc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/gcc/cp/call.cc b/gcc/cp/call.cc index 45253b1babf..726770d4db8 100644 --- a/gcc/cp/call.cc +++ b/gcc/cp/call.cc @@ -4675,7 +4675,7 @@ resolve_args (vec<tree, va_gc> *args, tsubst_flags_t complain) /* Force auto deduction now. Omit tf_warning to avoid redundant deprecated warning on deprecated-14.C. */ - if (!mark_single_function (arg, tf_error)) + if (!mark_single_function (arg, complain & ~tf_warning)) return NULL; } return args;
reply other threads:[~2022-07-01 14:55 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220701145545.95A16385C40D@sourceware.org \ --to=jason@gcc.gnu.org \ --cc=gcc-cvs@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).