public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Diego Novillo <dnovillo@redhat.com>
To: Toon Moene <toon@moene.indiv.nluug.nl>
Cc: David Edelsohn <dje@watson.ibm.com>,
	Richard Henderson <rth@redhat.com>,
	Daniel Berlin <dan@cgsoftware.com>, Daniel Egger <degger@fhm.edu>,
	gcc-patches@gcc.gnu.org, gcc@gcc.gnu.org
Subject: Re: A bit of vector extension documentation
Date: Fri, 28 Sep 2001 12:45:00 -0000	[thread overview]
Message-ID: <20010928154512.C11185@tornado.cygnus.com> (raw)
In-Reply-To: <3BB4CB8E.DF6B40F4@moene.indiv.nluug.nl>

On Fri, 28 Sep 2001, Toon Moene wrote:

> Diego Novillo wrote:
> 
> > On Fri, 28 Sep 2001, David Edelsohn wrote:
> 
> > >       I thought the point of the paper is that it is a generalization
> > > that does not require loops.  For SIMD, as opposed to vector,
> > > architectures, it might be better because it can take advantage of such
> > > instructions without the loop setup overhead.
> > >
> > Yes, the paper does not attempt to design a vectorizing compiler.
> > It merely points out that in several cases you can get away with
> > converting sequence of expressions into SIMD instructions.  They
> > do have the limitation of working on single basic blocks, though.
> 
> Hmmm, wouldn't that already help on most of the interesting Fortran
> loops, when unrolled (i.e., when "converting sequences of expressions
> into SIMD instructions" is performed after loop unrolling) ?
> 
Oh, most definitely.  It was just an observation of an obvious
extension to their work.  If the analysis is globalized you can
minimize the overhead of packing/unpacking the vector instructions
at block boundaries (if you can re-use a previous packing, for
instance).

The ideas in the paper are certainly interesting and I think
could be put to very good use in GCC.

Diego.

  reply	other threads:[~2001-09-28 12:45 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.BSF.4.33.0109271622590.737-100000@naos.dbai.tuwien.ac.at>
2001-09-27  8:06 ` Bernd Schmidt
2001-09-27  8:24   ` Jan Hubicka
2001-09-27  8:45     ` Bernd Schmidt
2001-09-27  8:32   ` Gerald Pfeifer
2001-09-27  9:04   ` Matt Kraai
2001-09-27 11:34   ` Daniel Jacobowitz
2001-09-27 12:33   ` Richard Henderson
2001-09-27 12:37     ` Bernd Schmidt
2001-09-27 12:44       ` Richard Henderson
2001-09-27 12:45         ` Bernd Schmidt
2001-09-28  0:05   ` Daniel Egger
2001-09-28  0:39     ` Richard Henderson
2001-09-28  0:59       ` Daniel Egger
2001-09-28  1:32         ` Richard Henderson
2001-09-28  1:56           ` Daniel Egger
2001-09-28  8:48           ` Daniel Berlin
2001-09-28  9:38             ` Richard Henderson
2001-09-28 10:13               ` David Edelsohn
2001-09-28 10:25                 ` Diego Novillo
2001-09-28 12:11                   ` Toon Moene
2001-09-28 12:45                     ` Diego Novillo [this message]
2001-09-28 13:21                     ` Tim Prince
2001-09-29 14:33                       ` Aldy Hernandez
2001-09-28 15:37                   ` Daniel Berlin
2001-09-29 17:11               ` Daniel Berlin
2001-09-29 19:37                 ` Richard Henderson

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=20010928154512.C11185@tornado.cygnus.com \
    --to=dnovillo@redhat.com \
    --cc=dan@cgsoftware.com \
    --cc=degger@fhm.edu \
    --cc=dje@watson.ibm.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gcc@gcc.gnu.org \
    --cc=rth@redhat.com \
    --cc=toon@moene.indiv.nluug.nl \
    /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).