diff configure @ 27318:bb5ed9aa34fc

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.

--- a/configure	Fri Jul 25 09:15:08 2008 +0000
+++ b/configure	Sat Jul 26 12:26:04 2008 +0000
@@ -2470,11 +2470,9 @@
     # check if the compiler supports braces for vector declarations
     cat > $TMPC << EOF
 $inc_altivec_h
-#define AVV(x...) {x}
-int main(void) { (vector int) AVV(1); return 0; }
-EOF
-    cc_check $_altivec_gcc_flags &&
-        _def_altivec_vector_braces='#define HAVE_ALTIVEC_VECTOR_BRACES 1'
+int main(void) { (vector int) {1}; return 0; }
+EOF
+    cc_check $_altivec_gcc_flags || die "You need a compiler that supports {} in AltiVec vector declarations."
 
     # Disable runtime cpudetection if we cannot generate AltiVec code or
     # AltiVec is disabled by the user.
@@ -8630,7 +8628,6 @@
 `ff_config_enable "$_cpuexts_all" "$_cpuexts" "HAVE"`
 
 $_def_altivec_h	// enables usage of altivec.h
-$_def_altivec_vector_braces
 
 /* libvo options */
 #define SCREEN_SIZE_X 1