public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/46528] [4.6 Regression] profiledbootstrap failure
Date: Thu, 25 Nov 2010 13:40:00 -0000 [thread overview]
Message-ID: <bug-46528-4-Y5BS2CbJgC@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-46528-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46528
Richard Guenther <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |WAITING
--- Comment #17 from Richard Guenther <rguenth at gcc dot gnu.org> 2010-11-25 12:40:32 UTC ---
Please try
Index: gcc/profile.c
===================================================================
--- gcc/profile.c (revision 167127)
+++ gcc/profile.c (working copy)
@@ -940,7 +943,8 @@ branch_prob (void)
for (gsi = gsi_last_bb (bb); !gsi_end_p (gsi); gsi_prev (&gsi))
{
last = gsi_stmt (gsi);
- if (gimple_has_location (last))
+ if (!is_gimple_debug (last)
+ && gimple_has_location (last))
break;
}
we do CFG manipulations based on debug stmts (verified with a later
assert that triggers on -O2 -g -fprofile-use).
It's of course unfortunate that we do this BB splitting at all when
not doing coverage test.
next prev parent reply other threads:[~2010-11-25 12:41 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-17 23:35 [Bug bootstrap/46528] New: [ia64] " steven at gcc dot gnu.org
2010-11-18 10:11 ` [Bug bootstrap/46528] " rguenth at gcc dot gnu.org
2010-11-18 15:03 ` mkuvyrkov at gcc dot gnu.org
2010-11-18 22:09 ` steven at gcc dot gnu.org
2010-11-20 23:19 ` [Bug bootstrap/46528] [4.6 Regression] " ubizjak at gmail dot com
2010-11-21 20:08 ` hjl.tools at gmail dot com
2010-11-24 21:08 ` ubizjak at gmail dot com
2010-11-24 21:36 ` ubizjak at gmail dot com
2010-11-24 21:51 ` rguenth at gcc dot gnu.org
2010-11-24 22:04 ` rguenth at gcc dot gnu.org
2010-11-24 22:17 ` ubizjak at gmail dot com
2010-11-24 22:32 ` ubizjak at gmail dot com
2010-11-24 22:57 ` ubizjak at gmail dot com
2010-11-24 23:06 ` ubizjak at gmail dot com
2010-11-24 23:53 ` ubizjak at gmail dot com
2010-11-25 0:19 ` ubizjak at gmail dot com
2010-11-25 12:41 ` rguenth at gcc dot gnu.org
2010-11-25 13:40 ` rguenth at gcc dot gnu.org [this message]
2010-11-25 13:48 ` Jan Hubicka
2010-11-25 13:56 ` hubicka at ucw dot cz
2010-11-25 18:09 ` hjl.tools at gmail dot com
2010-11-25 19:59 ` ubizjak at gmail dot com
2010-11-26 9:54 ` rguenth at gcc dot gnu.org
2010-11-26 9:55 ` rguenth at gcc dot gnu.org
2010-12-06 19:31 ` jakub 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-46528-4-Y5BS2CbJgC@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).