This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: auto vectorization in gcc

From: Daniel Berlin <dberlin at dberlin dot org>
To: Richard Henderson <rth at redhat dot com>
Cc: Dorit Naishlos <DORIT at il dot ibm dot com>,gcc at gcc dot gnu dot org,Diego Novillo <dnovillo at redhat dot com>,dje at watson dot ibm dot com
Date: Thu, 17 Jul 2003 14:09:35 -0400
Subject: Re: auto vectorization in gcc
References: <OF129DBCCF.99C6474B-ONC2256D66.004608FF-C2256D66.00461C31@telaviv.ibm.com> <20030717174805.GB10554@redhat.com>

On Thursday, July 17, 2003, at 1:48 PM, Richard Henderson wrote:

On Thu, Jul 17, 2003 at 03:45:47PM +0300, Dorit Naishlos wrote:

(c) since the tree-level is machine independent, actual vectorization
    will take place in the RTL level


I would think this would be false.  Just because the tree level
representation is machine independent doesn't mean we can't do
any target-specific transformations.

The tree level is *more* capable than the rtl level at representing
vector types (and thus operations).  I think all we need is some
small amount of info from the target about vector widths and memory
blocking, and then the transformation should happen at the tree level.

I agree completely. Especially since it's a matter of just making tree nodes with a vector type, and performing standard tree ops on them.

IE PLUS_EXPR of two trees with types of V4SF_type_node should work just fine, and convert to the right vector RTL.

If it doesn't, we should make it work.

r~

Follow-Ups:
- Re: auto vectorization in gcc
  - From: David Edelsohn

References:
- auto vectorization in gcc
  - From: Dorit Naishlos
- Re: auto vectorization in gcc
  - From: Richard Henderson

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]