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++/99558] wrong argument types reported for "no matching function" error message if ctor argument is a variable Date: Fri, 12 Mar 2021 09:30:39 +0000 [thread overview] Message-ID: <bug-99558-4-Fmn6AmTvwX@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99558-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99558 Jonathan Wakely <redi at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED --- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> --- (In reply to J. Hart from comment #0) > $ g++ -c -o utl2.o utl2.cc > utl2.cc: In function "int main()": > utl2.cc:13:5: error: no matching function for call to "cls4::cls4(int&, int)" > > correct argument type: constant used as argument, first argument is > correctly shown as "int" GCC is correct. When you use a variable you are passing an lvalue of type int, which is what int& means. When you pass a constant it is an rvalue, i.e. int. > > $ g++ -D DBG1 -c -o utl2.o utl2.cc > utl2.cc: In function "int main()": > utl2.cc:13:5: error: no matching function for call to "cls4::cls4(int, int)" Because you're passing two rvalues.
next prev parent reply other threads:[~2021-03-12 9:30 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-12 8:30 [Bug c++/99558] New: " jfhart085 at gmail dot com 2021-03-12 9:30 ` redi at gcc dot gnu.org [this message] 2021-03-13 7:15 ` [Bug c++/99558] " jfhart085 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-99558-4-Fmn6AmTvwX@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).