public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tbsaunde at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/64326] [5 Regression] ICE at -O3 on x86_64-linux-gnu in check_probability, at basic-block.h:581
Date: Thu, 22 Jan 2015 16:27:00 -0000	[thread overview]
Message-ID: <bug-64326-4-6WZ40w9rKq@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64326-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64326

tbsaunde at gcc dot gnu.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |tbsaunde at gcc dot gnu.org

--- Comment #3 from tbsaunde at gcc dot gnu.org ---
So, in cfghooks.c make_forwarder_block we redirect two edges to point at a bb, 
both edges have probability 1 (10000) the first edge's src bb has freq 873, and
the second 9409.  So at least one of those is slightly high, and when we
combine them we set the freq for dummy to 10282.  Then later we copy that freq
of 10282 and assert because that's not a sane frequency.  Its not entirely
clear to me if make_forwarder_block should handle this case by capping freq at
10000, or if the bug is even earlier when those two initial frequencies are
generated.


  parent reply	other threads:[~2015-01-22 16:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-16  8:34 [Bug tree-optimization/64326] New: " su at cs dot ucdavis.edu
2014-12-16  9:53 ` [Bug tree-optimization/64326] [5 Regression] " rguenth at gcc dot gnu.org
2014-12-16  9:57 ` mpolacek at gcc dot gnu.org
2015-01-22 16:27 ` tbsaunde at gcc dot gnu.org [this message]
2015-01-30 18:05 ` hubicka at gcc dot gnu.org
2015-02-05 13:27 ` tbsaunde at gcc dot gnu.org
2015-02-09 22:49 ` hubicka at gcc dot gnu.org
2015-02-10  1:48 ` tbsaunde at gcc dot gnu.org
2015-02-10 14:49 ` tbsaunde at gcc dot gnu.org
2015-02-10 15:30 ` tbsaunde 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-64326-4-6WZ40w9rKq@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).