public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: jason@gcc.gnu.org
To: agesen@vmware.com, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
	mchen@vmware.com, mendel@vmware.com, nobody@gcc.gnu.org
Subject: Re: optimization/10171: [3.2/3.3/3.4 regression] wrong code for inlined function
Date: Fri, 21 Mar 2003 06:17:00 -0000	[thread overview]
Message-ID: <20030321061728.27452.qmail@sources.redhat.com> (raw)

Synopsis: [3.2/3.3/3.4 regression] wrong code for inlined function

State-Changed-From-To: open->analyzed
State-Changed-By: jason
State-Changed-When: Fri Mar 21 06:17:28 2003
State-Changed-Why:
    This is a bug in loop unrolling; 2.95 shows the bug with
    -funroll-loops.  The only difference is that now we do some
    unrolling at -O2.
    
    The loop optimizer properly calculates that there will
    always be a single pass through the loop.  The unroller
    has a special case for this.  It looks for and deletes an
    unconditional jump to the continue point, then deletes a
    conditional jump from the end of the loop.  Unfortunately,
    this code fails to handle nontrivial for loops, as the
    unconditional jump at the beginning of the loop (created
    previously by loop inversion) is to the test, not to the
    continue point.  So that jump is not deleted, but the
    conditional jump at the end is, and so we just skip over
    the loop.  Oops.

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


             reply	other threads:[~2003-03-21  6:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-21  6:17 jason [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-03-25 21:06 jason
2003-03-22 23:06 Janis Johnson
2003-03-22 22:26 Steven Bosscher
2003-03-22 21:46 Janis Johnson
2003-03-21 23:56 Jason Merrill
2003-03-21 23:36 Steven Bosscher
2003-03-21  6:10 jason
2003-03-20 19:09 bangerth

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=20030321061728.27452.qmail@sources.redhat.com \
    --to=jason@gcc.gnu.org \
    --cc=agesen@vmware.com \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=mchen@vmware.com \
    --cc=mendel@vmware.com \
    --cc=nobody@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).