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: altivec questions

From: Segher Boessenkool <segher at kernel dot crashing dot org>
To: Janis Johnson <janis187 at us dot ibm dot com>
Cc: gcc at gcc dot gnu dot org, zlaski at apple dot com, aldyh at redhat dot com
Date: Wed, 30 Jun 2004 18:08:41 +0200
Subject: Re: altivec questions
References: <20040629205816.GA6614@us.ibm.com>

   Use of "vector signed long" and "vector unsigned long" isn't
   documented, but GCC gives "warning: use of 'long' in AltiVec types
   is deprecated; use 'int'".  These ought to be hard errors for -m64,
   right?

Yes.

   Several tests pass 'long *' or 'unsigned long *' in places where the
   Motorola AltiVec PIM does not include those types among the
   acceptable arguments.  GCC doesn't complain for either -m32 or -m64.
   These ought to be errors for -m64, right?  Should GCC's altivec.h
   support the ones that are used in the gcc.dg/vmx tests?

The tests should be fixed.

Segher

References:
- altivec questions
  - From: Janis Johnson

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