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/40087] [4.3/4.4/4.5 Regression] Number of iterations analysis wrong
Date: Sun, 10 May 2009 09:53:00 -0000 [thread overview]
Message-ID: <20090510095251.24327.qmail@sourceware.org> (raw)
In-Reply-To: <bug-40087-17694@http.gcc.gnu.org/bugzilla/>
------- Comment #5 from rguenth at gcc dot gnu dot org 2009-05-10 09:52 -------
It is number of iteration analysis that gets it wrong (I suppose it might get
confused by the two exits of the loop?).
Disabling loop header copying makes the code easier to analyze.
--
rguenth at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |rakdver at gcc dot gnu dot
| |org
Keywords| |wrong-code
Summary|Bad assembly for -O2 |[4.3/4.4/4.5 Regression]
| |Number of iterations
| |analysis wrong
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40087
next prev parent reply other threads:[~2009-05-10 9:53 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-10 1:39 [Bug c/40087] New: Bad assembly for -O2 markus at cs dot wisc dot edu
2009-05-10 1:41 ` [Bug c/40087] " markus at cs dot wisc dot edu
2009-05-10 1:44 ` markus at cs dot wisc dot edu
2009-05-10 1:48 ` markus at cs dot wisc dot edu
2009-05-10 9:42 ` [Bug tree-optimization/40087] " rguenth at gcc dot gnu dot org
2009-05-10 9:53 ` rguenth at gcc dot gnu dot org [this message]
2009-05-10 12:59 ` [Bug tree-optimization/40087] [4.3/4.4/4.5 Regression] Number of iterations analysis wrong rakdver at gcc dot gnu dot org
2009-05-15 0:34 ` rakdver at gcc dot gnu dot org
2009-05-15 8:44 ` rguenther at suse dot de
2009-05-15 15:45 ` rakdver at kam dot mff dot cuni dot cz
2009-05-20 0:34 ` rakdver at gcc dot gnu dot org
2009-05-20 9:21 ` [Bug tree-optimization/40087] [4.3/4.4 " rguenth at gcc dot gnu dot org
2009-05-21 11:37 ` rguenth at gcc dot gnu dot org
2009-05-22 20:44 ` rakdver at gcc dot gnu dot org
2009-05-23 9:15 ` [Bug tree-optimization/40087] [4.3 " rguenth at gcc dot gnu dot org
2009-06-15 10:10 ` cnstar9988 at gmail dot com
2009-06-15 14:24 ` mikpe at it dot uu dot se
2009-06-17 15:12 ` rguenth at gcc dot gnu dot org
2009-06-17 19:46 ` rguenth at gcc dot gnu dot org
2009-06-17 19:46 ` rguenth at gcc dot gnu dot org
2009-06-17 19:49 ` 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=20090510095251.24327.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).