From: Richard Guenther <richard.guenther@gmail.com>
To: Dominique Dhumieres <dominiq@lps.ens.fr>
Cc: gcc@gcc.gnu.org, Albert.Cohen@inria.fr
Subject: Re: complete_unrolli / complete_unroll
Date: Thu, 20 Aug 2009 12:25:00 -0000 [thread overview]
Message-ID: <84fc9c000908200257w3a4515efu718d69ac25749fcb@mail.gmail.com> (raw)
In-Reply-To: <20090820094807.C6A5C3BE85@mailhost.lps.ens.fr>
On Thu, Aug 20, 2009 at 11:48 AM, Dominique Dhumieres<dominiq@lps.ens.fr> wrote:
> IIRC another code that is "improved" by complete_unrolli is the polyhedron
> test induct.f90. However it gives worse results for some variants
> (see pr34265: induct_v2/3).
>
>> Can't we use graphite to re-roll loops? ...
>
> Is doing and undoing always some kind of work?
Yes it is, but you can only reliably find out if unrolling will enable
further optimizations if you do the unrolling. If it didn't enable anything
re-rolling the loop should be possible. And within the polyhedral
representation it should even be easy (I hope).
Richard.
> Cheers
>
> Dominique
>
next prev parent reply other threads:[~2009-08-20 9:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-20 11:20 Dominique Dhumieres
2009-08-20 12:25 ` Richard Guenther [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-08-19 11:53 mips64 gcc 3.3.6 problem Sergey Anosov
2009-08-19 12:13 ` complete_unrolli / complete_unroll Albert Cohen
2009-08-19 12:33 ` Richard Guenther
2009-08-19 12:35 ` Richard Guenther
2009-08-19 13:56 ` Albert Cohen
2009-08-19 14:44 ` Albert Cohen
2009-08-19 15:09 ` Richard Guenther
2009-08-19 20:30 ` Richard Guenther
2009-08-20 8:45 ` Albert Cohen
2009-08-20 9:57 ` Richard Guenther
2009-08-20 13:34 ` Albert Cohen
2009-09-29 18:54 ` David Edelsohn
2009-09-30 12:36 ` Richard Guenther
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=84fc9c000908200257w3a4515efu718d69ac25749fcb@mail.gmail.com \
--to=richard.guenther@gmail.com \
--cc=Albert.Cohen@inria.fr \
--cc=dominiq@lps.ens.fr \
--cc=gcc@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).