public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "paulo@matos-sorge.com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/58862] [4.9 Regression] LTO profiledbootstrap failure: lto1: ICE in edge_badness, at ipa-inline.c:1008
Date: Fri, 01 Nov 2013 17:01:00 -0000 [thread overview]
Message-ID: <bug-58862-4-HHRUQbDnwO@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-58862-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58862
--- Comment #9 from Paulo J. Matos <paulo@matos-sorge.com> ---
I didn't manage to reproduce the bug yet. With the git sha before my commit
4bc0f16, I get the following on a profiledbootstrap on x64:
insn-opinit.c: In function 'void init_all_optabs(target_optabs*)':
insn-opinit.c:1234:1: error: verify_flow_info: Wrong probability of edge
1437->2606 66380
init_all_optabs (struct target_optabs *optabs)
^
insn-opinit.c:1234:1: error: verify_flow_info: Wrong probability of edge
1427->2598 66380
insn-opinit.c:1234:1: internal compiler error: verify_flow_info failed
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.
Unfortunately running one of these takes a long time so it's a slow process to
check it out since as far as I am aware it's not possible to use a parallel
build. Do let me know if there's a fast way to build it.
I will keep investigating.
next prev parent reply other threads:[~2013-11-01 17:01 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-24 13:13 [Bug ipa/58862] New: " ubizjak at gmail dot com
2013-10-24 13:18 ` [Bug ipa/58862] " ubizjak at gmail dot com
2013-10-24 13:41 ` [Bug ipa/58862] [4.9 Regression] " rguenth at gcc dot gnu.org
2013-10-29 15:05 ` tejohnson at google dot com
2013-10-29 16:33 ` tejohnson at google dot com
2013-10-29 20:39 ` tejohnson at gcc dot gnu.org
2013-10-30 13:10 ` tejohnson at google dot com
2013-10-30 13:17 ` paulo@matos-sorge.com
2013-11-01 17:01 ` paulo@matos-sorge.com [this message]
2013-11-01 17:14 ` tejohnson at google dot com
2013-11-01 17:16 ` ubizjak at gmail dot com
2013-11-02 11:40 ` ubizjak at gmail dot com
2013-11-04 19:11 ` tejohnson at google dot com
2013-11-04 19:12 ` tejohnson at google dot com
2013-11-04 19:13 ` tejohnson at google dot com
2013-11-12 15:49 ` tejohnson at google dot com
2013-11-12 19:00 ` ubizjak at gmail dot com
2013-11-13 21:49 ` tejohnson at gcc dot gnu.org
2013-11-13 21:51 ` tejohnson at gcc dot gnu.org
2013-11-14 7:53 ` ubizjak at gmail dot com
2013-11-26 3:48 ` tejohnson 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-58862-4-HHRUQbDnwO@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).