public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: bangerth@dealii.org
To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org,
	struppi@acm.org
Subject: Re: c++/8591: g++ crashes while instantiating templates
Date: Thu, 21 Nov 2002 09:00:00 -0000	[thread overview]
Message-ID: <20021115165206.6866.qmail@sources.redhat.com> (raw)

Synopsis: g++ crashes while instantiating templates

State-Changed-From-To: open->analyzed
State-Changed-By: bangerth
State-Changed-When: Fri Nov 15 08:52:05 2002
State-Changed-Why:
    Confirmed. A reduced testcase is
    -------------------------------------
    namespace NS {
      template <class T1, class T2, class T3 = int, class T4 = int>
      struct C {};
    }
    
    template <class T> class X {
        friend class NS::C;
    };
    
    X<int> c;
    ----------------------------------
    I get a segfault:
    tmp/g> /home/bangerth/bin/gcc-3.3x-pre/bin/g++ -c x.cc
    x.cc: In instantiation of `X<int>':
    x.cc:10:   instantiated from here
    x.cc:6: internal compiler error: Speicherzugriffsfehler
    Please submit a full bug report,
    with preprocessed source if appropriate.
    See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.
    
    This is for all versions of gcc, including present CVS.
    
    My list of similar reports (friends and templates and/or 
    namespaces) includes PRs 8355, 8280, 8099, 53, 641, 765, 
    1016, 6256. The last one may be the closest.
    
    By the way, the code is illegal, since you have to declare
    the friend as
      template <...> friend class NS::C;
    Fixing this makes the ICE go away.

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


             reply	other threads:[~2002-11-15 16:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-21  9:00 bangerth [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-12-19  7:21 lerdsuwa
2002-11-21  7:41 struppi

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=20021115165206.6866.qmail@sources.redhat.com \
    --to=bangerth@dealii.org \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@gcc.gnu.org \
    --cc=struppi@acm.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).