Make the assembler-knows-POWER-DFP test a bit stricter, since it appears
some older assemblers know 'dadd' but not 'dcffix', which also appears
in the DFP tests.
git-svn-id: svn://svn.valgrind.org/valgrind/trunk@12864 a5019735-40e9-0310-863c-91ae7b9d1cf9
diff --git a/configure.in b/configure.in
index 06d63ae..e7f5db1 100644
--- a/configure.in
+++ b/configure.in
@@ -1184,11 +1184,13 @@
AM_CONDITIONAL(HAS_VSX, test x$ac_have_vsx = xyes)
+
AC_MSG_CHECKING([that assembler knows DFP])
AC_COMPILE_IFELSE([AC_LANG_PROGRAM([[
]], [[
__asm__ __volatile__("dadd 1, 2, 3");
+ __asm__ __volatile__("dcffix 1, 2");
]])], [
ac_asm_have_dfp=yes
AC_MSG_RESULT([yes])
@@ -1197,12 +1199,14 @@
AC_MSG_RESULT([no])
])
+
AC_MSG_CHECKING([that compiler knows -mhard-dfp switch])
safe_CFLAGS=$CFLAGS
CFLAGS="-mhard-dfp"
AC_COMPILE_IFELSE([AC_LANG_PROGRAM([[
]], [[
__asm__ __volatile__("dadd 1, 2, 3");
+ __asm__ __volatile__("dcffix 1, 2");
]])], [
ac_gcc_have_dfp=yes
AC_MSG_RESULT([yes])
@@ -1215,6 +1219,7 @@
AM_CONDITIONAL(HAS_DFP, test x$ac_asm_have_dfp = xyes -a x$ac_gcc_have_dfp = xyes)
+
# Check for pthread_create@GLIBC2.0
AC_MSG_CHECKING([for pthread_create@GLIBC2.0()])