diff options
author | Diego Biurrun <diego@biurrun.de> | 2008-07-24 10:53:32 +0000 |
---|---|---|
committer | Diego Biurrun <diego@biurrun.de> | 2008-07-24 10:53:32 +0000 |
commit | 80a61f08d2d6059b0aaffa4c8b8120fb0ab0ca75 (patch) | |
tree | 4567552fff1cba203b754fc790485d702414a687 /configure | |
parent | ec072669f7398f40d8001c8cb0868880569c6cd9 (diff) | |
download | ffmpeg-80a61f08d2d6059b0aaffa4c8b8120fb0ab0ca75.tar.gz |
Remove AltiVec vector declaration compiler compatibility macros.
The original problem was that FSF and Apple gcc used a different syntax
for vector declarations, i.e. {} vs. (). Nowadays Apple gcc versions support
the standard {} syntax and versions that support {} are available on all
relevant Mac OS X versions. Thus the greater compatibility is no longer
worth cluttering the code with macros.
Originally committed as revision 14366 to svn://svn.ffmpeg.org/ffmpeg/trunk
Diffstat (limited to 'configure')
-rwxr-xr-x | configure | 6 |
1 files changed, 2 insertions, 4 deletions
@@ -725,7 +725,6 @@ HAVE_LIST=" $ARCH_EXT_LIST $THREADS_LIST altivec_h - altivec_vector_braces arpa_inet_h bswap byteswap_h @@ -1567,10 +1566,9 @@ int main(void) { EOF # check if our compiler supports braces for vector declarations - check_cc <<EOF && enable altivec_vector_braces + check_cc <<EOF || die "You need a compiler that supports {} in AltiVec vector declarations." $inc_altivec_h -#define AVV(x...) {x} -int main (void) { (vector int) AVV(1); return 0; } +int main (void) { (vector int) {1}; return 0; } EOF fi |