[PATCH, testsuite]: tweak gcc.dg/vmx cases

[Janis Johnson]

On Tue, 2008-04-22 at 11:52 +1000, Ben Elliston wrote:
> On Mon, 2008-04-21 at 18:26 -0700, Andrew Pinski wrote:
> 
> > No, this is incorrect.  The Altivec PIM says:
> > In this method, __vector, __pixel , and bool are added as keywords
> > while vector and pixel are predefined macros. bool is already a
> > keyword in C++. To allow its use in C as a keyword, it is treated
> > the same as it is in C++. This means that the C language is
> > extended to allow bool alone as a set of type specifiers.
> 
> And for the context-sensitive method, it says:
> 
> "Since vector must be first among the type specifiers, it can be
> recognized as a type specifier when a type identifier is being scanned.
> The new uses of pixel and bool occur after vector has been recognized.
> In all other contexts, vector, pixel, and bool are not reserved."
> 
> That is, outside a vector type declaration, "bool" is an identifier and
> not a permitted type of its own.

This isn't a testsuite question, it's a language lawyer question
about AltiVec extensions.  If the extensions really are incompatible
then there should be separate versions of the test.

Janis