public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: giovannibajo@libero.it
To: gawrilow@math.tu-berlin.de, gcc-bugs@gcc.gnu.org,
	gcc-prs@gcc.gnu.org, giovannibajo@libero.it, nobody@gcc.gnu.org
Subject: Re: c++/10661: ICE in instantiate_decl, at cp/pt.c:10052 while instantiating static member variables
Date: Thu, 08 May 2003 17:07:00 -0000	[thread overview]
Message-ID: <20030508170736.10761.qmail@sources.redhat.com> (raw)

Old Synopsis: [3.3/3.4? regression] ICE in instantiate_decl
New Synopsis: ICE in instantiate_decl, at cp/pt.c:10052 while instantiating static member variables

Responsible-Changed-From-To: bajo->unassigned
Responsible-Changed-By: bajo
Responsible-Changed-When: Thu May  8 17:07:36 2003
Responsible-Changed-Why:
    Analysys is done
State-Changed-From-To: open->analyzed
State-Changed-By: bajo
State-Changed-When: Thu May  8 17:07:36 2003
State-Changed-Why:
    Ok, I'm done with this report. This is the reduced
    snippet that triggers the bug:
    
    ------------------------------------------------
    template <class A>
    struct Foo
    {
    	static const int var = 0; 
    
    	template <class>
    	struct Nested
    	{
    		static const int nested_var = var;
    	}; 
    };
    
    template <class A>
    struct Bar
    {
        typename Foo<A>::Nested<void> a;
    };
    
    template struct Bar<void>;
    ------------------------------------------------
    pr10661.cpp: In instantiation of `const int Foo<void>::var':
    pr10661.cpp:9:   instantiated from `Foo<void>::Nested<void>'
    pr10661.cpp:16:   instantiated from `Bar<void>'
    pr10661.cpp:19:   instantiated from here
    pr10661.cpp:4: internal compiler error: in instantiate_decl, at cp/pt.c:10330
    Please submit a full bug report,
    
    As anticipated, the code is illegal: it's missing a
    keyword 'template' in line 16, but we should not ICE
    anyway. Now the funny thing is, this reduced snippet
    is not a regression. I have no _clue_ why the original
    big testcase did compile on 3.2, probably for some weird
    reason. And I will _not_ go through everything again to
    find the difference, since there is an easy fix for this:
    just make the code legal. 
    Anyway, while working on this I forked out about 10 other
    ICEs, which I will file to GNATS and analyze in the next
    few days.

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


             reply	other threads:[~2003-05-08 17:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-08 17:07 giovannibajo [this message]
2003-05-08 17:11 giovannibajo

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=20030508170736.10761.qmail@sources.redhat.com \
    --to=giovannibajo@libero.it \
    --cc=gawrilow@math.tu-berlin.de \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --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).