[Mesa-dev] [PATCH] clover: work around altivec build failure with GNU C++ and -std=c++

[Chí-Thanh Christopher Nguyễn]

Francisco Jerez schrieb:
> Chí-Thanh Christopher Nguyễn <chithanh at gentoo.org> writes:
> 
>> Chí-Thanh Christopher Nguyễn schrieb:
>>>> How about disabling AltiVec code generation by adding
>>>> "-mno-altivec" to CXXFLAGS?  AFAICT what's going on is that the
>>>> "-maltivec" option (which is implied by your "-mcpu=7450") enables
>>>> a number of language extensions as a side effect that collide with
>>>> the C++ standard, which is exacerbated by GCC's seemingly broken
>>>> implementation.
>> 
>> Ah, and one potential issue I didn't think of yet is that -mno-altivec
>> also implies -mabi=no-altivec and I am unsure if this can lead to
>> problems if altivec ABI is enabled for the rest of the build.
>> 
> Aren't both options orthogonal?  It seems like you can enable the 
> AltiVec ABI without getting the annoying language extensions by doing 
> "-mno-altivec -mabi=altivec".

Yes, but how are we going to find out whether we need to pass -mabi=altivec
or not? Certain values for -mcpu imply -maltivec and -mabi=altivec, while
others don't.
(That is assuming mixing -mabi=altivec and -mabi=no-altivec can cause
problems, which I have no idea at all about.)


Best regards,
Chí-Thanh Christopher Nguyễn