This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: altivec: fix macros
- From: Daniel Jacobowitz <drow at mvista dot com>
- To: gcc-patches at gcc dot gnu dot org
- Date: Tue, 16 Apr 2002 22:16:38 -0400
- Subject: Re: altivec: fix macros
- References: <20020417030900.GA3832@redhat.com>
On Wed, Apr 17, 2002 at 10:09:00AM +0700, Aldy Hernandez wrote:
> Index: config/rs6000/altivec.h
> ===================================================================
> RCS file: /cvs/uberbaum/gcc/config/rs6000/altivec.h,v
> retrieving revision 1.13
> diff -c -p -r1.13 altivec.h
> *** config/rs6000/altivec.h 16 Apr 2002 06:40:40 -0000 1.13
> --- config/rs6000/altivec.h 17 Apr 2002 01:59:23 -0000
> *************** Boston, MA 02111-1307, USA. */
> *** 35,48 ****
> --- 35,52 ----
> /* Required by Motorola specs. */
> #define __VEC__ 10206
>
> + #ifndef __ALTIVEC__
> #define __ALTIVEC__ 1
> + #endif
>
> #define __vector __attribute__((vector_size(16)))
>
> /* You are allowed to undef this for C++ compatability. */
> #define vector __vector
>
> + #define bool unsigned
I know Altivec is already grossly in the user's namespace, but is it
really necessary to #define bool? Could you at least get away with
including <stdbool.h>?
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer