public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rakdver at atrey dot karlin dot mff dot cuni dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/22041] Reverse loop order for increased efficiency
Date: Sun, 28 May 2006 14:25:00 -0000 [thread overview]
Message-ID: <20060528142500.18409.qmail@sourceware.org> (raw)
In-Reply-To: <bug-22041-10391@http.gcc.gnu.org/bugzilla/>
------- Comment #5 from rakdver at atrey dot karlin dot mff dot cuni dot cz 2006-05-28 14:25 -------
Subject: Re: Reverse loop order for increased efficiency
> ------- Comment #4 from tkoenig at gcc dot gnu dot org 2006-05-28 14:10 -------
> (In reply to comment #3)
> > Dunno if tree loop reversal is already there, but Zdenek probably likes to know
> > what bugs he is fixing...
>
> Loop reversal doesn't occur yet.
>
> gcc version 4.2.0 20060521 (experimental) gives us:
>
> L4:
> movl (%ecx), %eax
> addl $1, %ebx
> addl %edi, %ecx
> movl %eax, (%edx)
> addl %esi, %edx
> cmpl 16(%ebp), %ebx
> jne L4
loop reversal was removed with the old loop optimizer; the tree level
loop reversal patch
(http://gcc.gnu.org/ml/gcc-patches/2006-01/msg01851.html) was not
reviewed.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22041
next prev parent reply other threads:[~2006-05-28 14:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-22041-10391@http.gcc.gnu.org/bugzilla/>
2006-02-27 14:06 ` steven at gcc dot gnu dot org
2006-05-28 14:10 ` tkoenig at gcc dot gnu dot org
2006-05-28 14:25 ` rakdver at atrey dot karlin dot mff dot cuni dot cz [this message]
2006-06-05 21:36 ` tkoenig at gcc dot gnu dot org
[not found] <bug-22041-4@http.gcc.gnu.org/bugzilla/>
2010-12-30 12:29 ` tkoenig at gcc dot gnu.org
2013-03-17 17:13 ` tkoenig at gcc dot gnu.org
2021-03-03 18:47 ` pinskia at gcc dot gnu.org
2005-06-12 20:57 [Bug tree-optimization/22041] New: " tkoenig at gcc dot gnu dot org
2005-06-12 23:44 ` [Bug tree-optimization/22041] " pinskia at gcc dot gnu dot org
2005-07-07 23:42 ` 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=20060528142500.18409.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).