From: Jason Merrill <jason@redhat.com>
To: gcc-patches@gcc.gnu.org
Subject: [pushed] c++: tweak resolve_args change
Date: Fri, 1 Jul 2022 10:55:22 -0400 [thread overview]
Message-ID: <20220701145522.908108-1-jason@redhat.com> (raw)
In-Reply-To: <CAMOnLZaJqULrkgXiYF3Fyxk863iNebbK86bNRfdbBa1BNtYQdg@mail.gmail.com>
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.
---
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 f1dd8377628..fc98552fda2 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;
base-commit: 288c6cce0277e03e08b324283b6a015a70066bb7
--
2.27.0
prev parent reply other threads:[~2022-07-01 14:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-01 19:20 [pushed] c++: auto function as function argument [PR105779] Jason Merrill
2022-06-30 21:06 ` Patrick Palka
2022-07-01 14:55 ` Jason Merrill [this message]
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=20220701145522.908108-1-jason@redhat.com \
--to=jason@redhat.com \
--cc=gcc-patches@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: link
Be 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).