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/964] missed warning and optimization
Date: Sun, 16 Nov 2003 01:47:00 -0000	[thread overview]
Message-ID: <20031116014714.16190.qmail@sources.redhat.com> (raw)
In-Reply-To: <20001202165600.964.bh@techhouse.brown.edu>


------- Additional Comments From pinskia at gcc dot gnu dot org  2003-11-16 01:47 -------
>From <http://gcc.gnu.org/onlinedocs/gcc/Non-bugs.html#Non-bugs> "Certain Changes We Don't 
Want to Make":
Deleting "empty" loops.

Historically, GCC has not deleted "empty" loops under the assumption that the most likely reason 
you would put one in a program is to have a delay, so deleting them will not make real programs 
run any faster.

However, the rationale here is that optimization of a nonempty loop cannot produce an empty one, 
which holds for C but is not always the case for C++.

Moreover, with -funroll-loops small "empty" loops are already removed, so the current behavior is 
both sub-optimal and inconsistent and will change in the future.


-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|SUSPENDED                   |RESOLVED
         Resolution|                            |INVALID


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


      parent reply	other threads:[~2003-11-16  1:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20001202165600.964.bh@techhouse.brown.edu>
2003-08-17  1:37 ` pinskia at gcc dot gnu dot org
2003-11-16  1:47 ` pinskia at gcc dot gnu dot org [this message]

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=20031116014714.16190.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).