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 tree-optimization/54717] [4.8 Regression] Runtime regression: polyhedron test "rnflow" degraded
Date: Wed, 14 Nov 2012 20:11:00 -0000	[thread overview]
Message-ID: <bug-54717-4-Pe82PR7z66@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-54717-4@http.gcc.gnu.org/bugzilla/>


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

Jan Hubicka <hubicka at gcc dot gnu.org> changed:

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

--- Comment #14 from Jan Hubicka <hubicka at gcc dot gnu.org> 2012-11-14 20:11:17 UTC ---
Hmm, the optimize_edge_for_speed never returns false here. The problem is that
patch assumes that interesting successors of block with partial anticipance are
blocks with partial anticipance. The anticipance however could be full and it
seems that full anticipance do not imply partial one
Index: tree-ssa-pre.c
===================================================================
*** tree-ssa-pre.c      (revision 193503)
--- tree-ssa-pre.c      (working copy)
*************** do_partial_partial_insertion (basic_bloc
*** 3525,3531 ****
                 may cause regressions on the speed path.  */
              FOR_EACH_EDGE (succ, ei, block->succs)
                {
!                 if (bitmap_set_contains_value (PA_IN (succ->dest), val))
                    {
                      if (optimize_edge_for_speed_p (succ))
                        do_insertion = true;
--- 3525,3532 ----
                 may cause regressions on the speed path.  */
              FOR_EACH_EDGE (succ, ei, block->succs)
                {
!                 if (bitmap_set_contains_value (PA_IN (succ->dest), val)
!                     || bitmap_set_contains_value (ANTIC_IN (succ->dest),
val))
                    {
                      if (optimize_edge_for_speed_p (succ))
                        do_insertion = true;


  parent reply	other threads:[~2012-11-14 20:11 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-26 12:54 [Bug tree-optimization/54717] New: " sergos.gnu at gmail dot com
2012-09-26 13:17 ` [Bug tree-optimization/54717] " ubizjak at gmail dot com
2012-09-26 14:17 ` [Bug tree-optimization/54717] [4.8 Regression] " rguenth at gcc dot gnu.org
2012-09-26 15:12 ` sergos.gnu at gmail dot com
2012-09-26 15:41 ` dominiq at lps dot ens.fr
2012-09-26 20:07 ` sergos.gnu at gmail dot com
2012-09-27  9:28 ` rguenth at gcc dot gnu.org
2012-09-27 10:43 ` rguenth at gcc dot gnu.org
2012-10-02 20:24 ` dominiq at lps dot ens.fr
2012-10-08  8:55 ` sergos.gnu at gmail dot com
2012-11-13 18:40 ` ubizjak at gmail dot com
2012-11-13 18:54 ` dominiq at lps dot ens.fr
2012-11-14 18:56 ` sergos.gnu at gmail dot com
2012-11-14 19:42   ` Jan Hubicka
2012-11-14 19:43 ` hubicka at ucw dot cz
2012-11-14 20:11 ` hubicka at gcc dot gnu.org [this message]
2012-11-15 10:28 ` hubicka at gcc dot gnu.org
2012-11-15 10:52 ` hubicka at gcc dot gnu.org
2012-11-15 15:07 ` dominiq at lps dot ens.fr
2012-11-16 10:37 ` hubicka at gcc dot gnu.org
2012-12-06 16:51 ` 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-54717-4-Pe82PR7z66@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).