public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Reichelt <reichelt@igpm.rwth-aachen.de> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c++/8061: ICE Date: Fri, 04 Oct 2002 12:56:00 -0000 [thread overview] Message-ID: <20021004195601.30272.qmail@sources.redhat.com> (raw) The following reply was made to PR c++/8061; it has been noted by GNATS. From: Reichelt <reichelt@igpm.rwth-aachen.de> To: gcc-gnats@gcc.gnu.org, gcc-bugs@gcc.gnu.org, nobody@gcc.gnu.org, dave@boost-consulting.com Cc: Subject: Re: c++/8061: ICE Date: Fri, 4 Oct 2002 22:36:03 +0200 Hi, the bug can be reproduced with the following legal code snippet: -------------------------------snip here------------------------ struct A { template <typename T> struct B {}; }; template <typename T> struct C { typedef A::template B<void> Type; }; -------------------------------snip here------------------------ Compiling this with gcc 2.95.x, 3.0.x, 3.1, 3.2 (just use g++ -c) and the main trunk will result in an ICE (checked on i686-pc-linux-gnu and mips-sgi-irix6.5). The example can be further reduced to following code snippet which is illegal code, however: -------------------------------snip here------------------------ struct A { template <typename T> struct B {}; }; typedef A::template B<void> Type; -------------------------------snip here------------------------ Greetings, Volker Reichelt http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8061
next reply other threads:[~2002-10-04 19:56 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-10-04 12:56 Reichelt [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-09-28 6:38 lerdsuwa 2002-09-26 16:36 dave
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=20021004195601.30272.qmail@sources.redhat.com \ --to=reichelt@igpm.rwth-aachen.de \ --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).