[macstl-dev] gcc 3.3 on YellowDogLinux
glen.low at pixelglow.com
Fri Apr 1 21:04:58 WST 2005
On 31/03/2005, at 12:17 AM, Michael LeBlanc wrote:
> Well, not exactly like Apple. In <altivec.h> they replaced all
> "vector" by "__vector", "bool" by "__bool", and "pixel" by "__pixel".
> The "__" words are reserved. If you #define __APPLE_ALTIVEC__, they
> #define vector __vector
> #define bool __bool
> #define pixel __pixel
> but we don't want to do that, at least for bool. However, in Altivec
> code, you have to write
> __vector __bool char
That seems to work OK with Apple gcc 3.3 as well, and I'm happier
seeing __bool in code rather than worrying whether the C++ parser would
mistake a bool in that context to be a C++ bool.
We'll have to change all the vector bool and pixel to __bool and
__pixel respectively (no fence required).
> It's OK by me to use 3.4, but my bosses want to avoid building another
> GCC. I'll ask.
Is this work for your company, SkyComputers? Embedded processors?
Cheers, Glen Low
pixelglow software | simply brilliant stuff
More information about the macstl-dev