[svn-r11311] Purpose: New features.

Description:  Added 2 new configure options, --enable-exception and --enable-accuracy.

--enable-exception lets the library check whether user's exception handling
functions are present during compiler data conversions and use them if they are.
When it's disabled, this step is skipped to improve conversion speed.  This
step isn't implemented yet for soft conversions because there would be little
gain in speed.

--enable-accuracy guarantees data accuracy during data conversions.  It means
the library will choose compiler conversions only if the accurate data is
secured.  Otherwise, the library will go for the library's own conversions.  If
this option is disabled, the library uses compiler conversions in favor of
their speed as long as they work even if data can be incorrect.


Platforms tested: h5committest and fuss.  Some systems may fail after this
checkin.

2 files changed, 6 insertions, 6 deletions

diff --git a/config/irix5.x b/config/irix5.x
index 51b0462..874e263 100644
--- a/config/irix5.x
+++ b/config/irix5.x
@@ -61,7 +61,7 @@ esac
 
 # Hard set flag to indicate that the 'unsigned long long' to floating-point
 # value conversion are broken by the compilers (as of 4/27/04 - QAK)
-hdf5_cv_sw_ulong_to_fp_bottom_bit_works=${hdf5_cv_sw_ulong_to_fp_bottom_bit_works='no'}
+hdf5_cv_ulong_to_fp_bottom_bit_accurate=${hdf5_cv_ulong_to_fp_bottom_bit_accurate='no'}
 
 # Set flags to avoid conversion between 'long double' and integers because of 
 # SGI's compiler problems.  For both IRIX64 6.5 and IRIX 6.5, the compilers
@@ -76,5 +76,5 @@ hdf5_cv_sw_ulong_to_fp_bottom_bit_works=${hdf5_cv_sw_ulong_to_fp_bottom_bit_work
 #       long or long long -> long double : correct value but incorrect bit pattern
 #       unsigned long or long long -> long double : correct value but incorrect bit pattern
 # (1/5/05 - SLU)
-hdf5_cv_sw_ldouble_to_int_works=${hdf5_cv_sw_ldouble_to_int_works='no'}
-hdf5_cv_sw_integer_to_ldouble_works=${hdf5_cv_sw_integer_to_ldouble_works='no'}
+hdf5_cv_ldouble_to_integer_accurate=${hdf5_cv_ldouble_to_integer_accurate='no'}
+hdf5_cv_integer_to_ldouble_accurate=${hdf5_cv_integer_to_ldouble_accurate='no'}
diff --git a/config/irix6.x b/config/irix6.x
index 2bc87c0..3c9920d 100644
--- a/config/irix6.x
+++ b/config/irix6.x
@@ -155,7 +155,7 @@ fi
 
 # Hard set flag to indicate that the 'unsigned long long' to floating-point
 # value conversion are broken by the compilers (as of 4/27/04 - QAK)
-hdf5_cv_sw_ulong_to_fp_bottom_bit_works=${hdf5_cv_sw_ulong_to_fp_bottom_bit_works='no'}
+hdf5_cv_ulong_to_fp_bottom_bit_accurate=${hdf5_cv_ulong_to_fp_bottom_bit_accurate='no'}
 
 # Set flags to avoid conversion between 'long double' and integers because of 
 # SGI's compiler problems.  For both IRIX64 6.5 and IRIX 6.5, the compilers
@@ -170,8 +170,8 @@ hdf5_cv_sw_ulong_to_fp_bottom_bit_works=${hdf5_cv_sw_ulong_to_fp_bottom_bit_work
 #       long or long long -> long double : correct value but incorrect bit pattern
 #       unsigned long or long long -> long double : correct value but incorrect bit pattern
 # (1/5/05 - SLU)
-hdf5_cv_sw_ldouble_to_integer_works=${hdf5_cv_sw_ldouble_to_integer_works='no'}
-hdf5_cv_sw_integer_to_ldouble_works=${hdf5_cv_sw_integer_to_ldouble_works='no'}
+hdf5_cv_ldouble_to_integer_accurate=${hdf5_cv_ldouble_to_integer_accurate='no'}
+hdf5_cv_integer_to_ldouble_accurate=${hdf5_cv_integer_to_ldouble_accurate='no'}
 
 # For IRIX 6.5, any version that is older than MIPSpro 7.3.1.3m, 
 # the MPI derived datatype is not working.