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: Timothy J.Wood <tjw at omnigroup dot com>
To: Andrew Pinski <pinskia at physics dot uc dot edu>
Cc: gcc at gcc dot gnu dot org
Date: Fri, 31 Dec 2004 00:32:41 -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>

On Dec 30, 2004, at 8:52 PM, Andrew Pinski wrote:

No it did not accidentally get defined in the FSF's sources.

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.

Didn't I also close a bug about this before from you?

Woops; I hope not -- if so I apologize for forgetting about the issue.

-tim

Follow-Ups:
- Re: __APPLE_CC__ defined on head of mainline
  - From: Devang Patel

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

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