This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: __APPLE_CC__ defined on head of mainline
- From: Timothy J.Wood <tjw at omnigroup dot com>
- To: Devang Patel <dpatel at apple dot com>
- Cc: gcc mailing list <gcc at gcc dot gnu dot org>
- Date: Sat, 1 Jan 2005 19:22:48 -0800
- Subject: Re: __APPLE_CC__ defined on head of mainline
- References: <637591E2-5ADF-11D9-A009-000D93361BA8@omnigroup.com> <BDF110A8-5AE7-11D9-8F73-000A95D692F4@physics.uc.edu> <895DD288-5B06-11D9-A009-000D93361BA8@omnigroup.com> <70CF5534-5B5F-11D9-880C-000393A91CAA@apple.com>
On Dec 31, 2004, at 11:09 AM, Devang Patel wrote:
Try __APPLE_ALTIVEC__
Apple's compiler doesn't seem to define this macro:
% touch /tmp/foo.c; cc -faltivec -dM -E /tmp/foo.c | grep ALTIVEC
#define __ALTIVEC__ 1
% uname -a
Darwin tjw 7.7.0 Darwin Kernel Version 7.7.0: Sun Nov 7 16:06:51 PST
2004; root:xnu/xnu-517.9.5.obj~1/RELEASE_PPC Power Macintosh powerpc
The FSF sources mention it only as:
./gcc/config/rs6000/altivec.h:/* If __APPLE_ALTIVEC__ is defined, the
compiler supports 'vector',
./gcc/config/rs6000/altivec.h:#if !defined(__APPLE_ALTIVEC__)
So, my search for a way to determine the correct vector syntax at
compile time continues.
-tim