[Bug lto/61646] New: [4.10 Regression] ICE: in write_ts_type_non_common_tree_pointers, at tree-streamer-out.c:812
trippels at gcc dot gnu.org
gcc-bugzilla@gcc.gnu.org
Sun Jun 29 07:30:00 GMT 2014
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61646
Bug ID: 61646
Summary: [4.10 Regression] ICE: in
write_ts_type_non_common_tree_pointers, at
tree-streamer-out.c:812
Product: gcc
Version: 4.10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: lto
Assignee: unassigned at gcc dot gnu.org
Reporter: trippels at gcc dot gnu.org
CC: hubicka at ucw dot cz
Happens during Firefox build:
markus@x4 ds % cat ManifestParser.ii
class nsChromeRegistry;
struct B
{
void (nsChromeRegistry::*regfunc)();
};
const B *a;
void fn1 ()
{
if (a->regfunc)
;
}
markus@x4 ds % c++ -flto -c ManifestParser.ii
ManifestParser.ii:11:1: internal compiler error: in
write_ts_type_non_common_tree_pointers, at tree-streamer-out.c:812
}
^
0xd4f480 write_ts_type_non_common_tree_pointers
../../gcc/gcc/tree-streamer-out.c:812
0xd4f480 streamer_write_tree_body(output_block*, tree_node*, bool)
../../gcc/gcc/tree-streamer-out.c:1017
0xa824a3 lto_write_tree_1
../../gcc/gcc/lto-streamer-out.c:364
0xa865ab DFS_write_tree
../../gcc/gcc/lto-streamer-out.c:1307
0xa88057 lto_output_tree(output_block*, tree_node*, bool, bool)
../../gcc/gcc/lto-streamer-out.c:1384
0xa822ff write_global_stream
../../gcc/gcc/lto-streamer-out.c:2136
0xa8a3ce lto_output_decl_state_streams
../../gcc/gcc/lto-streamer-out.c:2180
0xa8a3ce produce_asm_for_decls()
../../gcc/gcc/lto-streamer-out.c:2477
0xace1bf write_lto
../../gcc/gcc/passes.c:2260
0xad1188 ipa_write_summaries_1
../../gcc/gcc/passes.c:2319
0xad1188 ipa_write_summaries()
../../gcc/gcc/passes.c:2376
0x84d036 ipa_passes
../../gcc/gcc/cgraphunit.c:2090
0x84d036 compile()
../../gcc/gcc/cgraphunit.c:2186
0x84d2f4 finalize_compilation_unit()
../../gcc/gcc/cgraphunit.c:2341
0x63866e cp_write_global_declarations()
../../gcc/gcc/cp/decl2.c:4647
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.
More information about the Gcc-bugs
mailing list