Module: libav Branch: release/0.8 Commit: 29a2fdb184b13efb7007d4b631cae2c35001c509
Author: Mans Rullgard <[email protected]> Committer: Reinhard Tartler <[email protected]> Date: Thu Aug 16 00:10:33 2012 +0100 configure: clean up Altivec detection There used to be one test for Altivec intrinsics support and a separate test to determine which of two possible syntaxes to use for vector literals. Since 2008, we only support the more common of these so the split test no longer makes sense. This combines the tests into one and also changes the hard error on failure to a warning. The test can reasonably fail if no --cpu flag is provided (or is provided with an unknown CPU) and the compiler default target does not support Altivec. Aborting in this case is probably over-reacting. Fixes: #464, http://bugs.debian.org/701710 Signed-off-by: Mans Rullgard <[email protected]> (cherry picked from commit 20bcce507aa6b9c866e34eee75d80305109767a8) Signed-off-by: Reinhard Tartler <[email protected]> --- configure | 11 ++++------- 1 files changed, 4 insertions(+), 7 deletions(-) diff --git a/configure b/configure index 2d17ce0..081854f 100755 --- a/configure +++ b/configure @@ -2723,17 +2723,14 @@ elif enabled ppc; then check_cc <<EOF || disable altivec $inc_altivec_h int main(void) { - vector signed int v1, v2, v3; - v1 = vec_add(v2,v3); + vector signed int v1 = (vector signed int) { 0 }; + vector signed int v2 = (vector signed int) { 1 }; + v1 = vec_add(v1, v2); return 0; } EOF - # check if our compiler supports braces for vector declarations - check_cc <<EOF || die "You need a compiler that supports {} in AltiVec vector declarations." -$inc_altivec_h -int main (void) { (vector int) {1}; return 0; } -EOF + enabled altivec || warn "Altivec disabled, possibly missing --cpu flag" fi elif enabled sparc; then _______________________________________________ libav-commits mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-commits
