public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/26602] final_cleanup can mess up incoming frequencies
Date: Sat, 11 Mar 2006 05:00:00 -0000	[thread overview]
Message-ID: <20060311050044.1467.qmail@sourceware.org> (raw)
In-Reply-To: <bug-26602-6528@http.gcc.gnu.org/bugzilla/>



------- Comment #1 from pinskia at gcc dot gnu dot org  2006-03-11 05:00 -------
Hmm, what is happening here is we fold the conditional and then update the
frequency for the next bb but not the ones after it which causes us to get the
warnings:
Invalid sum of incoming frequencies 2731, should be 2048

The numbers before the cleanup:
  # BLOCK 9 freq:719
  # BLOCK 3 freq:2156

After:
  # BLOCK 2 freq:2875


But:
  # BLOCK 6 freq:375
  # BLOCK 3 freq:2048


2875-375 == 2731 != 2048


-- 


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


      reply	other threads:[~2006-03-11  5:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-08  5:15 [Bug tree-optimization/26602] New: " pinskia at gcc dot gnu dot org
2006-03-11  5:00 ` pinskia at gcc dot gnu dot org [this message]

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=20060311050044.1467.qmail@sourceware.org \
    --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).