public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/56163] New: Template instantiation limit not kicking in
Date: Thu, 31 Jan 2013 13:57:00 -0000	[thread overview]
Message-ID: <bug-56163-4@http.gcc.gnu.org/bugzilla/> (raw)


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56163

             Bug #: 56163
           Summary: Template instantiation limit not kicking in
    Classification: Unclassified
           Product: gcc
           Version: 4.8.0
            Status: UNCONFIRMED
          Keywords: ice-on-invalid-code
          Severity: normal
          Priority: P3
         Component: c++
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: jakub@gcc.gnu.org
                CC: jason@gcc.gnu.org


template <class U>
struct B
{
  typedef void type;
};
template <bool U>
struct C
{
};
template <typename T, typename E = void>
struct D {
  static const bool d = false;
};
template <typename T>
struct D<T, typename B<C<D<T>::d > >::type>
{
  static const bool d = false;
};

D<double> d;

reduced from https://bugzilla.redhat.com/show_bug.cgi?id=904652 segfaults due
to
endless recursion during instantiation, -ftemplate-depth= limit doesn't seem to
affect this.  This ICEd already with 3.2, so might not be a regression.


             reply	other threads:[~2013-01-31 13:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-31 13:57 jakub at gcc dot gnu.org [this message]
2013-08-10 21:04 ` [Bug c++/56163] " paolo.carlini at oracle dot com

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=bug-56163-4@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).