public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dberlin at dberlin dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/23361] Can't eliminate empty loops with power of two step and variable bounds
Date: Fri, 12 Aug 2005 23:43:00 -0000	[thread overview]
Message-ID: <20050812234335.7278.qmail@sourceware.org> (raw)
In-Reply-To: <20050812185248.23361.chris@bubblescope.net>


------- Additional Comments From dberlin at gcc dot gnu dot org  2005-08-12 23:43 -------
Subject: Re:  Can't eliminate empty loops with
	power of two step and variable bounds

On Fri, 2005-08-12 at 19:10 +0000, pinskia at gcc dot gnu dot org wrote:
> ------- Additional Comments From pinskia at gcc dot gnu dot org  2005-08-12 19:10 -------

Personally, i think -funsafe-loop-optimizations should be on by default
in -O3, with a warning for when we rely on it.

It's *incredibly* rare that a user actually intends for a loop counter
to be able to overflow.




-- 


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


  parent reply	other threads:[~2005-08-12 23:43 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-12 18:52 [Bug rtl-optimization/23361] New: " chris at bubblescope dot net
2005-08-12 18:57 ` [Bug tree-optimization/23361] " pinskia at gcc dot gnu dot org
2005-08-12 18:58 ` chris at bubblescope dot net
2005-08-12 19:10 ` pinskia at gcc dot gnu dot org
2005-08-12 23:43   ` Daniel Berlin
2005-08-12 23:43 ` dberlin at dberlin dot org [this message]
2005-08-13 10:01 ` giovannibajo at libero dot it
2005-09-15 13:46 ` bonzini at gcc dot gnu dot org
2005-09-15 14:02 ` chris at bubblescope dot net
     [not found] <bug-23361-9525@http.gcc.gnu.org/bugzilla/>
2005-11-09  3:09 ` pinskia at gcc dot gnu dot org
2007-02-05 18:53 ` pcarlini at suse dot de
2007-02-05 21:45 ` rakdver at gcc dot gnu dot org
2007-02-08 14:38 ` rakdver at gcc dot gnu dot org
2007-02-09 13:29 ` rguenth at gcc dot gnu dot org
2007-02-09 14:19 ` 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=20050812234335.7278.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).