This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/28330] New: finds wrong template overload; peculiar diagnostic
- From: "igodard at pacbell dot net" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 10 Jul 2006 20:10:46 -0000
- Subject: [Bug c++/28330] New: finds wrong template overload; peculiar diagnostic
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
The error is an invocation of operator<<(ring<cacheRequest>&, loadRequest*).
ring<cacheRequest> defines operator<<(ring<cacheRequest>&, cacheRequest*), and
cacheRequest is a public base of the actual loadRequest argument. If the right
argument is explicitly cast to cacheRequest* (as shown in the line immediately
before the reported error) the correct operator<< is found and invoked.
However, when the argument is the derived class the compiler finds and invokes
an irrelevant definition of operator<< and then blows up inside it. The
definition it finds is declared by template wideUint<size_t> and in particular
by wideUint<1>: operator<<(wideUint<1>, const uint32_t&). Somehow it seems to
decide that it can turn a ring<cacheRequest>& into a wideUint<1>, and then
complains that it can't turn a cacheRequest* into a uint32_t (which is a
typedef
for unsigned int).
It seems to me that the compiler should be able to match the intended operator
by converting to the base class. However, even if it cannot then shouldn't it
just say "no match found for ..." rather than accepting the bogus match and
then
complaining about the conversion to uint32_t?
--
Summary: finds wrong template overload; peculiar diagnostic
Product: gcc
Version: 4.0.2
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: igodard at pacbell dot net
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28330