public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
* Re: c++/95: No implicit instantiation of static data member templates on HPUX
@ 2002-10-22 16:06 Wolfgang Bangerth
0 siblings, 0 replies; only message in thread
From: Wolfgang Bangerth @ 2002-10-22 16:06 UTC (permalink / raw)
To: nobody; +Cc: gcc-prs
The following reply was made to PR c++/95; it has been noted by GNATS.
From: Wolfgang Bangerth <bangerth@ticam.utexas.edu>
To: law@redhat.com, <gcc-bugs@gcc.gnu.org>, <gcc-gnats@gcc.gnu.org>
Cc:
Subject: Re: c++/95: No implicit instantiation of static data member templates
on HPUX
Date: Tue, 22 Oct 2002 18:04:49 -0500 (CDT)
c++/95 is about the following:
-----------------------------------------
template <class T> class X { static int *i; };
class Y {};
int *X<Y>::i; // = 0;
-----------------------------------------
With gcc2.95, this puts the static variable into different segments,
depending on whether we have the initialization I commented out, or not.
On Linux, I get either
00000004 C _t1X1Z1Y.i # without initialization
00000000 D _t1X1Z1Y.i # with initialization
This difference has gone with present CVS and 3.2. I always get
00000000 B _ZN1XI1YE1iE
Jeff, this report is against HPUX which I cannot test, but you are the
maintainer of this port. Can you test the above test case with/without the
initializer, and if you the symbol is defined in both cases, can you
please close this report?
Thanks
Wolfgang
-------------------------------------------------------------------------
Wolfgang Bangerth email: bangerth@ticam.utexas.edu
www: http://www.ticam.utexas.edu/~bangerth
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2002-10-22 23:06 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2002-10-22 16:06 c++/95: No implicit instantiation of static data member templates on HPUX Wolfgang Bangerth
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).