public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jfhart085 at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/99558] New: wrong argument types reported for "no matching function" error message if ctor argument is a variable Date: Fri, 12 Mar 2021 08:30:21 +0000 [thread overview] Message-ID: <bug-99558-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99558 Bug ID: 99558 Summary: wrong argument types reported for "no matching function" error message if ctor argument is a variable Product: gcc Version: 10.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: jfhart085 at gmail dot com Target Milestone: --- Created attachment 50371 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=50371&action=edit utl2.cc - demonstrates using deliberate error message from compile Wrong argument types are reported for "no matching function" error message for a ctor if a ctor argument is a variable. The argument is reported as being a reference when it is not. An error message is deliberately generated to demonstrate the problem as follows: wrong argument type: variable used as argument, first argument is shown as "int &" but is actually "int" : $ 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" $ 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)" from gcc -v : Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-pc-linux-gnu/10.2.0/lto-wrapper Target: x86_64-pc-linux-gnu Configured with: /home/jhart/temp1/gcc-10.2.0/configure --prefix=/usr --disable-multilib --with-system-zlib --enable-languages=c,c++,fortran Thread model: posix Supported LTO compression algorithms: zlib gcc version 10.2.0 (GCC)
next reply other threads:[~2021-03-12 8:30 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-12 8:30 jfhart085 at gmail dot com [this message] 2021-03-12 9:30 ` [Bug c++/99558] " redi at gcc dot gnu.org 2021-03-13 7:15 ` 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@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).