public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rakdver at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/30730] -Wunsafe-loop-optimizations gives too many warnings
Date: Wed, 14 Mar 2007 00:39:00 -0000	[thread overview]
Message-ID: <20070314003903.9132.qmail@sourceware.org> (raw)
In-Reply-To: <bug-30730-5650@http.gcc.gnu.org/bugzilla/>



------- Comment #3 from rakdver at gcc dot gnu dot org  2007-03-14 00:39 -------
Subject: Bug 30730

Author: rakdver
Date: Wed Mar 14 00:38:34 2007
New Revision: 122896

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=122896
Log:
        PR tree-optimization/30730
        PR tree-optimization/26900
        * tree-ssa-loop-niter.c: Include gmp.h.
        (bounds): New type.
        (mpz_set_double_int, get_type_bounds, mpz_to_double_int,
        split_to_var_and_offset, determine_value_range,
        bound_difference_of_offsetted_base, refine_bounds_using_guard,
        bound_difference, bounds_add, bounds_negate,
        number_of_iterations_ne_max, dump_affine_iv): New functions.
        (number_of_iterations_ne, number_of_iterations_lt_to_ne,
        assert_loop_rolls_lt, assert_loop_rolls_le): Use bounds on the
        difference of initial and final value of control iv to validate
        results.
        (number_of_iterations_cond): Add loop parameter.  Determine bounds
        on the difference of the extremes of the control iv.  Add dumps.
        (expand_simple_operations): Handle phi nodes.
        (simplify_using_initial_conditions): Do not record used conditions.
        (number_of_iterations_exit): Pass loop to number_of_iterations_cond.
        Do not set additional_info.
        (implies_nonnegative_p, implies_ge_p): Removed.
        (derive_constant_upper_bound): Do not use parameter `additional'.
        (record_estimate): Parameter `additional' removed.  Parameter
        `i_bound' added.  Do not call derive_constant_upper_bound.
        (record_nonwrapping_iv): Use derive_constant_upper_bound to
        bound the number of iterations estimate.
        (estimate_numbers_of_iterations_loop): Pass the estimate from
        the number of iterations analysis to record_estimate.
        * tree.h (multiple_of_p): Declare.
        * tree-scalar-evolution.c (expression_expensive_p): Removed.
        (scev_const_prop): Do not check expression_expensive_p.
        * fold-const.c (multiple_of_p): Exported.
        * double-int.c (double_int_mask): Exported.
        * double-int.h (double_int_mask): Declare.
        * tree-flow.h (struct tree_niter_desc): Removed additional_info
        field.  Added max field.

        * gcc.dg/tree-ssa/loop-26.c: New test.


Added:
    trunk/gcc/testsuite/gcc.dg/tree-ssa/loop-26.c
Modified:
    trunk/gcc/ChangeLog
    trunk/gcc/double-int.c
    trunk/gcc/double-int.h
    trunk/gcc/testsuite/ChangeLog
    trunk/gcc/tree-flow.h
    trunk/gcc/tree-scalar-evolution.c
    trunk/gcc/tree-ssa-loop-niter.c
    trunk/gcc/tree.h


-- 


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


  parent reply	other threads:[~2007-03-14  0:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-07 20:25 [Bug c/30730] New: " roland dot illig at gmx dot de
2007-02-08  9:34 ` [Bug tree-optimization/30730] " rguenth at gcc dot gnu dot org
2007-02-08  9:38 ` rakdver at gcc dot gnu dot org
2007-03-14  0:39 ` rakdver at gcc dot gnu dot org [this message]
2007-07-10  8:31 ` spop at gcc dot gnu dot 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=20070314003903.9132.qmail@sourceware.org \
    --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).