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

[Francisco Jerez]

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".

>
> Best regards,
> Chí-Thanh Christopher Nguyễn
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 229 bytes
Desc: not available
URL: <http://lists.freedesktop.org/archives/mesa-dev/attachments/20130826/a34801b1/attachment.pgp>