public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "patrick.marlier at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/48075] New: [trans-mem] infinite loop when compiling
Date: Fri, 11 Mar 2011 15:42:00 -0000	[thread overview]
Message-ID: <bug-48075-4@http.gcc.gnu.org/bugzilla/> (raw)

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

           Summary: [trans-mem] infinite loop when compiling
           Product: gcc
           Version: trans-mem
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: patrick.marlier@gmail.com
                CC: rth@gcc.gnu.org, aldyh@gcc.gnu.org


Created attachment 23632
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=23632
infinite calls testcase.

An infinite loop happens with the attached testcase.
Maybe not related to trans-mem specifically...

Here the backtrace:

#10225 0x000000000050b680 in instantiate_class_template (type=0x7ffff6b20e70)
at ../../transactional-memory/gcc/cp/pt.c:7965
#10226 0x00000000005740b7 in complete_type (type=0x7ffff6b20e70) at
../../transactional-memory/gcc/cp/typeck.c:130
#10227 0x00000000004de334 in tsubst_decl (t=0x7ffff6bd31e0,
args=0x7ffff6b1f090, complain=3)
    at ../../transactional-memory/gcc/cp/pt.c:9533
#10228 0x00000000004e96d0 in tsubst (t=0x7ffff6bd31e0, args=0x7ffff6b1f090,
complain=3, in_decl=0x0)
    at ../../transactional-memory/gcc/cp/pt.c:9912
#10229 0x000000000050b680 in instantiate_class_template (type=0x7ffff6b200a8)
at ../../transactional-memory/gcc/cp/pt.c:7965
#10230 0x00000000005740b7 in complete_type (type=0x7ffff6b200a8) at
../../transactional-memory/gcc/cp/typeck.c:130
#10231 0x00000000004de334 in tsubst_decl (t=0x7ffff6bd31e0,
args=0x7ffff6b1c4b0, complain=3)
    at ../../transactional-memory/gcc/cp/pt.c:9533
#10232 0x00000000004e96d0 in tsubst (t=0x7ffff6bd31e0, args=0x7ffff6b1c4b0,
complain=3, in_decl=0x0)
    at ../../transactional-memory/gcc/cp/pt.c:9912
#10233 0x000000000050b680 in instantiate_class_template (type=0x7ffff6b1b2a0)
at ../../transactional-memory/gcc/cp/pt.c:7965
#10234 0x00000000005740b7 in complete_type (type=0x7ffff6b1b2a0) at
../../transactional-memory/gcc/cp/typeck.c:130
#10235 0x00000000004de334 in tsubst_decl (t=0x7ffff6bd31e0,
args=0x7ffff6b198d0, complain=3)
    at ../../transactional-memory/gcc/cp/pt.c:9533
#10236 0x00000000004e96d0 in tsubst (t=0x7ffff6bd31e0, args=0x7ffff6b198d0,
complain=3, in_decl=0x0)
    at ../../transactional-memory/gcc/cp/pt.c:9912
...

Patrick Marlier.


             reply	other threads:[~2011-03-11 15:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-11 15:42 patrick.marlier at gmail dot com [this message]
2011-03-12 22:03 ` [Bug c++/48075] " rth at gcc dot gnu.org
2011-03-31  8:55 ` patrick.marlier at gmail dot com
2011-10-12 16:14 ` [Bug c++/48075] " paolo.carlini at oracle dot com
2011-12-03  3:53 ` patrick.marlier at gmail dot com
2012-01-09 15:50 ` patrick.marlier at gmail 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-48075-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).