public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: gccbugs@contacts.eelis.net To: gcc-gnats@gcc.gnu.org Subject: c++/10552: Small sample using nested templates causes internal compiler error. Date: Tue, 29 Apr 2003 19:26:00 -0000 [thread overview] Message-ID: <20030429192242.18701.qmail@sources.redhat.com> (raw) >Number: 10552 >Category: c++ >Synopsis: Small sample using nested templates causes internal compiler error. >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: ice-on-legal-code >Submitter-Id: net >Arrival-Date: Tue Apr 29 19:26:00 UTC 2003 >Closed-Date: >Last-Modified: >Originator: Eelis van der Weegen >Release: gcc versions 3.2.2 and 3.2.1 >Organization: >Environment: My Windows workstation: gcc version 3.2.2 (mingw special 20030208-1) Configured with: ../gcc/configure --with-gcc --with-gnu-ld --with-gnu-as --host=mingw32 --target=mingw32 --prefix=/mingw --enable-threads --disable-nls --enable-languages=c++,f77,objc --disable-win32-registry --disable-shared --enable-sjlj-exceptions Thread model: win32 Also reproduced on my Slackware Linux box: gcc version 3.2.1 Configured with: ../gcc-3.2.1/configure --prefix=/usr --enable-shared --enable-threads=posix --enable-__cxa_atexit --disable-checking --with-gnu-ld --verbose --target=i386-slackware-linux --host=i386-slackware-linux Thread model: posix >Description: Compiling the following code: template <template <typename> class A, typename> struct B { typedef typename A<int>::t t; }; template <typename D> struct E { template <typename> struct F { typedef int t; }; typedef typename B<F, D>::t t; }; typedef E<int>::t t; results in the following error: internal error: Segmentation fault >How-To-Repeat: Try compiling the code from the description. >Fix: No idea. >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2003-04-29 19:26 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-04-29 19:26 gccbugs [this message] 2003-04-29 19:54 reichelt 2003-05-01 9:47 lerdsuwa 2003-05-01 13:46 Kriang Lerdsuwanakij 2003-05-11 10:06 lerdsuwa
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=20030429192242.18701.qmail@sources.redhat.com \ --to=gccbugs@contacts.eelis.net \ --cc=gcc-gnats@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).