diff options
author | Dana Robinson <derobins@hdfgroup.org> | 2017-07-05 21:37:11 (GMT) |
---|---|---|
committer | Dana Robinson <derobins@hdfgroup.org> | 2017-07-05 21:37:11 (GMT) |
commit | 5bf108432ba9b49ee545af3947b7fb2e2b6e8514 (patch) | |
tree | b3a5c2e7af1b5169769793e44038990d7931c214 | |
parent | dc048e96f3d57a4804101d17528e40051734c022 (diff) | |
download | hdf5-5bf108432ba9b49ee545af3947b7fb2e2b6e8514.zip hdf5-5bf108432ba9b49ee545af3947b7fb2e2b6e8514.tar.gz hdf5-5bf108432ba9b49ee545af3947b7fb2e2b6e8514.tar.bz2 |
Updated RELEASE.txt
-rw-r--r-- | release_docs/RELEASE.txt | 90 |
1 files changed, 53 insertions, 37 deletions
diff --git a/release_docs/RELEASE.txt b/release_docs/RELEASE.txt index 7df405d..a4a74a7 100644 --- a/release_docs/RELEASE.txt +++ b/release_docs/RELEASE.txt @@ -72,41 +72,6 @@ New Features (HDFFV-9937, DER, 2017/05/31) - - Corrected FORTRAN_HAVE_C_LONG_DOUBLE processing in the autotools. - - A bug in the autotools Fortran processing code always set the - FORTRAN_HAVE_C_LONG_DOUBLE variable to be true regardless of - whether or not a C long double type was present. - - This would cause compilation failures on platforms where a C - long double type was not available and the Fortran wrappers - were being built. - - (HDFFV-10247, DER, 2017/07/05) - - - The deprecated --enable-production and --enable-debug configure options - failed to emit errors when passed an empty string - (e.g.: --enable-debug=""). - - Due to the way we checked for these options being set, it was possible - to avoid the error message and continue configuration if an empty string - was passed to the option. - - Any use of --enable-production or --enable-debug will now halt the - configuration step and emit a helpful error message - (use --enable-build-mode=debug|production instead). - - (HDFFV-10248, DER, 2017/07/05) - - - FC_BASENAME was set to 'gfortran40' instead 'gfortran' in the autotools - processing on gcc (any platform) and freebsd. - - This was probably a historical artifact and so was changed to - 'gfortran'. We don't use FC_BASENAME in our processing, so this - had no effect on building the library normally. - - (HDFFV-10249, DER, 2017/05/31) - - -fno-omit-frame-pointer was added when building with debugging symbols enabled. @@ -116,7 +81,7 @@ New Features we've disabled this optimization when debugging symbols are requested (e.g.: via building with --enable-symbols). - (HDFFV-10250, DER, 2017/05/31) + (HDFFV-10226, DER, 2017/05/31) Library: -------- @@ -143,6 +108,17 @@ New Features (HDFFV-10214, DER, 2017/05/31) + - The H5I_REFERENCE value in the H5I_type_t enum (defined in H5Ipublic.h) + has been marked as deprectated. + + This ID type value is not used in the C library. i.e.: There are no + hid_t values that are of ID type H5I_REFERENCE. + + This enum value will be removed in a future major version of the library. + The code will remain unchanged in the HDF5 1.10.x branches. + + (HDFFV-10252, DER, 2017/04/05) + Parallel Library: ----------------- - @@ -155,6 +131,21 @@ New Features ------------ - + Java Library: + ------------- + + - The H5I_REFERENCE value in the H5I_type_t enum (defined in H5Ipublic.h) + has been marked as deprectated. + + JNI code which refers to this value will be removed in a future + major version of the library. The code will remain unchanged in the + 1.10.x branches. + + See the C library section, above, for further information. + + (HDFFV-10252, DER, 2017/04/05) + + Tools: ------ - @@ -188,7 +179,32 @@ Bug Fixes since HDF5-1.10.0-patch1 release Configuration ------------- - - + - Corrected FORTRAN_HAVE_C_LONG_DOUBLE processing in the autotools. + + A bug in the autotools Fortran processing code always set the + FORTRAN_HAVE_C_LONG_DOUBLE variable to be true regardless of + whether or not a C long double type was present. + + This would cause compilation failures on platforms where a C + long double type was not available and the Fortran wrappers + were being built. + + (HDFFV-10247, DER, 2017/07/05) + + - The deprecated --enable-production and --enable-debug configure options + failed to emit errors when passed an empty string + (e.g.: --enable-debug=""). + + Due to the way we checked for these options being set, it was possible + to avoid the error message and continue configuration if an empty string + was passed to the option. + + Any use of --enable-production or --enable-debug will now halt the + configuration step and emit a helpful error message + (use --enable-build-mode=debug|production instead). + + (HDFFV-10248, DER, 2017/07/05) + Performance ------------- |