public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: ehrhardt@mathematik.uni-ulm.de
To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
	gendzwil@sedsystems.ca, nobody@gcc.gnu.org
Subject: Re: c++/9649: gcc hangs when static declared twice in templated class
Date: Mon, 10 Feb 2003 21:57:00 -0000	[thread overview]
Message-ID: <20030210215745.6119.qmail@sources.redhat.com> (raw)

Synopsis: gcc hangs when static declared twice in templated class

State-Changed-From-To: open->analyzed
State-Changed-By: cae
State-Changed-When: Mon Feb 10 21:57:45 2003
State-Changed-Why:
    Confrimed. All supported versions fail to compile this, 3.2.2 gives
    an endless loop, 3.3 and 3.4 give an ICE at the same place. Here's 
    a minimal legal example, it is possible to remove the out of class
    definition of the static member without the ICE going away.
    ---------------- cut -----------------
    template <class R>
    struct A {
    	static int _test;
    	static int _test;
    };
    template <class R> int A<R>::_test = 0;
    struct B : public A <int> { };
    ---------------- cut -----------------
    9649.cc: In instantiation of `A<int>':
    9649.cc:7:   instantiated from here
    9649.cc:4: internal compiler error: in finish_member_declaration, at 
       cp/semantics.c:1868
    Please submit a full bug report,
    with preprocessed source if appropriate.
    See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.
    

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9649


             reply	other threads:[~2003-02-10 21:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-10 21:57 ehrhardt [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-02-10 20:26 gendzwil

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=20030210215745.6119.qmail@sources.redhat.com \
    --to=ehrhardt@mathematik.uni-ulm.de \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=gendzwil@sedsystems.ca \
    --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).