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/26900] Number of iterations not know for simple loop
Date: Tue, 28 Mar 2006 15:13:00 -0000	[thread overview]
Message-ID: <20060328151343.5849.qmail@sourceware.org> (raw)
In-Reply-To: <bug-26900-10053@http.gcc.gnu.org/bugzilla/>



------- Comment #1 from rguenth at gcc dot gnu dot org  2006-03-28 15:13 -------
Note that we in principle know the number of iterations - just we cannot prove
the loop runs at least once in number of iterations analysis.  Of course we
know this because we did loop header copying on the loop and no other pass
interfered with this.  Maybe we should remember the BB of the loop header copy
so we can verify
later that it still dominates the loop header.  This would avoid needing to
deal
with symbolic range simplification like in PR26899.


-- 

rguenth at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |sebastian dot pop at cri dot
                   |                            |ensmp dot fr


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


  reply	other threads:[~2006-03-28 15:13 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-28 14:22 [Bug middle-end/26900] New: " rguenth at gcc dot gnu dot org
2006-03-28 15:13 ` rguenth at gcc dot gnu dot org [this message]
2006-03-28 15:14 ` [Bug middle-end/26900] " rguenth at gcc dot gnu dot org
2006-03-28 15:16 ` rguenth at gcc dot gnu dot org
2006-03-29  1:03 ` rakdver at gcc dot gnu dot org
2006-03-29  1:14 ` pinskia at gcc dot gnu dot org
2006-03-29  8:01 ` rguenth at gcc dot gnu dot org
2006-03-29  9:01 ` rakdver at atrey dot karlin dot mff dot cuni dot cz
2006-03-29  9:11 ` rakdver at atrey dot karlin dot mff dot cuni dot cz
2006-03-29 15:45 ` rguenth at gcc dot gnu dot org
2006-03-30  9:15 ` patchapp at dberlin dot org
2006-04-02 16:04 ` rakdver at gcc dot gnu dot org
2006-06-19  8:11 ` sebastian dot pop at cri dot ensmp dot fr
2006-06-19  9:29 ` rguenth at gcc dot gnu dot org
2006-10-28 18:23 ` rguenth at gcc dot gnu dot org
2007-01-24 14:59 ` rguenth at gcc dot gnu dot org
2007-02-10 20:07 ` rakdver at gcc dot gnu dot org
2007-03-14  0:39 ` rakdver at gcc dot gnu dot org
2007-07-10  8:30 ` 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=20060328151343.5849.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).