public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bangerth at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/54994] New: [4.8 regression] New ICE in tsubst_copy
Date: Sat, 20 Oct 2012 02:23:00 -0000 [thread overview]
Message-ID: <bug-54994-4@http.gcc.gnu.org/bugzilla/> (raw)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54994
Bug #: 54994
Summary: [4.8 regression] New ICE in tsubst_copy
Classification: Unclassified
Product: gcc
Version: 4.8.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: bangerth@gmail.com
May or may not be related to PR 54844:
This little piece of code has recently started to produce an ICE on mainline:
..............................
template <bool> class X {};
template <typename T> struct A {
X<(sizeof(T)<sizeof(long double))> x;
};
A<int> a;
..............................
> c++ -c numerics/a.cc
numerics/a.cc: In instantiation of 'struct A<int>':
numerics/a.cc:7:8: required from here
numerics/a.cc:4:24: internal compiler error: in tsubst_copy, at cp/pt.c:12387
X<(sizeof(T)<sizeof(long double))> x;
^
linux-vdso.so.1: No such file or directory
0x596d03 tsubst_copy
../../mainline/gcc/cp/pt.c:12387
0x586762 tsubst_copy_and_build(tree_node*, tree_node*, int, tree_node*, bool,
bool)
../../mainline/gcc/cp/pt.c:13514
0x585b81 tsubst_copy_and_build(tree_node*, tree_node*, int, tree_node*, bool,
bool)
../../mainline/gcc/cp/pt.c:13539
0x585602 tsubst_copy_and_build(tree_node*, tree_node*, int, tree_node*, bool,
bool)
../../mainline/gcc/cp/pt.c:13494
0x58e6a4 tsubst_expr
../../mainline/gcc/cp/pt.c:13194
0x5a1002 tsubst_template_arg
../../mainline/gcc/cp/pt.c:9039
0x5a75e2 tsubst_template_args
../../mainline/gcc/cp/pt.c:9489
0x5add71 tsubst_aggr_type
../../mainline/gcc/cp/pt.c:9686
0x59e773 tsubst(tree_node*, tree_node*, int, tree_node*)
../../mainline/gcc/cp/pt.c:11039
0x599216 tsubst_decl
../../mainline/gcc/cp/pt.c:10329
0x59eb8c tsubst(tree_node*, tree_node*, int, tree_node*)
../../mainline/gcc/cp/pt.c:10965
0x5c4a5c instantiate_class_template_1
../../mainline/gcc/cp/pt.c:8778
0x5c4a5c instantiate_class_template(tree_node*)
../../mainline/gcc/cp/pt.c:9020
0x64eb2b complete_type(tree_node*)
../../mainline/gcc/cp/typeck.c:134
0x54b548 start_decl_1(tree_node*, bool)
../../mainline/gcc/cp/decl.c:4621
0x5675e1 start_decl(cp_declarator const*, cp_decl_specifier_seq*, int,
tree_node*, tree_node*, tree_node**)
../../mainline/gcc/cp/decl.c:4584
0x6415dc cp_parser_init_declarator
../../mainline/gcc/cp/parser.c:15887
0x641f6f cp_parser_simple_declaration
../../mainline/gcc/cp/parser.c:10560
0x63ce27 cp_parser_block_declaration
../../mainline/gcc/cp/parser.c:10441
0x647f3b cp_parser_declaration
../../mainline/gcc/cp/parser.c:10338
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.
Best
W.
next reply other threads:[~2012-10-20 2:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-20 2:23 bangerth at gmail dot com [this message]
2012-10-20 6:56 ` [Bug c++/54994] " jakub 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-54994-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).