public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/22348] [4.0/4.1 Regression] IV canonicalization causes execution of loops past their end condition
Date: Wed, 27 Jul 2005 14:06:00 -0000	[thread overview]
Message-ID: <20050727140436.20746.qmail@sourceware.org> (raw)
In-Reply-To: <20050707165800.22348.matt+gccbugs@ucc.asn.au>


------- Additional Comments From cvs-commit at gcc dot gnu dot org  2005-07-27 14:04 -------
Subject: Bug 22348

CVSROOT:	/cvs/gcc
Module name:	gcc
Changes by:	rakdver@gcc.gnu.org	2005-07-27 14:04:17

Modified files:
	gcc            : ChangeLog tree-ssa-loop-niter.c 
	gcc/testsuite  : ChangeLog 
Added files:
	gcc/testsuite/gcc.c-torture/execute: pr22348.c 

Log message:
	PR tree-optimize/22348
	* tree-ssa-loop-niter.c (number_of_iterations_cond):
	Fold the partial computation.
	
	* gcc.c-torture/execute/pr22348.c: New.

Patches:
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/ChangeLog.diff?cvsroot=gcc&r1=2.9564&r2=2.9565
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/tree-ssa-loop-niter.c.diff?cvsroot=gcc&r1=2.33&r2=2.34
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/testsuite/ChangeLog.diff?cvsroot=gcc&r1=1.5828&r2=1.5829
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/testsuite/gcc.c-torture/execute/pr22348.c.diff?cvsroot=gcc&r1=NONE&r2=1.1



-- 


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


  parent reply	other threads:[~2005-07-27 14:04 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-07 16:58 [Bug c/22348] New: Execution continues past end of for loop end condition with optimisation enabled matt+gccbugs at ucc dot asn dot au
2005-07-07 16:59 ` [Bug c/22348] " matt+gccbugs at ucc dot asn dot au
2005-07-07 17:02 ` matt+gccbugs at ucc dot asn dot au
2005-07-07 17:13 ` [Bug tree-optimization/22348] [4.0 Regression] " pinskia at gcc dot gnu dot org
2005-07-07 17:39 ` [Bug tree-optimization/22348] [4.0/4.1 " pinskia at gcc dot gnu dot org
2005-07-14 20:36 ` [Bug tree-optimization/22348] [4.0/4.1 Regression] IV canonicalization causes execution of loops past their end condition steven at gcc dot gnu dot org
2005-07-14 23:46 ` steven at gcc dot gnu dot org
2005-07-15  0:06 ` steven at gcc dot gnu dot org
2005-07-15  9:58 ` rakdver at gcc dot gnu dot org
2005-07-15 10:26 ` rakdver at gcc dot gnu dot org
2005-07-27 14:06 ` cvs-commit at gcc dot gnu dot org [this message]
2005-07-27 14:27 ` [Bug tree-optimization/22348] [4.0/4.1 Regression] Wrong folding for FLOOR_MOD_EXPR rakdver at gcc dot gnu dot org
2005-07-27 16:37 ` pinskia at gcc dot gnu dot org
2005-07-27 16:39 ` [Bug tree-optimization/22348] [4.0/4.1 Regression] Execution continues past end of for loop end condition with optimisation enabled pinskia at gcc dot gnu dot org
2005-07-27 16:40 ` [Bug tree-optimization/22348] [4.0 " pinskia at gcc dot gnu dot org
2005-07-27 16:45 ` pinskia at gcc dot gnu dot org
2005-08-29 14:58 ` bonzini at gcc dot gnu dot org
2005-08-29 15:26 ` rakdver at gcc dot gnu dot org
2005-09-01 16:09 ` cvs-commit at gcc dot gnu dot org
2005-09-08 10:09 ` cvs-commit at gcc dot gnu dot org
2005-09-08 12:38 ` pinskia 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=20050727140436.20746.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).