public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/53321] [4.8 Regression] LTO bootstrap failed with bootstrap-profiled Date: Fri, 25 May 2012 20:26:00 -0000 [thread overview] Message-ID: <bug-53321-4-VvqD8KnWX7@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-53321-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53321 --- Comment #9 from Uros Bizjak <ubizjak at gmail dot com> 2012-05-25 20:10:54 UTC --- (gdb) bt #0 internal_error (gmsgid=0x1214dd8 "vector %s %s domain error, in %s at %s:%u") at ../../gcc-svn/trunk/gcc/diagnostic.c:951 #1 0x0000000000ef31a9 in vec_assert_fail (op=0x11d3093 "index", struct_name=0xfa61d0 "VEC(inline_edge_summary_t,base)", file=<optimized out>, line=200, function=0xfa6fd0 "inline_edge_summary") at ../../gcc-svn/trunk/gcc/vec.c:528 #2 0x000000000079114e in VEC_inline_edge_summary_t_base_index (ix_=<optimized out>, vec_=<optimized out>, file_=<optimized out>, line_=<optimized out>, function_=<optimized out>) at ../../gcc-svn/trunk/gcc/ipa-inline.h:145 #3 inline_edge_summary (edge=<optimized out>) at ../../gcc-svn/trunk/gcc/ipa-inline.h:199 #4 cgraph_propagate_frequency_1 (node=0x7ffff109b138, data=0x7fffffffdb20) at ../../gcc-svn/trunk/gcc/cgraph.c:1805 #5 0x0000000000794810 in cgraph_for_node_and_aliases (node=0x7ffff109b138, callback=0x790f10 <cgraph_propagate_frequency_1(cgraph_node*, void*)>, data=0x7fffffffdb20, include_overwritable=true) at ../../gcc-svn/trunk/gcc/cgraph.c:1633 #6 0x0000000000794a92 in cgraph_propagate_frequency (node=0x7ffff109b138) at ../../gcc-svn/trunk/gcc/cgraph.c:1839 #7 0x0000000000930487 in symtab_remove_unreachable_nodes (before_inlining_p=<optimized out>, file=0x0) at ../../gcc-svn/trunk/gcc/ipa.c:455 #8 0x000000000079b6a0 in ipa_passes () at ../../gcc-svn/trunk/gcc/cgraphunit.c:1853
next prev parent reply other threads:[~2012-05-25 20:11 UTC|newest] Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-05-11 11:21 [Bug bootstrap/53321] New: " hjl.tools at gmail dot com 2012-05-11 12:03 ` [Bug bootstrap/53321] " hjl.tools at gmail dot com 2012-05-11 15:49 ` hubicka at gcc dot gnu.org 2012-05-11 17:06 ` hjl.tools at gmail dot com 2012-05-11 18:29 ` hubicka at gcc dot gnu.org 2012-05-12 11:16 ` hubicka at gcc dot gnu.org 2012-05-19 19:40 ` hjl.tools at gmail dot com 2012-05-25 20:06 ` ubizjak at gmail dot com 2012-05-25 20:09 ` ubizjak at gmail dot com 2012-05-25 20:26 ` ubizjak at gmail dot com [this message] 2012-05-26 11:00 ` ubizjak at gmail dot com 2012-05-26 19:42 ` steven at gcc dot gnu.org 2012-05-26 20:23 ` steven at gcc dot gnu.org 2012-05-28 8:48 ` hubicka at gcc dot gnu.org 2012-06-23 14:51 ` hjl.tools at gmail dot com 2012-07-02 9:49 ` ubizjak at gmail dot com 2012-07-03 15:58 ` ubizjak at gmail dot com 2012-07-03 18:17 ` ubizjak at gmail dot com 2012-07-04 13:50 ` uros at gcc dot gnu.org 2012-07-04 13:56 ` [Bug middle-end/53321] " ubizjak at gmail dot com 2012-07-04 13:58 ` ubizjak at gmail dot com 2012-07-06 18:30 ` hjl.tools at gmail dot com 2012-07-06 18:46 ` hjl.tools at gmail dot com 2012-07-06 20:23 ` hjl.tools at gmail dot com 2012-07-06 23:17 ` hjl.tools at gmail dot com 2012-08-02 16:59 ` hjl at gcc dot gnu.org 2012-08-02 18:06 ` hjl.tools 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-53321-4-VvqD8KnWX7@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).