public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rmansfield at qnx dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/56857] New: Crash in resolve_args
Date: Sat, 06 Apr 2013 15:09:00 -0000	[thread overview]
Message-ID: <bug-56857-4@http.gcc.gnu.org/bugzilla/> (raw)


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

             Bug #: 56857
           Summary: Crash in resolve_args
    Classification: Unclassified
           Product: gcc
           Version: 4.8.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: rmansfield@qnx.com


Created attachment 29815
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=29815
Partially reduced testcase

$ ./xgcc -v
Using built-in specs.
COLLECT_GCC=./xgcc
Target: x86_64-unknown-linux-gnu
Configured with: ../configure --enable-languages=c++ --disable-bootstrap
Thread model: posix
gcc version 4.9.0 20130406 (experimental) [trunk revision 197540] (GCC) 


Testcase is partially reduced by delta from
libstdc++-v3/src/c++11/compatibility-thread-c++0x.cc 

$ ./xgcc -B. -std=gnu++11 ~/ice.ii
<snip>

/home/ryan/ice.ii:62:17:   required from here
/home/ryan/ice.ii:48:20: internal compiler error: Segmentation fault
        (__args) ...);
                    ^
0xa9722f crash_signal
    ../../gcc/toplev.c:332
0x4fc912 resolve_args
    ../../gcc/cp/call.c:3755
0x5150f7 build_new_function_call(tree_node*, vec<tree_node*, va_gc,
vl_embed>**, bool, int)
    ../../gcc/cp/call.c:3865
0x681632 finish_call_expr(tree_node*, vec<tree_node*, va_gc, vl_embed>**, bool,
bool, int)
    ../../gcc/cp/semantics.c:2252
0x566b98 tsubst_copy_and_build(tree_node*, tree_node*, int, tree_node*, bool,
bool)
    ../../gcc/cp/pt.c:14099
0x56d13b tsubst_expr
    ../../gcc/cp/pt.c:13376
0x57af51 tsubst_decl
    ../../gcc/cp/pt.c:10759
0x5825e7 tsubst
    ../../gcc/cp/pt.c:11121
0x5825e7 tsubst(tree_node*, tree_node*, int, tree_node*)
    ../../gcc/cp/pt.c:11106
0x57935b tsubst_copy
    ../../gcc/cp/pt.c:12180
0x564d3c tsubst_copy_and_build(tree_node*, tree_node*, int, tree_node*, bool,
bool)
    ../../gcc/cp/pt.c:14435
0x56d13b tsubst_expr
    ../../gcc/cp/pt.c:13376
0x581997 tsubst
    ../../gcc/cp/pt.c:11799
0x581997 tsubst(tree_node*, tree_node*, int, tree_node*)
    ../../gcc/cp/pt.c:11106
0x581902 tsubst
    ../../gcc/cp/pt.c:11190
0x581902 tsubst(tree_node*, tree_node*, int, tree_node*)
    ../../gcc/cp/pt.c:11106
0x57adef tsubst_decl
    ../../gcc/cp/pt.c:10658
0x5825e7 tsubst
    ../../gcc/cp/pt.c:11121
0x5825e7 tsubst(tree_node*, tree_node*, int, tree_node*)
    ../../gcc/cp/pt.c:11106
0x56ebe3 tsubst_expr
    ../../gcc/cp/pt.c:12892
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <http://gcc.gnu.org/bugs.html> for instructions.


             reply	other threads:[~2013-04-06 15:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-06 15:09 rmansfield at qnx dot com [this message]
2013-04-06 15:12 ` [Bug c++/56857] " rmansfield at qnx dot com
2013-04-06 18:42 ` rmansfield at qnx dot com
2013-04-06 22:18 ` paolo.carlini at oracle dot com
2013-04-16 13:35 ` rmansfield at qnx dot com
2013-04-16 21:43 ` jason at gcc dot gnu.org

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-56857-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).