public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/53152] In "no match for operatorXX" error message gives the wrong column info Date: Sat, 28 Apr 2012 07:26:00 -0000 [thread overview] Message-ID: <bug-53152-4-puqM2fUKeE@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-53152-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53152 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Keywords| |diagnostic Last reconfirmed| |2012-04-28 Ever Confirmed|0 |1 Summary|In "no match for |In "no match for |operatorXX" error message, |operatorXX" error message |mention the types of the |gives the wrong column info |arguments | Severity|normal |enhancement --- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> 2012-04-28 07:25:33 UTC --- The trunk already does: t.cc: In function ‘int main()’: t.cc:11:21: error: no match for ‘operator==’ (operand types are ‘T’ and ‘T’) a.foo() == b.foo(); ^ Tough we don't point at == but the call to b.foo() which seems wrong. So confirmed about the wrong column info.
next prev parent reply other threads:[~2012-04-28 7:26 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-04-28 6:38 [Bug c++/53152] New: In "no match for operatorXX" error message, mention the types of the arguments zeratul976 at hotmail dot com 2012-04-28 7:26 ` pinskia at gcc dot gnu.org [this message] 2012-04-28 19:55 ` [Bug c++/53152] In "no match for operatorXX" error message gives the wrong column info redi at gcc dot gnu.org 2012-05-04 10:57 ` paolo.carlini at oracle dot com 2012-05-04 11:27 ` manu at gcc dot gnu.org 2012-05-04 12:31 ` paolo.carlini at oracle dot com 2012-05-04 12:32 ` paolo.carlini at oracle dot com 2012-05-06 15:07 ` paolo at gcc dot gnu.org 2012-05-06 15:40 ` paolo.carlini at oracle 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-53152-4-puqM2fUKeE@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).