public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: bangerth@dealii.org To: galen_sampson@yahoo.com, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org Subject: Re: c++/8561: Segfault when template class is not defined. Date: Tue, 19 Nov 2002 18:56:00 -0000 [thread overview] Message-ID: <20021113185638.13067.qmail@sources.redhat.com> (raw) Synopsis: Segfault when template class is not defined. State-Changed-From-To: open->analyzed State-Changed-By: bangerth State-Changed-When: Wed Nov 13 10:56:38 2002 State-Changed-Why: Confirmed. This is probably the minimal example: -------------------------- template <class T> class X {}; template <class T> class X<T>::Y : X<T>::Z {}; ----------------------------------- The code is of course bogus, since neither X::Y nor X::Z are forward declared. The compiler ICEs, however, also if X::Z _is_ forward declared, but X::Y is not. These are the messages I get (gcc 2.95 -- the last one -- does a little better, but not much; however, the message is significantly more helpful, so I raise the priority of this report): tmp/g> /home/bangerth/bin/gcc-3.3x-pre/bin/c++ -c x.ii x.ii:2: 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. tmp/g> /home/bangerth/bin/gcc-3.2.1-pre/bin/c++ -c x.ii x.ii:2: internal 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. gcc-2.95: tmp/g> c++ -c x.ii x.ii:2: `X<T>' does not have a nested type named `Y' x.ii:2: template class without a name x.ii:2: template class without a name x.ii:2: confused by earlier errors, bailing out http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8561
next reply other threads:[~2002-11-13 18:56 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-11-19 18:56 bangerth [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-11-20 2:46 reichelt 2002-11-19 18:39 galen_sampson
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=20021113185638.13067.qmail@sources.redhat.com \ --to=bangerth@dealii.org \ --cc=galen_sampson@yahoo.com \ --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: linkBe 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).