public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/36262] [4.3 Regression] Extreme memory usage of VRP compared to older versions Date: Sat, 31 May 2008 13:02:00 -0000 [thread overview] Message-ID: <20080531130158.28552.qmail@sourceware.org> (raw) In-Reply-To: <bug-36262-1532@http.gcc.gnu.org/bugzilla/> ------- Comment #7 from rguenth at gcc dot gnu dot org 2008-05-31 13:01 ------- Subject: Bug 36262 Author: rguenth Date: Sat May 31 13:01:10 2008 New Revision: 136237 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=136237 Log: 2008-05-31 Richard Guenther <rguenther@suse.de> PR tree-optimization/34244 * fold-const.c (tree_expr_nonnegative_warnv_p): Do not ask VRP. (tree_expr_nonzero_warnv_p): Likewise. * tree-vrp.c (vrp_expr_computes_nonnegative): Call ssa_name_nonnegative_p. (vrp_expr_computes_nonzero): Call ssa_name_nonzero_p. (extract_range_from_unary_expr): Use vrp_expr_computes_nonzero, not tree_expr_nonzero_warnv_p. PR tree-optimization/36262 Revert 2007-11-29 Zdenek Dvorak <ook@ucw.cz> PR tree-optimization/34244 * tree-vrp.c (adjust_range_with_scev): Clear scev cache. (record_numbers_of_iterations): New function. (execute_vrp): Cache the numbers of iterations of loops. * tree-scalar-evolution.c (scev_reset_except_niters): New function. (scev_reset): Use scev_reset_except_niters. * tree-scalar-evolution.h (scev_reset_except_niters): Declare. Modified: trunk/gcc/ChangeLog trunk/gcc/fold-const.c trunk/gcc/tree-scalar-evolution.c trunk/gcc/tree-scalar-evolution.h trunk/gcc/tree-vrp.c -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36262
next prev parent reply other threads:[~2008-05-31 13:02 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-05-18 23:06 [Bug c/36262] New: Extreme memory usage " hakonrk at fys dot uio dot no 2008-05-18 23:07 ` [Bug c/36262] " hakonrk at fys dot uio dot no 2008-05-19 9:19 ` [Bug middle-end/36262] [4.3/4.4 Regression] Extreme memory usage of VRP " rguenth at gcc dot gnu dot org 2008-05-19 9:43 ` rguenth at gcc dot gnu dot org 2008-05-19 11:01 ` rguenth at gcc dot gnu dot org 2008-05-20 13:01 ` rguenth at gcc dot gnu dot org 2008-05-27 8:32 ` rguenth at gcc dot gnu dot org 2008-05-28 22:09 ` rguenth at gcc dot gnu dot org 2008-05-31 13:02 ` [Bug middle-end/36262] [4.3 " rguenth at gcc dot gnu dot org 2008-05-31 13:02 ` rguenth at gcc dot gnu dot org [this message] 2008-06-06 15:05 ` rguenth at gcc dot gnu dot org 2008-06-06 20:07 ` rguenth at gcc dot gnu dot org 2008-06-06 20:08 ` rguenth at gcc dot gnu dot org 2008-07-06 10:00 ` steven at gcc dot gnu dot org 2008-07-06 12:28 ` rguenth 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=20080531130158.28552.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: linkBe 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).