From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-return-153742-listarch-gcc=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 27052 invoked by alias); 6 May 2009 09:08:24 -0000
Received: (qmail 27041 invoked by uid 22791); 6 May 2009 09:08:22 -0000
X-SWARE-Spam-Status: No, hits=-2.1 required=5.0 	tests=AWL,BAYES_00,RCVD_IN_SORBS_WEB,SPF_PASS
X-Spam-Check-By: sourceware.org
Received: from mail-ew0-f157.google.com (HELO mail-ew0-f157.google.com) (209.85.219.157)     by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 06 May 2009 09:08:18 +0000
Received: by ewy1 with SMTP id 1so5642115ewy.8         for <gcc@gcc.gnu.org>; Wed, 06 May 2009 02:08:15 -0700 (PDT)
Received: by 10.210.10.8 with SMTP id 8mr4101055ebj.99.1241600895545;         Wed, 06 May 2009 02:08:15 -0700 (PDT)
Received: from scientist-2.mobile.usilu.net ([195.176.179.202])         by mx.google.com with ESMTPS id 28sm1263790eyg.4.2009.05.06.02.08.13         (version=TLSv1/SSLv3 cipher=RC4-MD5);         Wed, 06 May 2009 02:08:13 -0700 (PDT)
Message-ID: <4A01537D.5030405@gnu.org>
Date: Wed, 06 May 2009 09:08:00 -0000
From: Paolo Bonzini <bonzini@gnu.org>
User-Agent: Thunderbird 2.0.0.21 (Macintosh/20090302)
MIME-Version: 1.0
To: DJ Delorie <dj@redhat.com>
CC: Andrew Pinski <pinskia@gmail.com>, gcc@gcc.gnu.org
Subject: Re: opaque vector types?
References: <200905060604.n4664Skm024765@greed.delorie.com> 	<de8d50360905052311g670513b3l6d51c8ed4c6b03f9@mail.gmail.com> <xnmy9qvj51.fsf@greed.delorie.com>
In-Reply-To: <xnmy9qvj51.fsf@greed.delorie.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc/>
List-Post: <mailto:gcc@gcc.gnu.org>
List-Help: <http://gcc.gnu.org/ml/>
Sender: gcc-owner@gcc.gnu.org
X-SW-Source: 2009-05/txt/msg00109.txt.bz2

DJ Delorie wrote:
> Andrew Pinski <pinskia@gmail.com> writes:
>> You could do what the rs6000 back-end does for the altivec builtins
>> and resolve them while the parser is run (the SPU back-end does the
>> same thing too).  Yes there are opaque vector types, you just use
>> build_opaque_vector_type instead of build_vector_type.
> 
> Thanks, I'll look at those.  Any way to prototype such functions in C ?

If the opaque vector type is exported as say __v4si_opaque__ that would
be simply

extern __v4si_opaque__ my_and (__v4si_opaque__, __v4si_opaque__);

Opaque vector types are not available via attributes, but that could be
easily added.

Paolo