public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: jsg@rz.uni-potsdam.de
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: driver/10544: g++ crashes when compiling
Date: Wed, 30 Apr 2003 11:46:00 -0000	[thread overview]
Message-ID: <20030430114601.13631.qmail@sources.redhat.com> (raw)

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

From: jsg@rz.uni-potsdam.de
To: bangerth@dealii.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
   jsg@rz.uni-potsdam.de, nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org
Cc:  
Subject: Re: driver/10544: g++ crashes when compiling
Date: Wed, 30 Apr 2003 13:42:37 +0200

 Hi there,
 
 Thanks alot for so quick of an answer. There is no gcc 3.3.X release on the gcc 
 website so I assume I need to get it through CVS.
 
 Jean
 
 Zitat von bangerth@dealii.org:
 
 > Synopsis: g++ crashes when compiling
 > 
 > State-Changed-From-To: open->closed
 > State-Changed-By: bangerth
 > State-Changed-When: Tue Apr 29 17:11:19 2003
 > State-Changed-Why:
 >     That was an easy one: gcc3.2 crashes on
 >     -----------------------------
 >     template <typename> struct X {
 >         typedef int (P)();
 >         static P p;
 >     };
 >     template class X<char>;
 >     -----------------------------
 >     The bug is fixed for 3.3 and 3.4, though.
 >     
 >     Wolfgang
 > 
 > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-
 trail&database=gcc&pr=10544
 > 
 
 
 


             reply	other threads:[~2003-04-30 11:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-30 11:46 jsg [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-04-30 13:56 Wolfgang Bangerth
2003-04-29 17:11 bangerth
2003-04-29 16:56 jsg

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=20030430114601.13631.qmail@sources.redhat.com \
    --to=jsg@rz.uni-potsdam.de \
    --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).