public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "d.g.gorbachev at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug lto/64075] New: [5 Regression] ICE: in bp_pack_value, at data-streamer.h:106 Date: Tue, 25 Nov 2014 21:23:00 -0000 [thread overview] Message-ID: <bug-64075-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64075 Bug ID: 64075 Summary: [5 Regression] ICE: in bp_pack_value, at data-streamer.h:106 Product: gcc Version: 5.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: lto Assignee: unassigned at gcc dot gnu.org Reporter: d.g.gorbachev at gmail dot com Created attachment 34119 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=34119&action=edit Testcase GCC 5.0.0 20141123 (experimental). bug.c:4:1: internal compiler error: in bp_pack_value, at data-streamer.h:106 } ^ 0x817a447 bp_pack_value ../../gcc-5/gcc/data-streamer.h:105 0x893c35a bp_pack_value ../../gcc-5/gcc/data-streamer.h:115 0x893e94e pack_ts_function_decl_value_fields ../../gcc-5/gcc/tree-streamer-out.c:303 0x893e94e streamer_pack_tree_bitfields(output_block*, bitpack_d*, tree_node*) ../../gcc-5/gcc/tree-streamer-out.c:443 0x86045b9 lto_write_tree_1 ../../gcc-5/gcc/lto-streamer-out.c:370 0x860ea18 lto_write_tree ../../gcc-5/gcc/lto-streamer-out.c:404 0x860ea18 lto_output_tree_1 ../../gcc-5/gcc/lto-streamer-out.c:447 0x860ea18 DFS::DFS_write_tree(output_block*, DFS::sccs*, tree_node*, bool, bool, bool) ../../gcc-5/gcc/lto-streamer-out.c:1448 0x860f20e DFS::DFS(output_block*, tree_node*, bool, bool, bool) ../../gcc-5/gcc/lto-streamer-out.c:495 0x860fca2 lto_output_tree(output_block*, tree_node*, bool, bool) ../../gcc-5/gcc/lto-streamer-out.c:1552 0x8603c47 write_global_stream ../../gcc-5/gcc/lto-streamer-out.c:2339 0x8612480 lto_output_decl_state_streams ../../gcc-5/gcc/lto-streamer-out.c:2386 0x8612480 produce_asm_for_decls() ../../gcc-5/gcc/lto-streamer-out.c:2666 0x8668ab0 write_lto ../../gcc-5/gcc/passes.c:2391 0x866bdd9 ipa_write_summaries_1 ../../gcc-5/gcc/passes.c:2451 0x866bdd9 ipa_write_summaries(bool) ../../gcc-5/gcc/passes.c:2511 0x834d703 ipa_passes ../../gcc-5/gcc/cgraphunit.c:2091 0x834d703 symbol_table::compile() ../../gcc-5/gcc/cgraphunit.c:2187 0x834f542 symbol_table::finalize_compilation_unit() ../../gcc-5/gcc/cgraphunit.c:2340 0x81e0feb c_write_global_declarations() ../../gcc-5/gcc/c/c-decl.c:10777 Please submit a full bug report, with preprocessed source if appropriate. libgcc
next reply other threads:[~2014-11-25 21:23 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-11-25 21:23 d.g.gorbachev at gmail dot com [this message] 2014-11-25 21:25 ` [Bug lto/64075] " d.g.gorbachev at gmail dot com 2014-11-25 21:52 ` hjl.tools at gmail dot com 2014-11-25 22:29 ` hjl.tools at gmail dot com 2014-11-26 8:51 ` enkovich.gnu at gmail dot com 2014-11-26 10:11 ` rguenth at gcc dot gnu.org 2014-11-26 13:54 ` ienkovich at gcc dot gnu.org 2014-11-26 16:28 ` d.g.gorbachev at gmail dot com 2014-11-26 17:54 ` enkovich.gnu at gmail dot com
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-64075-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).