public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "trippels at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/66405] New: [5/6 Regression] ICE: in tsubst, at cp/pt.c:11984 Date: Wed, 03 Jun 2015 13:48:00 -0000 [thread overview] Message-ID: <bug-66405-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66405 Bug ID: 66405 Summary: [5/6 Regression] ICE: in tsubst, at cp/pt.c:11984 Product: gcc Version: 6.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: trippels at gcc dot gnu.org Target Milestone: --- % g++ -std=c++11 -c zip.ii ... /home/trippels/range-v3/include/meta/meta.hpp:887:66: internal compiler error: in tsubst, at cp/pt.c:12021 integer_sequence<bool, (Bools || true)...>>; ^ 0x10162107 tsubst(tree_node*, tree_node*, int, tree_node*) ../../gcc/gcc/cp/pt.c:12021 0x10171293 tsubst_copy ../../gcc/gcc/cp/pt.c:13391 0x1015e0bb tsubst_copy_and_build(tree_node*, tree_node*, int, tree_node*, bool, bool) ../../gcc/gcc/cp/pt.c:15756 0x1015e737 tsubst_copy_and_build(tree_node*, tree_node*, int, tree_node*, bool, bool) ../../gcc/gcc/cp/pt.c:14789 0x101678c7 tsubst_expr ../../gcc/gcc/cp/pt.c:14424 0x1016bda7 gen_elem_of_pack_expansion_instantiation ../../gcc/gcc/cp/pt.c:9939 0x1016bda7 tsubst_pack_expansion ../../gcc/gcc/cp/pt.c:10142 0x10170343 tsubst_template_args ../../gcc/gcc/cp/pt.c:10242 0x1017028f tsubst_template_args ../../gcc/gcc/cp/pt.c:10260 0x101707d7 tsubst_aggr_type ../../gcc/gcc/cp/pt.c:10475 0x101614af tsubst(tree_node*, tree_node*, int, tree_node*) ../../gcc/gcc/cp/pt.c:11935 0x101701ab tsubst_template_args ../../gcc/gcc/cp/pt.c:10278 0x101707d7 tsubst_aggr_type ../../gcc/gcc/cp/pt.c:10475 0x101614af tsubst(tree_node*, tree_node*, int, tree_node*) ../../gcc/gcc/cp/pt.c:11935 0x1016a6d7 tsubst_decl ../../gcc/gcc/cp/pt.c:11365 0x10161733 tsubst(tree_node*, tree_node*, int, tree_node*) ../../gcc/gcc/cp/pt.c:11856 0x10172fab instantiate_template_1 ../../gcc/gcc/cp/pt.c:15991 0x10172fab instantiate_template(tree_node*, tree_node*, int) ../../gcc/gcc/cp/pt.c:16041 0x101616d7 instantiate_alias_template ../../gcc/gcc/cp/pt.c:16071 0x101616d7 tsubst(tree_node*, tree_node*, int, tree_node*) ../../gcc/gcc/cp/pt.c:11883 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.
next reply other threads:[~2015-06-03 13:48 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-06-03 13:48 trippels at gcc dot gnu.org [this message] 2015-06-03 13:48 ` [Bug c++/66405] " trippels at gcc dot gnu.org 2015-06-03 13:57 ` trippels at gcc dot gnu.org 2015-06-03 14:09 ` mpolacek at gcc dot gnu.org 2015-06-04 11:26 ` trippels at gcc dot gnu.org 2015-06-05 19:14 ` jason at gcc dot gnu.org 2015-06-05 19:14 ` jason at gcc dot gnu.org 2015-06-05 19:18 ` jason at gcc dot gnu.org 2015-06-05 19:18 ` jason at gcc dot gnu.org 2015-06-05 19:18 ` 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-66405-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: linkBe 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).