public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Wolfgang Bangerth <bangerth@ices.utexas.edu>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/6749: [2003-05-12] infinte loop with inheritance of abstract classes
Date: Wed, 14 May 2003 00:56:00 -0000	[thread overview]
Message-ID: <20030514005600.20090.qmail@sources.redhat.com> (raw)

The following reply was made to PR c++/6749; it has been noted by GNATS.

From: Wolfgang Bangerth <bangerth@ices.utexas.edu>
To: gcc-bugs@gcc.gnu.org, <gcc-gnats@gcc.gnu.org>, <rullo.pat@tiscalinet.it>
Cc:  
Subject: Re: c++/6749: [2003-05-12] infinte loop with inheritance of abstract
 classes
Date: Tue, 13 May 2003 19:47:44 -0500 (CDT)

 This is even shorter than Nathanael's testcase:
 --------------------------------
 template <class T> struct inner {};
  
 template <class T> struct parent {
     virtual void f()
       { parent<inner<T> > p; };
 };
  
 template struct parent<int>;
 ---------------------------------
 
 I don't think it's particularly surprising that this puts gcc into a loong 
 loop, since in parent<T> we instantiate parent<inner<T> >, in which we 
 instantiate parent<inner<inner<T> > >, in which... well, we get the 
 picture.
 
 Compiling this indeed takes very long. I didn't check how, long, but what 
 _is_ surprising, that it takes long already with -ftemplate-depth-2, which 
 really shouldn't happen.
 
 Funny testcase...
 
 W.
 
 -------------------------------------------------------------------------
 Wolfgang Bangerth              email:            bangerth@ices.utexas.edu
                                www: http://www.ices.utexas.edu/~bangerth/
 
 


                 reply	other threads:[~2003-05-14  0:56 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20030514005600.20090.qmail@sources.redhat.com \
    --to=bangerth@ices.utexas.edu \
    --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: 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).