public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ghoort1 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/68010] internal compiler error: in tree_to_shwi, at tree.h:3661
Date: Sun, 18 Oct 2015 19:02:00 -0000 [thread overview]
Message-ID: <bug-68010-4-RQHaP096gp@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-68010-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68010
--- Comment #1 from ghoort1 at gmail dot com ---
At GCC-5.1.1
/home/ghoort/projects/nfg/NFserver/StructDecoder.h:67:2: internal compiler
error: in tree_to_shwi, at tree.h:3856
}
^
0x806864 tree_to_shwi(tree_node const*)
../../src/gcc/tree.h:3856
0x806864 add_data_member_location_attribute
../../src/gcc/dwarf2out.c:15327
0x8137ce gen_inheritance_die
../../src/gcc/dwarf2out.c:19886
0x8137ce gen_member_die
../../src/gcc/dwarf2out.c:19938
0x8137ce gen_struct_or_union_type_die
../../src/gcc/dwarf2out.c:20039
0x81425c gen_tagged_type_die
../../src/gcc/dwarf2out.c:20228
0x8145c1 gen_type_die_with_usage
../../src/gcc/dwarf2out.c:20377
0x815881 gen_type_die
../../src/gcc/dwarf2out.c:20430
0x815881 modified_type_die
../../src/gcc/dwarf2out.c:10817
0x815fff force_type_die
../../src/gcc/dwarf2out.c:20729
0x8161db get_context_die
../../src/gcc/dwarf2out.c:20644
0x8161db force_decl_die
../../src/gcc/dwarf2out.c:20663
0x81611a get_context_die
../../src/gcc/dwarf2out.c:20647
0x81611a force_decl_die
../../src/gcc/dwarf2out.c:20663
0x825853 dwarf2out_imported_module_or_decl_1
../../src/gcc/dwarf2out.c:21157
0x825d07 process_scope_var
../../src/gcc/dwarf2out.c:20540
0x825da7 decls_for_scope
../../src/gcc/dwarf2out.c:20567
0x825f58 gen_lexical_block_die
../../src/gcc/dwarf2out.c:19487
0x825f58 gen_block_die
../../src/gcc/dwarf2out.c:20514
0x825e0a decls_for_scope
../../src/gcc/dwarf2out.c:20581
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <file:///usr/share/doc/gcc-5/README.Bugs> for instructions.
CMakeFiles/NFServer.dir/build.make:445: recipe for target
'CMakeFiles/NFServer.dir/home/ghoort/projects/nfg/NFserver/nfg_parser.cpp.o'
failed
next prev parent reply other threads:[~2015-10-18 19:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-18 18:33 [Bug c++/68010] New: " ghoort1 at gmail dot com
2015-10-18 19:02 ` ghoort1 at gmail dot com [this message]
2015-10-18 19:23 ` [Bug c++/68010] " trippels at gcc dot gnu.org
2015-10-18 19:53 ` ghoort1 at gmail dot com
2015-10-18 20:18 ` [Bug debug/68010] " trippels at gcc dot gnu.org
2015-10-19 17:43 ` trippels at gcc dot gnu.org
2015-10-21 20:15 ` ghoort1 at gmail dot com
2015-10-22 7:48 ` trippels at gcc dot gnu.org
2021-08-13 21:46 ` [Bug debug/68010] ICE with -g and using namespace and namespace alias pinskia at gcc dot gnu.org
2024-03-25 5:25 ` [Bug debug/68010] [11/12/13/14 Regression] ICE with -g and using namespace and namespace alias inside a template class with dependent inheritance pinskia 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-68010-4-RQHaP096gp@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).