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: __APPLE_CC__ defined on head of mainline

From: Devang Patel <dpatel at apple dot com>
To: "Timothy J.Wood" <tjw at omnigroup dot com>
Cc: gcc mailing list <gcc at gcc dot gnu dot org>
Date: Fri, 31 Dec 2004 11:09:05 -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>

On Dec 31, 2004, at 12:32 AM, Timothy J.Wood wrote:

OK. I was looking for something to distinguish at compile time whether I'm using FSF GCC (requires <altivec.h>, uses (vector xxx){a,b,c,d} for vector constants) or Apple GCC (doesn't; uses (vector xxx)(a,b,c,d)). I guess I'll keep looking.

Try __APPLE_ALTIVEC__

-
Devang

References:
- __APPLE_CC__ defined on head of mainline
  - From: Timothy J . Wood
- Re: __APPLE_CC__ defined on head of mainline
  - From: Andrew Pinski
- Re: __APPLE_CC__ defined on head of mainline
  - From: Timothy J . Wood

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