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: generic vectors: how should they work?

From: James E Wilson <wilson at specifixinc dot com>
To: David Edelsohn <dje at watson dot ibm dot com>
Cc: Janis Johnson <janis187 at us dot ibm dot com>, gcc at gcc dot gnu dot org
Date: Wed, 01 Sep 2004 14:22:27 -0700
Subject: Re: generic vectors: how should they work?
References: <20040901003511.GA8377@us.ibm.com> <41362D1C.2020906@specifixinc.com> <200409012040.i81KecO30194@makai.watson.ibm.com>

On Wed, 2004-09-01 at 13:40, David Edelsohn wrote:
> 	Honza submitted a patch to implement additional init/set/extract
> expanders, but the second patch never was reviewed.
> http://gcc.gnu.org/ml/gcc-patches/2004-01/msg00050.html

That is an x86 backend patch, which doesn't help a mips user much.  I
was looking for front-end/middle changes to add syntax that would
translate into vec_init/vec_set/vec_extract calls.  We have the
constructor syntax that turns into vec_init, but we have no syntax that
turns into vec_set or vec_extract.
-- 
Jim Wilson, GNU Tools Support, http://www.SpecifixInc.com

References:
- generic vectors: how should they work?
  - From: Janis Johnson
- Re: generic vectors: how should they work?
  - From: James E Wilson
- Re: generic vectors: how should they work?
  - From: David Edelsohn

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