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++/3613: [alpha] no instantiation of explicitly initialized static template member variables (gcc 3.0) (fwd)
Date: Thu, 06 Feb 2003 23:16:00 -0000	[thread overview]
Message-ID: <20030206231600.11837.qmail@sources.redhat.com> (raw)

The following reply was made to PR c++/3613; it has been noted by GNATS.

From: Wolfgang Bangerth <bangerth@ticam.utexas.edu>
To: gcc-gnats@gcc.gnu.org
Cc:  
Subject: Re: c++/3613: [alpha] no instantiation of explicitly initialized
 static template member variables (gcc 3.0) (fwd)
Date: Thu, 6 Feb 2003 17:08:03 -0600 (CST)

 ---------- Forwarded message ----------
 Date: Thu, 6 Feb 2003 23:51:00 +0100 (CET)
 From: Stefan Schwarzer <sts@ica1.uni-stuttgart.de>
 To: bangerth@dealii.org
 Subject: Re: c++/3613: [alpha] no instantiation of explicitly initialized
     static template member variables (gcc 3.0)
 
 
 Wolfgang:
 
 sorry for the late reply, but I left your hometown almost two years
 ago... 
 
 Concerning the instantiation of static member variables on alpha / gcc.
 The latest version I have got on the alpha 
 is dusty 3.0.2, but the snippet now compiles fine in the same
 OS-environment as reported initially. Though I did not take the time
 to test more recent versions, I assume the issue can be closed...
 
 Thanks for the attention,  
 
 Stefan.
 
 >Old Synopsis: no instantiation of explicitly initialized static template member variaibles on alphas
 >New Synopsis: [alpha] no instantiation of explicitly initialized static template member variables (gcc 3.0)
 >
 >State-Changed-From-To: open->feedback
 >State-Changed-By: bangerth
 >State-Changed-When: Sat Feb  1 21:36:51 2003
 >State-Changed-Why:
 >    Is this still an issue with a more recent gcc version on Alpha?
 >    (Asking back into my hometown... :-)
 >    
 >    Thanks
 >      Wolfgang
 >
 >http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=3613
 
 -- 
 Stefan Schwarzer                                     home: +49-(0)7071-368980
                                (?-                 mobile: +49-(0)170-8633428  
 Eugenstr. 22                   //\                  sts@ica1.uni-stuttgart.de
 72072 Tuebingen, Germany      -V_/----  http://www.ica1.uni-stuttgart.de/~sts
 


                 reply	other threads:[~2003-02-06 23:16 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=20030206231600.11837.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).