public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "nicoara at roguewave dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/32440] New: Lookup fails to find later function overload if template has been defined earlier Date: Wed, 20 Jun 2007 21:13:00 -0000 [thread overview] Message-ID: <bug-32440-10428@http.gcc.gnu.org/bugzilla/> (raw) The following: $ cat t.cpp template< typename T > int baz (T const*) { return 0; } template <class T> void bar(T* ptr) { baz (*ptr); } int baz (int const&) { return 0; } void foo () { int const n = 0; bar (&n); } fails to compile with gcc 4.2.0: $ g++ -v; g++ -c t.cpp Using built-in specs. Target: i686-pc-linux-gnu Configured with: ../gcc-4.2.0/configure --prefix=/opt/compilers/gcc-4.2.0 --enable-threads --enable-shared --enable-languages=c,c++ Thread model: posix gcc version 4.2.0 t.cpp: In function 'void bar(T*) [with T = const int]': t.cpp:25: instantiated from here t.cpp:12: error: no matching function for call to 'baz(const int&)' Moving "int baz (int const&)" to top, or removing top function template avoids the error. It is possible that this issue may be somehow related to the issue reported in the bug report 31816. Thanks, Liviu -- Summary: Lookup fails to find later function overload if template has been defined earlier Product: gcc Version: 4.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: nicoara at roguewave dot com GCC build triplet: i686-pc-linux-gnu GCC host triplet: i686-pc-linux-gnu GCC target triplet: i686-pc-linux-gnu http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32440
next reply other threads:[~2007-06-20 21:13 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-06-20 21:13 nicoara at roguewave dot com [this message] 2007-06-20 21:17 ` [Bug c++/32440] " pinskia at gcc dot gnu dot org
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-32440-10428@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).