Changeset 1358

Timestamp:

Jun 25, 2008, 12:21:32 AM (15 years ago)

Author:

Peter

Message:

fixes #338 - runtime tests for quiet_NaN and infinity are not
performed when cross-compiling, but instead we use a compilation
test. On the other hand, for the (most common) case when not
cross-compiling, I removed the compilation test because the result of
the test was ignored anyway.

File:

• trunk/configure.ac (modified) (3 diffs)

trunk/configure.ac

@@ -148 +148 @@
 
 # check for quiet_NaN support in OS
-# At compile time, but this may not work if quiet_NaN exists and returns
-# an incorrect value
-AC_MSG_CHECKING([for std::numeric_limits<>::quiet_NaN()])
-AC_COMPILE_IFELSE(
-  [AC_LANG_PROGRAM(
-    [#include <limits>
-     extern void f(double);],
-    [f(std::numeric_limits<double>::quiet_NaN())])],
-  [quiet_nan=yes],
-  [quiet_nan=no])
-AC_MSG_RESULT($quiet_nan)
-# At run-time, but this has the disadvantage that yat cannot be built  
-# for cross-compilation
+# Check at run-time, but if we are cross-compiling fall back on a
+# compilation test
 AC_MSG_CHECKING([if std::numeric_limits<>::has_quiet_NaN is true])
 AC_RUN_IFELSE(
@@ -166 +155 @@
     [#include <limits>],
     [return !std::numeric_limits<double>::has_quiet_NaN])],
-  [quiet_nan=yes],
-  [quiet_nan=no])
-AC_MSG_RESULT($quiet_nan)
+  [quiet_nan=yes 
+   AC_MSG_RESULT($quiet_nan)],
+  [quiet_nan=no 
+   AC_MSG_RESULT($quiet_nan)],
+  # if we are cross-compiling fall back on compilation test
+  [AC_MSG_RESULT(cross-compiling)
+   AC_MSG_CHECKING([for std::numeric_limits<>::quiet_NaN()])
+    AC_COMPILE_IFELSE(
+     [AC_LANG_PROGRAM(
+        [#include <limits>
+         extern void f(double);],
+        [f(std::numeric_limits<double>::quiet_NaN())])],
+     [quiet_nan=yes],
+     [quiet_nan=no])
+   AC_MSG_RESULT($quiet_nan)])
 # Check for infinity support for doubles in OS
-# At run-time, but this has the disadvantage that yat cannot be built  
-# for cross-compilation
+# Check at run-time, but if we are cross-compiling fall back on a
+# compilation test
 AC_MSG_CHECKING([if std::numeric_limits<>::has_infinity is true])
 AC_RUN_IFELSE(
@@ -177 +178 @@
     [#include <limits>],
     [return !std::numeric_limits<double>::has_infinity])],
-  [has_infinity=yes],
-  [has_infinity=no])
-AC_MSG_RESULT($has_infinity)
+  [has_infinity=yes
+   AC_MSG_RESULT($has_infinity)],
+  [has_infinity=no 
+   AC_MSG_RESULT($has_infinity)],
+  # if we are cross-compiling fall back on compilation test
+  [AC_MSG_RESULT(cross-compiling)
+   AC_MSG_CHECKING([for std::numeric_limits<>::infinity()])
+    AC_COMPILE_IFELSE(
+     [AC_LANG_PROGRAM(
+        [#include <limits>
+         extern void f(double);],
+        [f(std::numeric_limits<double>::infinity())])],
+     [has_infinity=yes],
+     [has_infinity=no])
+   AC_MSG_RESULT($has_infinity)])