public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "paolo.carlini at oracle dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/51488] ICE on infinite template recursion
Date: Sun, 11 Aug 2013 10:03:00 -0000	[thread overview]
Message-ID: <bug-51488-4-ZNMORiXhGW@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-51488-4@http.gcc.gnu.org/bugzilla/>

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

Paolo Carlini <paolo.carlini at oracle dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |manu at gcc dot gnu.org

--- Comment #2 from Paolo Carlini <paolo.carlini at oracle dot com> ---
Manuel, looks like these 3 testcases are instances of the very same issue: our
template instantiation depth control mechanism doesn't handle this case. I'm
attaching below a piece of a stack trace, to show you the infinite recursion.

I seem to remember you did work in this area: any tips to handle this case too?

////////////////

#82 0x000000000060338e in instantiate_class_template (type=0x7ffff687eb28) at
/scratch/Gcc/svn-dirs/trunk/gcc/cp/pt.c:9176
#83 0x00000000006e1e94 in complete_type (type=0x7ffff687eb28) at
/scratch/Gcc/svn-dirs/trunk/gcc/cp/typeck.c:131
#84 0x000000000061142b in tsubst (t=0x7ffff687e930, args=0x7ffff613d880,
complain=0, in_decl=0x0) at /scratch/Gcc/svn-dirs/trunk/gcc/cp/pt.c:11815
#85 0x00000000006033fc in tsubst_template_arg (t=0x7ffff687e930,
args=0x7ffff613d880, complain=0, in_decl=0x0) at
/scratch/Gcc/svn-dirs/trunk/gcc/cp/pt.c:9189
#86 0x000000000060549d in tsubst_template_args (t=0x7ffff613fe60,
args=0x7ffff613d880, complain=0, in_decl=0x0) at
/scratch/Gcc/svn-dirs/trunk/gcc/cp/pt.c:9730
#87 0x0000000000610886 in tsubst (t=0x7ffff613fe60, args=0x7ffff613d880,
complain=0, in_decl=0x0) at /scratch/Gcc/svn-dirs/trunk/gcc/cp/pt.c:11580
#88 0x000000000062f333 in get_class_bindings (main_tmpl=0x7ffff6878ac8,
tparms=0x7ffff688a800, spec_args=0x7ffff613fe60, args=0x7ffff688d528) at
/scratch/Gcc/svn-dirs/trunk/gcc/cp/pt.c:18055
#89 0x0000000000630399 in most_specialized_class (type=0x7ffff687eb28,
tmpl=0x7ffff6878ac8, complain=3) at
/scratch/Gcc/svn-dirs/trunk/gcc/cp/pt.c:18279
#90 0x0000000000600ad1 in instantiate_class_template_1 (type=0x7ffff687eb28) at
/scratch/Gcc/svn-dirs/trunk/gcc/cp/pt.c:8665
#91 0x000000000060338e in instantiate_class_template (type=0x7ffff687eb28) at
/scratch/Gcc/svn-dirs/trunk/gcc/cp/pt.c:9176


  parent reply	other threads:[~2013-08-11 10:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-09 23:09 [Bug c++/51488] New: " cas43 at cs dot stanford.edu
2013-08-10 21:06 ` [Bug c++/51488] " paolo.carlini at oracle dot com
2013-08-11 10:03 ` paolo.carlini at oracle dot com [this message]
2013-08-22 19:39 ` paolo.carlini at oracle dot com
2013-09-07 19:34 ` paolo.carlini at oracle dot com
2014-07-01 18:12 ` 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-51488-4-ZNMORiXhGW@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).