This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/22363] Problems with friend function injection and destructor
- From: "bangerth at dealii dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 8 Jul 2005 14:58:57 -0000
- Subject: [Bug c++/22363] Problems with friend function injection and destructor
- References: <20050708110943.22363.cxl@ntllib.org>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Additional Comments From bangerth at dealii dot org 2005-07-08 14:58 -------
I don't quite know what to say, whether this is a bug or not. Take
this reduced snippet:
---------------------------
template <class T> struct S {
friend void foo(T *);
};
template <class T> void bar() { foo((T*)0); }
template <class T>
struct X : S< X<T> >
{
X() { bar<T>(); }
};
X< X<int> > test;
----------------------------
icc compiles this, but gcc doesn't, with this error message:
g/x> /home/bangerth/bin/gcc-4.1*/bin/c++ -c x.cc
x.cc:2: warning: friend declaration ‘void foo(T*)’ declares a non-template
function
x.cc:2: warning: (if this is not what you intended, make sure the function
template has already been declared and add <> after the function name here)
-Wno-non-template-friend disables this warning
x.cc: In function ‘void bar() [with T = X<int>]’:
x.cc:10: instantiated from ‘X<T>::X() [with T = X<int>]’
x.cc:13: instantiated from here
x.cc:5: error: cannot convert ‘X<int>*’ to ‘X<X<int> >*’ for argument ‘1’ to
‘void foo(X<X<int> >*)’
What is happening is that in the definition of 'test', we instantiate
X<X<int> >, which through its derivation from S<X<X<int>>> makes sure
that there is a function foo<X<X<int>>> (that this function is available
is visible from the error message). However, in the destructor of
X<X<int>>, we call bar<X<int>> which in turn wants to call foo<X<int>>,
which doesn't exist.
I believe that the reason why icc can compile this is that in the definition
of 'test', the compiler does not only instantiate X<X<int>>, but also X<int>.
If that were the case, then we would have a function foo<X<int>> from that
instantiation, available for use when we get to instantiate the destructor
of X<X<int>>. The question is: do we need to instantiate X<int> in order to
instantiate X<X<int>>?
(Here's a sidenote: apparently, icc only instantiates the *type* X<int>,
but not the destructor X<int>::~X. I can infer this because if it did,
then it would want to call bar<int> which in turn would want to call
foo<int>; that one, however, doesn't exist...)
W.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22363