This is the mail archive of the gcc-patches@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: [patch] detect invalid altivec data types

From: Janis Johnson <janis187 at us dot ibm dot com>
To: "Joseph S. Myers" <joseph at codesourcery dot com>
Cc: Janis Johnson <janis187 at us dot ibm dot com>, gcc-patches at gcc dot gnu dot org, uttamp at us dot ibm dot com
Date: Tue, 30 Nov 2004 13:14:04 -0800
Subject: Re: [patch] detect invalid altivec data types
References: <20041123234037.GA7724@us.ibm.com> <Pine.LNX.4.61.0411240009340.9421@digraph.polyomino.org.uk> <20041130204640.GA6029@us.ibm.com> <Pine.LNX.4.61.0411302053300.32288@digraph.polyomino.org.uk>

On Tue, Nov 30, 2004 at 08:54:29PM +0000, Joseph S. Myers wrote:
> On Tue, 30 Nov 2004, Janis Johnson wrote:
> 
> > +__vector Complex int vci;		/* { dg-error "error" "" } */
> 
> Should be _Complex or __complex__ not Complex.

<sigh>.  I fixed the tests, but now see that we don't catch
"vector _Complex int".

Janis

References:
- [patch] detect invalid altivec data types
  - From: Janis Johnson
- Re: [patch] detect invalid altivec data types
  - From: Joseph S. Myers
- Re: [patch] detect invalid altivec data types
  - From: Janis Johnson
- Re: [patch] detect invalid altivec data types
  - From: Joseph S. Myers

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