On Fri, May 30, 2008 at 02:29:43PM +0200, Diego Biurrun wrote:
> Here is a patch to handle AltiVec vector declaration syntax in a
> slightly better way. Yes, this reverts a patch I sent earlier :)
>
> Apple's gcc accepts vector declarations with () instead of {} like the
> FSF gcc. Newer variants of the Apple compiler understand {} as well and
> complain about () when compiling with -maltivec, which is the portable
> and thus preferred flag. Thus {} should be used where possible.
>
> AFAIK altivec.h is always necessary when compiling with -maltivec, thus
> checking for ALTIVEC_H is better than __APPLE_CC__.
>
> A cleaner solution would be to have a small test program in configure
> like
>
> #include <altivec.h>
> #define AVV(x...) {x}
> int main (void) { (vector int) AVV(1); return 0; }
>
> and if it compiles successfully, set a HAVE_ALTIVEC_VECTOR_BRACES to 1
> in config.h. I have done this for FFmpeg and MPlayer, but I have to
> admit I do not know how to hack this into your autoconf scripts.
>
> In the meantime, my proposed patch should be a rather reasonable
> workaround.
.. ping ..
Diego
-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
Libmpeg2-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/libmpeg2-devel
