This is the mail archive of the
mailing list for the GCC project.
Re: opaque vector types?
- From: Andrew Pinski <pinskia at gmail dot com>
- To: DJ Delorie <dj at redhat dot com>
- Cc: gcc at gcc dot gnu dot org
- Date: Tue, 5 May 2009 23:11:02 -0700
- Subject: Re: opaque vector types?
- References: <200905060604.n4664Skm024765@greed.delorie.com>
On Tue, May 5, 2009 at 11:04 PM, DJ Delorie <email@example.com> wrote:
> I'm working on a coprocessor which has separate SIMD arithmetic
> operations for each data size, but only one SIMD logical operation for
> all sizes. ÂI.e. there's four ADD insns (V8QI, V4HI, etc) , but only
> one AND insn. ÂI'd like to use an opaque vector type for the AND
> builtin, to avoid warnings.
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.