public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/52943] [4.7/4.8 Regression] likely wrong code bug caused by predictive commoning
Date: Thu, 12 Apr 2012 11:41:00 -0000	[thread overview]
Message-ID: <bug-52943-4-CvWhrgt6zG@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-52943-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from Richard Guenther <rguenth at gcc dot gnu.org> 2012-04-12 11:39:12 UTC ---
Author: rguenth
Date: Thu Apr 12 11:38:47 2012
New Revision: 186374

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=186374
Log:
2012-04-12  Richard Guenther  <rguenther@suse.de>

    PR tree-optimization/52943
    * tree-chrec.h (chrec_is_positive): Remove.
    * tree-scalar-evolution.c (chrec_is_positive): Move ...
    * tree-data-ref.c (chrec_is_positive): ... here.  Make static.
    Return false for a constant zero instead of negative.
    (analyze_siv_subscript_cst_affine): Handle zero difference
    in the initial condition explicitely.

    * gcc.dg/torture/pr52943.c: New testcase.

Added:
    trunk/gcc/testsuite/gcc.dg/torture/pr52943.c
Modified:
    trunk/gcc/ChangeLog
    trunk/gcc/testsuite/ChangeLog
    trunk/gcc/tree-chrec.h
    trunk/gcc/tree-data-ref.c
    trunk/gcc/tree-scalar-evolution.c


  parent reply	other threads:[~2012-04-12 11:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-12  3:28 [Bug c/52943] New: likely wrong code bug regehr at cs dot utah.edu
2012-04-12  9:24 ` [Bug tree-optimization/52943] [4.7/4.8 Regression] likely wrong code bug caused by predictive commoning rguenth at gcc dot gnu.org
2012-04-12  9:25 ` rguenth at gcc dot gnu.org
2012-04-12 11:41 ` rguenth at gcc dot gnu.org [this message]
2012-04-12 12:52 ` rguenth at gcc dot gnu.org
2012-04-12 12:52 ` 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-52943-4-CvWhrgt6zG@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).