public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Wolfgang Bangerth <bangerth@ticam.utexas.edu>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/95: No implicit instantiation of static data member templates on HPUX
Date: Tue, 22 Oct 2002 16:06:00 -0000	[thread overview]
Message-ID: <20021022230601.8907.qmail@sources.redhat.com> (raw)

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
 
 
 


                 reply	other threads:[~2002-10-22 23:06 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20021022230601.8907.qmail@sources.redhat.com \
    --to=bangerth@ticam.utexas.edu \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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: link
Be 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).