public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/53106] [4.8 Regression] Benchmarks in SPEC CPU 2006 failed to build
Date: Wed, 25 Apr 2012 16:12:00 -0000	[thread overview]
Message-ID: <bug-53106-4-TgyBhjX2Ch@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-53106-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53106

--- Comment #6 from Jan Hubicka <hubicka at gcc dot gnu.org> 2012-04-25 16:11:43 UTC ---
This is previously latent bug in frequency verification.  We check that
frequencies of edges match frequencies of basic block. This check is disabled
when function is inline, because then the frequencies of edges are scaled to
the same base as in the outer function.

Now what happens is that the function gets cloned, then the original version
gets fully inlined and finally becomes unreachable.  We however need to keep
function body around and thus remove_unreachable_nodes turns the inline clone
back to offline re-enabling the check that finally fires.

I am not sure how we got around this problem previously.  I am doiuble
checking.


  parent reply	other threads:[~2012-04-25 16:12 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-24 21:49 [Bug middle-end/53106] New: " hjl.tools at gmail dot com
2012-04-24 21:50 ` [Bug middle-end/53106] " hjl.tools at gmail dot com
2012-04-24 23:13 ` hjl.tools at gmail dot com
2012-04-24 23:13 ` hjl.tools at gmail dot com
2012-04-25 11:05 ` rguenth at gcc dot gnu.org
2012-04-25 14:35 ` hubicka at gcc dot gnu.org
2012-04-25 14:39 ` hjl.tools at gmail dot com
2012-04-25 16:12 ` hubicka at gcc dot gnu.org [this message]
2012-04-25 16:22 ` hubicka at gcc dot gnu.org
2012-05-03 15:17 ` wschmidt at gcc dot gnu.org
2012-05-03 19:19 ` hubicka at gcc dot gnu.org
2012-09-07 11:28 ` rguenth 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-53106-4-TgyBhjX2Ch@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).