public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Albert Cohen <Albert.Cohen@inria.fr>
To: Richard Guenther <richard.guenther@gmail.com>
Cc: gcc@gcc.gnu.org
Subject: Re: complete_unrolli / complete_unroll
Date: Wed, 19 Aug 2009 14:44:00 -0000	[thread overview]
Message-ID: <4A8C0405.9030008@inria.fr> (raw)
In-Reply-To: <4A8BFF5F.5070708@inria.fr>

Albert Cohen wrote:
> Thanks a lot for the quick and detailed response.
> 
> It is more difficult than I thought, then :-( We'll think more, and
> maybe come up with yet another pass ordering proposal, but definitely
> this tramp3d code deserves to be processed by graphite AFTER
> unrolling+cse has done its specialization trick.

One way out would be to make unrolli pass a little more careful. As you
suggest, the heuristic is already not quite satisfactory as it sometimes
unrolls outemost loops.

A better heursitic would be to run through the different cases where
unrolling helps specialization (e.g., the subscripts of subscripts in
the tramp3d example), and check for these patterns explicitely. But this
is not easy to implement (or to make it robust, and not too
syntax-dependent).

Albert

  reply	other threads:[~2009-08-19 13:54 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-19 11:53 mips64 gcc 3.3.6 problem Sergey Anosov
2009-08-19 11:55 ` Paolo Carlini
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 [this message]
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
2009-08-20 11:20 Dominique Dhumieres
2009-08-20 12:25 ` 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=4A8C0405.9030008@inria.fr \
    --to=albert.cohen@inria.fr \
    --cc=gcc@gcc.gnu.org \
    --cc=richard.guenther@gmail.com \
    /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).