[macstl-dev] gcc 3.3 on YellowDogLinux
leblanc at skycomputers.com
Thu Mar 31 00:17:51 WST 2005
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
It's OK by me to use 3.4, but my bosses want to avoid building another
GCC. I'll ask.
On Mar 29, 2005, at 7:43 PM, Glen Low wrote:
> On 28/03/2005, at 11:13 PM, Michael LeBlanc wrote:
>>> Is there any way, perhaps using a command-line switch or equivalent,
>>> to keep the old Motorola style definition of bool?
>> Not that I know of. After including <altivec.h> I can add
>> #undef bool
>> to unhide the reserved word. But that clobbers any legitimate
>> "vector bool ...".
>> This is a problem in GCC < 3.4. In that version, GCC treats vector,
>> bool and pixel as Apple does.
> Ooo... is there any reason you can't use GCC 3.4 on YDL then?
More information about the macstl-dev