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/55875] [4.8 Regression] IVopts caused miscompilation
Date: Mon, 07 Jan 2013 17:08:00 -0000	[thread overview]
Message-ID: <bug-55875-4-EzOESrkEzQ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-55875-4@http.gcc.gnu.org/bugzilla/>


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

--- Comment #6 from Jan Hubicka <hubicka at gcc dot gnu.org> 2013-01-07 17:07:57 UTC ---
OK, I understnad the issue now.  It is bug caused by my patch indeed.
The problem is logic in scev_probably_wraps_p that is trying to prove that
given IV at given STMT is not wrapping based on loop bounds connected.
When I was extending loop bounds to contain not only statements that dominate
the exit BB, I verified the walkers that they are valid after the change.
In this case it is however not true. What I missed is that it does two things

1) it tries to prove that STMT is bounded by given bound based on fact that
bound's STMT dominate the statement
2) it tries to prove the bound based on number of iterations of loop that it
derrives from the bounds

2) needs to be updated.  I am testing patch.


  parent reply	other threads:[~2013-01-07 17:08 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-04 12:09 [Bug tree-optimization/55875] New: " jakub at gcc dot gnu.org
2013-01-04 12:09 ` [Bug tree-optimization/55875] " jakub at gcc dot gnu.org
2013-01-04 12:21 ` mpolacek at gcc dot gnu.org
2013-01-04 12:24 ` jakub at gcc dot gnu.org
2013-01-07 13:37 ` hubicka at gcc dot gnu.org
2013-01-07 14:09 ` rakdver at iuuk dot mff.cuni.cz
2013-01-07 14:11 ` rakdver at gcc dot gnu.org
2013-01-07 17:08 ` hubicka at gcc dot gnu.org [this message]
2013-01-08 16:13 ` hubicka at gcc dot gnu.org
2013-01-08 17:56 ` hubicka at gcc dot gnu.org
2013-01-08 18:28 ` jakub at gcc dot gnu.org
2013-01-09 15:11 ` hubicka at gcc dot gnu.org
2013-01-09 15:13 ` jakub at gcc dot gnu.org
2013-01-09 16:29 ` hubicka at ucw dot cz
2013-01-09 16:35 ` 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-55875-4-EzOESrkEzQ@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).