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/55079] [4.8 regression] false positive -Warray-bounds
Date: Fri, 02 Nov 2012 16:35:00 -0000	[thread overview]
Message-ID: <bug-55079-4-zAeHdDmv1l@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-55079-4@http.gcc.gnu.org/bugzilla/>


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

--- Comment #4 from Jan Hubicka <hubicka at gcc dot gnu.org> 2012-11-02 16:35:01 UTC ---
Author: hubicka
Date: Fri Nov  2 16:34:52 2012
New Revision: 193098

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=193098
Log:

    PR middle-end/55079
    * tree-ssa-loop-niter.c (number_of_iterations_exit): Update
    MAX field if NITER was folded to contant.
    (record_estimate): Sanity check.
    * tree-ssa-loop-ivcanon.c (remove_exits_and_undefined_stmts): New
    function.
    (remove_redundant_iv_test): New function.
    (loops_to_unloop, loops_to_unloop_nunroll): New static vars.
    (unloop_loops): Break out from ...
    (try_unroll_loop_completely): ... here; Pass in MAXITER; use
    remove_exits_and_undefined_stmts; do not unloop.
    (canonicalize_loop_induction_variables): Compute MAXITER;
    use remove_redundant_iv_test; remove loop_close_ssa_invalidated
    and irred_invalidated arguments.
    (canonicalize_induction_variables): Compute fresh bound estimates;
    unloop; walk from innermost.
    (tree_unroll_loops_completely): Likewise.

    * gcc.dg/tree-ssa/cunroll-10.c: New testcase.
    * gcc.dg/tree-ssa/cunroll-9.c: New testcase.

Added:
    trunk/gcc/testsuite/gcc.dg/tree-ssa/cunroll-10.c
    trunk/gcc/testsuite/gcc.dg/tree-ssa/cunroll-9.c
Modified:
    trunk/gcc/ChangeLog
    trunk/gcc/testsuite/ChangeLog
    trunk/gcc/tree-ssa-loop-ivcanon.c
    trunk/gcc/tree-ssa-loop-niter.c


  parent reply	other threads:[~2012-11-02 16:35 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-26  9:56 [Bug tree-optimization/55079] New: [4.8 regeression] " dimhen at gmail dot com
2012-10-26 10:09 ` [Bug tree-optimization/55079] " rguenth at gcc dot gnu.org
2012-10-30  9:34 ` [Bug tree-optimization/55079] [4.8 regression] " rguenth at gcc dot gnu.org
2012-10-30  9:35 ` rguenth at gcc dot gnu.org
2012-11-02 16:35 ` hubicka at gcc dot gnu.org [this message]
2012-11-02 16:47 ` hubicka at gcc dot gnu.org
2012-11-02 18:45 ` hubicka at gcc dot gnu.org
2012-11-02 20:51 ` hubicka at gcc dot gnu.org
2012-11-14 19:31 ` [Bug tree-optimization/55079] [4.8 regression] false positive -Warray-bounds (also seen at -O3 bootstrap) hubicka at gcc dot gnu.org
2012-11-15  1:01 ` hubicka at gcc dot gnu.org
2012-12-07 12:55 ` rguenth at gcc dot gnu.org
2012-12-10 13:23 ` rguenth at gcc dot gnu.org
2012-12-10 13:50 ` rguenth at gcc dot gnu.org
2012-12-10 14:14 ` rguenth at gcc dot gnu.org
2012-12-10 16:27 ` hubicka at ucw dot cz
2012-12-11 10:06 ` rguenth at gcc dot gnu.org
2012-12-11 10:08 ` rguenth at gcc dot gnu.org
2012-12-12  9:33 ` schwab 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-55079-4-zAeHdDmv1l@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).