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/56273] [4.8 regression] Bogus -Warray-bounds warning
Date: Thu, 21 Feb 2013 10:53:00 -0000	[thread overview]
Message-ID: <bug-56273-4-Wgezsct0ZE@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-56273-4@http.gcc.gnu.org/bugzilla/>


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

--- Comment #11 from Richard Biener <rguenth at gcc dot gnu.org> 2013-02-21 10:52:44 UTC ---
Author: rguenth
Date: Thu Feb 21 10:52:39 2013
New Revision: 196200

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=196200
Log:
2013-02-21  Richard Biener  <rguenther@suse.de>

    PR tree-optimization/56415
    Revert
    2013-02-11  Richard Biener  <rguenther@suse.de>

    PR tree-optimization/56273
    * tree-vrp.c (simplify_cond_using_ranges): Disable for the
    first VRP run.

    * g++.dg/warn/Warray-bounds-6.C: New testcase.
    * gcc.dg/tree-ssa/pr21559.c: Adjust.
    * gcc.dg/tree-ssa/vrp17.c: Likewise.
    * gcc.dg/tree-ssa/vrp18.c: Likewise.
    * gcc.dg/tree-ssa/vrp23.c: Likewise.
    * gcc.dg/tree-ssa/vrp24.c: Likewise.

Removed:
    trunk/gcc/testsuite/g++.dg/warn/Warray-bounds-6.C
Modified:
    trunk/gcc/ChangeLog
    trunk/gcc/testsuite/ChangeLog
    trunk/gcc/testsuite/gcc.dg/tree-ssa/pr21559.c
    trunk/gcc/testsuite/gcc.dg/tree-ssa/vrp17.c
    trunk/gcc/testsuite/gcc.dg/tree-ssa/vrp18.c
    trunk/gcc/testsuite/gcc.dg/tree-ssa/vrp23.c
    trunk/gcc/testsuite/gcc.dg/tree-ssa/vrp24.c
    trunk/gcc/tree-vrp.c


  parent reply	other threads:[~2013-02-21 10:53 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-10  7:05 [Bug other/56273] New: " daniel at constexpr dot org
2013-02-10  7:07 ` [Bug other/56273] " daniel at constexpr dot org
2013-02-10  7:35 ` [Bug tree-optimization/56273] " pinskia at gcc dot gnu.org
2013-02-10 12:18 ` rguenth at gcc dot gnu.org
2013-02-11  9:33 ` rguenth at gcc dot gnu.org
2013-02-11 10:52 ` rguenth at gcc dot gnu.org
2013-02-11 13:33 ` rguenth at gcc dot gnu.org
2013-02-11 13:34 ` rguenth at gcc dot gnu.org
2013-02-11 15:09 ` rguenth at gcc dot gnu.org
2013-02-12 16:24 ` vincenzo.innocente at cern dot ch
2013-02-12 23:50 ` pinskia at gcc dot gnu.org
2013-02-21 10:53 ` rguenth at gcc dot gnu.org [this message]
2013-02-21 10:54 ` rguenth at gcc dot gnu.org
2013-03-08 15:33 ` rguenth at gcc dot gnu.org
2013-03-22 14:48 ` [Bug tree-optimization/56273] [4.8/4.9 " jakub at gcc dot gnu.org
2013-05-31 10:58 ` jakub at gcc dot gnu.org
2013-10-16  9:48 ` jakub at gcc dot gnu.org
2014-01-07  6:54 ` law at redhat dot com
2014-05-22  9:02 ` [Bug tree-optimization/56273] [4.8/4.9/4.10 " rguenth at gcc dot gnu.org
2014-12-19 13:26 ` [Bug tree-optimization/56273] [4.8/4.9/5 " jakub at gcc dot gnu.org
2015-01-27  9:50 ` [Bug tree-optimization/56273] [4.8/4.9 " rguenth at gcc dot gnu.org
2015-01-27  9:50 ` rguenth at gcc dot gnu.org
2015-01-27 11:03 ` rguenth at gcc dot gnu.org
2015-02-19 14:14 ` rguenth at gcc dot gnu.org
2015-02-24 13:05 ` [Bug tree-optimization/56273] [4.8 " rguenth at gcc dot gnu.org
2015-02-24 13:19 ` 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-56273-4-Wgezsct0ZE@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).