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 tree-optimization/27795] [4.1 Regression] optimizer produces faulty code [tree-vrp] Date: Mon, 24 Jul 2006 08:26:00 -0000 [thread overview] Message-ID: <20060724082615.22219.qmail@sourceware.org> (raw) In-Reply-To: <bug-27795-12751@http.gcc.gnu.org/bugzilla/> ------- Comment #7 from rguenth at gcc dot gnu dot org 2006-07-24 08:26 ------- Subject: Bug 27795 Author: rguenth Date: Mon Jul 24 08:25:57 2006 New Revision: 115709 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=115709 Log: 2006-07-21 Richard Guenther <rguenther@suse.de> PR tree-optimization/27795 PR tree-optimization/27639 PR tree-optimization/26719 Backport from mainline 2006-05-24 Zdenek Dvorak <dvorakz@suse.cz> * tree-vrp.c (adjust_range_with_scev): Use scev_direction and adjust call to scev_probably_wraps_p. * tree-ssa-loop-niter.c (compare_trees, convert_step_widening, used_in_pointer_arithmetic_p, convert_step): Removed. (nowrap_type_p): New function. (scev_probably_wraps_p): Rewritten. * tree-scalar-evolution.c (instantiate_parameters_1): Do not call chrec_convert if chrec_convert_aggressive might have been used. * tree-chrec.c (convert_affine_scev, chrec_convert_1, scev_direction): New functions. (chrec_convert): Changed to a wrapper over chrec_convert_1. * tree-ssa-loop-ivopts.c (idx_find_step): Use convert_affine_scev instead of convert_step. * tree-flow.h (scev_probably_wraps_p): Declaration changed. (convert_step): Declaration removed. (convert_affine_scev, nowrap_type_p, scev_direction): Declare. * gcc.dg/pr27639.c: New test. * gcc.dg/pr26719.c: New test. * gcc.dg/tree-ssa/scev-cast.c: New test. Added: branches/gcc-4_1-branch/gcc/testsuite/gcc.dg/pr26719.c - copied unchanged from r114057, trunk/gcc/testsuite/gcc.dg/pr26719.c branches/gcc-4_1-branch/gcc/testsuite/gcc.dg/pr27639.c - copied unchanged from r114057, trunk/gcc/testsuite/gcc.dg/pr27639.c branches/gcc-4_1-branch/gcc/testsuite/gcc.dg/tree-ssa/scev-cast.c - copied unchanged from r114057, trunk/gcc/testsuite/gcc.dg/tree-ssa/scev-cast.c Modified: branches/gcc-4_1-branch/gcc/ChangeLog branches/gcc-4_1-branch/gcc/testsuite/ChangeLog branches/gcc-4_1-branch/gcc/tree-chrec.c branches/gcc-4_1-branch/gcc/tree-flow.h branches/gcc-4_1-branch/gcc/tree-scalar-evolution.c branches/gcc-4_1-branch/gcc/tree-ssa-loop-ivopts.c branches/gcc-4_1-branch/gcc/tree-ssa-loop-niter.c branches/gcc-4_1-branch/gcc/tree-vrp.c -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27795
next prev parent reply other threads:[~2006-07-24 8:26 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-05-29 16:52 [Bug c++/27795] New: optimizer produces faulty code S dot Diederich at gmx dot de 2006-05-29 16:53 ` [Bug c++/27795] " S dot Diederich at gmx dot de 2006-05-29 16:54 ` S dot Diederich at gmx dot de 2006-05-29 16:58 ` [Bug tree-optimization/27795] [4.1/4.2 Regression] optimizer produces faulty code [tree-vrp] pinskia at gcc dot gnu dot org 2006-05-29 17:05 ` [Bug tree-optimization/27795] [4.1 " pinskia at gcc dot gnu dot org 2006-05-29 18:03 ` pinskia at gcc dot gnu dot org 2006-05-30 13:46 ` rguenth at gcc dot gnu dot org 2006-07-21 12:27 ` rguenth at gcc dot gnu dot org 2006-07-24 8:26 ` rguenth at gcc dot gnu dot org [this message] 2006-07-24 8:29 ` 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=20060724082615.22219.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).