Correct an Altivec configure think-o.

An earlier change introduced a think-o in the altivec capability
check, allowing a false positive if the compiler supported altivec
but the hardware did not.

Resolves bug #368412 - False positive result for altivec capability check
Patch by Will Schmidt <will_schmidt@vnet.ibm.com>

git-svn-id: svn://svn.valgrind.org/valgrind/trunk@15952

diff --git a/NEWS b/NEWS
index 09af2b9f163df21d54e77c3e482d97a72961f0bd..5b324becca557d295b6678635cb2f939420dea61 100644 (file)
--- a/NEWS
+++ b/NEWS
@@ -155,6 +155,7 @@ where XXXXXX is the bug number as listed below.
 363858  Valgrind does not support the IBM POWER ISA 3.0 instructions, part 4/5
 364948  Valgrind does not support the IBM POWER ISA 3.0 instructions, part 5/5
 366138  Fix configure errors out when using Xcode 8 (clang 8.0.0)
+368412  False positive result for altivec capability check
 368461  mmapunmap test fails on ppc64
 
 n-i-bz Fix incorrect (or infinite loop) unwind on RHEL7 x86 and amd64

diff --git a/configure.ac b/configure.ac
index 63c592fb2b43d08cdbc6d64778d9f7cb06658d7c..86cf0d649511e8bcf695cb8d92604a7f6d861743 100644 (file)
--- a/configure.ac
+++ b/configure.ac
@@ -1379,8 +1379,6 @@ AC_COMPILE_IFELSE([AC_LANG_PROGRAM([[
 ]])], [
 ac_have_altivec=yes
 AC_MSG_RESULT([yes])
-AC_DEFINE([HAS_ALTIVEC], 1,
-          [Define to 1 if gcc/as can do Altivec.])
 ], [
 ac_have_altivec=no
 AC_MSG_RESULT([no])