summaryrefslogtreecommitdiffstats
path: root/src/H5config.h.in
diff options
context:
space:
mode:
authorRaymond Lu <songyulu@hdfgroup.org>2009-08-19 21:57:12 (GMT)
committerRaymond Lu <songyulu@hdfgroup.org>2009-08-19 21:57:12 (GMT)
commit91e6f1e04de956b44c89ebaaeff5d9e91d8355c4 (patch)
treec47510553adfa094a1850b98a2436ab0ff33718d /src/H5config.h.in
parentd1ee62c9156db07134b80ba6cc3d6ddc9617d5d7 (diff)
downloadhdf5-91e6f1e04de956b44c89ebaaeff5d9e91d8355c4.zip
hdf5-91e6f1e04de956b44c89ebaaeff5d9e91d8355c4.tar.gz
hdf5-91e6f1e04de956b44c89ebaaeff5d9e91d8355c4.tar.bz2
[svn-r17387] I added a detection for the correctness of converting from unsigned long to float in the
configure.in. The Pathscale compiler on Sandia's Linux machine misinterprets the values of unsigned long as negative during the conversion to float, when the first bit of unsigned long is on. Tested on jam. Need to test it on Sandia's machine.
Diffstat (limited to 'src/H5config.h.in')
-rw-r--r--src/H5config.h.in4
1 files changed, 4 insertions, 0 deletions
diff --git a/src/H5config.h.in b/src/H5config.h.in
index 8ac19fc..ca73c6a 100644
--- a/src/H5config.h.in
+++ b/src/H5config.h.in
@@ -614,6 +614,10 @@
correct precision. */
#undef ULLONG_TO_LDOUBLE_PRECISION
+/* Define if your system accurately converting unsigned long to float values.
+ */
+#undef ULONG_TO_FLOAT_ACCURATE
+
/* Define if your system can accurately convert unsigned (long) long values to
floating-point values. */
#undef ULONG_TO_FP_BOTTOM_BIT_ACCURATE