public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/66968] Incorrect template argument shown in diagnostic Date: Sat, 25 Jul 2015 22:10:00 -0000 [thread overview] Message-ID: <bug-66968-4-SIzCUPO1Mu@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-66968-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66968 --- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> --- Yes maybe a dup of PR99 but it looks like all the examples in that bug involve an overload and using the parameter names from the wrong overload. Here it uses the parameter from a function that never participates in overload resolution.
next prev parent reply other threads:[~2015-07-25 22:10 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-07-22 13:37 [Bug c++/66968] New: " redi at gcc dot gnu.org 2015-07-25 18:44 ` [Bug c++/66968] " manu at gcc dot gnu.org 2015-07-25 22:10 ` redi at gcc dot gnu.org [this message] 2021-07-16 20:24 ` redi at gcc dot gnu.org 2021-07-16 22:05 ` cvs-commit at gcc dot gnu.org 2021-07-16 22:11 ` redi at gcc dot gnu.org 2022-07-13 12:34 ` redi at gcc dot gnu.org 2023-02-06 10:18 ` vanyacpp at gmail dot com 2023-02-06 10:20 ` vanyacpp at gmail dot com
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-66968-4-SIzCUPO1Mu@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).