public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: rth@gcc.gnu.org
To: gcc-bugs@gcc.gnu.org, gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org,
	nobody@gcc.gnu.org, ottoni@ic.unicamp.br
Subject: Re: optimization/4919: gcse inhibits loop optimization
Date: Wed, 21 Nov 2001 03:36:00 -0000	[thread overview]
Message-ID: <20011127070349.25276.qmail@sourceware.cygnus.com> (raw)

Synopsis: gcse inhibits loop optimization

State-Changed-From-To: open->suspended
State-Changed-By: rth
State-Changed-When: Mon Nov 26 23:03:48 2001
State-Changed-Why:
    GCSE did exactly what it was supposed to do -- the expression
    I+1, which appears twice in the body of the loop, is partially
    redundant with the increment of I at the end of the loop.
    
    This isn't really a problem with GCSE, but with the extreme lameness
    of our loop optimizer.  Hopefully we'll have time to rewrite it from
    scratch for gcc 3.2; Jan Hubicka has already volunteered to try.
    
    

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=4919&database=gcc


             reply	other threads:[~2001-11-27  7:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-21  3:36 rth [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-11-21  3:43 rth
2001-11-16 23:39 ottoni

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=20011127070349.25276.qmail@sourceware.cygnus.com \
    --to=rth@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@gcc.gnu.org \
    --cc=ottoni@ic.unicamp.br \
    /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).