public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: reichelt@igpm.rwth-aachen.de
To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org,
sneechy@hotmail.com
Subject: Re: c++/8149: internal error: Segmentation fault
Date: Wed, 23 Oct 2002 13:36:00 -0000 [thread overview]
Message-ID: <20021023203647.2923.qmail@sources.redhat.com> (raw)
Synopsis: internal error: Segmentation fault
State-Changed-From-To: open->analyzed
State-Changed-By: reichelt
State-Changed-When: Wed Oct 23 13:36:45 2002
State-Changed-Why:
Confirmed.
The example can be reduced a little bit further:
-------------------------snip here-------------------------
struct B { template <typename U> struct C; };
template <typename T> struct A { typedef typename T::C V; };
A<B>::V p;
-------------------------snip here-------------------------
Compiling this with "g++ -c" using the 3.2-branch or the main trunk
results in an ICE (checked on i686-pc-linux-gnu). With gcc 3.0.x or
2.95.x I get an error message:
PR8149.cc:3: aggregate `B::C<U> p' has incomplete type and cannot be
initialized
PR8149.cc:3: storage size of `p' isn't known
Changing "struct C;" to "struct C{};" in the first line to get rid of this
message (the rest of the code still remains illegal) causes gcc 3.0.x to
issue an ICE and 2.95.x to issue an assembler error.
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8149
next reply other threads:[~2002-10-23 20:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-23 13:36 reichelt [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-10-04 15:16 sneechy
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=20021023203647.2923.qmail@sources.redhat.com \
--to=reichelt@igpm.rwth-aachen.de \
--cc=gcc-bugs@gcc.gnu.org \
--cc=gcc-gnats@gcc.gnu.org \
--cc=gcc-prs@gcc.gnu.org \
--cc=nobody@gcc.gnu.org \
--cc=sneechy@hotmail.com \
/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).