public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug optimization/13835] [tree-ssa] Several loops detected instead of a single one
Date: Tue, 16 Mar 2004 00:21:00 -0000	[thread overview]
Message-ID: <20040316002137.14973.qmail@sources.redhat.com> (raw)
In-Reply-To: <20040123181835.13835.spop@gcc.gnu.org>


------- Additional Comments From pinskia at gcc dot gnu dot org  2004-03-16 00:21 -------
Actually it has nothing to do with the header at all.
The issue is more that DOM created two loops as it dected a >=29, a is always positive 
as b and c will always be positive.  This is not true for -fwrapv but that is off by default for 
C.
I do not see this as wrong code because there is too loops and DOM is right here.  The 
real problem is that the two loops are independent but loop dectection is not decting 
them.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|critical                    |normal
           Keywords|memory-hog                  |
   Target Milestone|tree-ssa                    |lno


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


  parent reply	other threads:[~2004-03-16  0:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-23 18:18 [Bug optimization/13835] New: " spop at gcc dot gnu dot org
2004-01-23 23:16 ` [Bug optimization/13835] " pinskia at gcc dot gnu dot org
2004-01-24  3:37 ` pinskia at gcc dot gnu dot org
2004-03-07  9:28 ` pinskia at gcc dot gnu dot org
2004-03-16  0:21 ` pinskia at gcc dot gnu dot org [this message]
2004-08-12  6:43 ` [Bug tree-optimization/13835] " 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=20040316002137.14973.qmail@sources.redhat.com \
    --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).