Update release.txt (#2201)

* Some Javadoc warning fixes

* Updated javadoc fixes

* # WARNING: head commit changed in the meantime

HDFFV-11229 Fix long double usage in tools and java

Changed h5dump and h5ls to just print 128-bit for long double type.
Added test and file for dataset and attributes with all three float
types.

* Committing clang-format changes

* HDFFV-11229 Add release note

* HDFFV-11229 windows testfile needed

* fix typo

* Remove non supported message text

* HDFFV-11229 - change ldouble test to check both native and general

* HDFFV-11229 add second file compare

* HDFFV-11229 fix reference file

* HDFFV-11229 autotools check two refs

* HDFFV-11229 revert back to removal of NATIVE_LDOUBLE in tools output

* Committing clang-format changes

* Update release note

* Update attribute type of ref file

* Change source of ninja for macs

* try port instead of brew

* Recommended is to use brew.

* Undo non long double changes

* remove unneeded file

* Fix perl and doxygen CMake code

* Add "option" command for clang options

* Rework CMake add_custom to use the BYPRODUCTS argument

* Add stamp files to BYPRODUCTS

* Only one copy of file exists

* Fix custom cmmand depends targets

* Fix fortran custom command DEPENDS

* Add LD_LIBRARY_PATH to tests

* Add custom target for DEPENDS

* Add h5detect conditionaly to generated target DEPENDS

* Correct DEPENDS targets

* Parallel builds need the mpi compiler for pkgconfig scripts.

* install only if MPI build

* Fortran target depends

* Remove incorrect source attribute

* doxygen adjustments

* doxygen build updates

* Correct version

* Correct function version - function has been merged to 1.12

* Correct version string for map functions

* Cleanup warnings for tools debug builds

* TRILAB-227 - fix indexing for h5diff selections

* Correct location of pos to index function call

* TRILAB-227 Enable test

* Quote subset args

* Use MATCHES because of AppleClang

* if blocks needed for build modes

* Update list of DT platforms

* VS2019 correctly displays float values

* revert VS2019 change

* Issue #669 remove version from pkgcfg filename

* remove version from h5cc script

* Java reference functions updated

enabled fortran in cmake gcc action yaml file
java reference test changed to correctly test refs
jni reference functions that create ids changed to use jni id logging

* Correct BYPRODUCTS argument

* Correct more genereated files BYPRODUCTS

* BYPRODUCTS must have unique locations

* Fix typo

* Fix fortran configure checks

* Rework H5_PAC_C_MAX_REAL_PRECISION setting logic

* Add note about fortran configure change

* Adds a quick for for some egregious chunk_info badness (#722)

* Fixes issue with ccmake that prevents building Fortran (#723)

ccmake runs iteratively, and the check_fortran_source_runs
macros were clobbering a single output file that did not
get updated on further configure iterations

* Fix conflicts with merge

* Move MAX_PRECISION back to HDF5UseFortran.cmake

* Use STREQUAL to test macro argument

* Move C language test to ConfigureChecks from HDF5UseFortran

* MAX_PRECISION defines must be defined

* Organize flags and align autotools and cmake

* Fix comment in no-error-general warnings files.

* Flag cleanup and fix typos

* Add comment

* Correct VAR used to find configure time file

* Set the path correctly

* Update missing release note info.

* Update code owners

* Correct JIRA note

* add known problem.

* Use only core library for testing dynamic plugins.

* Committing clang-format changes

* Update main.yml

* Update HISTORY-1_13.txt

Missing release note added for changed location of CMake configuration files.

* Update HISTORY-1_13.txt

Fix typo

* Update main.yml

revert change

* Updated version to 1.13.4-1 after creating hdf5_1_13_3 branch for 1.13.3
release.
Added new version to exceptions in lines 74-5 of src/H5.c

* Cleared RELEASE.txt entries following HDF5 1.13.3 release.

Co-authored-by: Allen Byrne <byrn@hdfgroup.org>
Co-authored-by: github-actions <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Allen Byrne <50328838+byrnHDF@users.noreply.github.com>
Co-authored-by: Dana Robinson <43805+derobins@users.noreply.github.com>
This commit is contained in:
Larry Knox 2022-10-28 10:10:02 -05:00 committed by GitHub
parent 4d0501f48c
commit 9acd203041
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -36,7 +36,7 @@ CONTENTS
- New Features
- Support for new platforms and languages
- Bug Fixes since HDF5-1.13.2
- Bug Fixes since HDF5-1.13.3
- Platforms Tested
- Known Problems
- CMake vs. Autotools installations
@ -47,36 +47,12 @@ New Features
Configuration:
-------------
- Add new CMake configuration variable HDF5_USE_GNU_DIRS
HDF5_USE_GNU_DIRS (default OFF) selects the use of GNU Coding Standard install
directory variables by including the CMake module, GNUInstallDirs(see CMake
documentation for details). The HDF_DIR_PATHS macro in the HDFMacros.cmake file
sets various PATH variables for use during the build, test and install processes.
By default, the historical settings for these variables will be used.
(ADB - 2022/10/21, GH-2175, GH-1716)
- Update CMake minimum version to 3.18
Updated CMake minimum version from 3.12 to 3.18 and removed version checks
which were added for Windows features not yet available in version 3.12. Also
removed configure macros and code checks for old style code compile checks.
(ADB - 2022/08/29, HDFFV-11329)
-
Library:
--------
- Added multi dataset I/O feature
Added H5Dread_multi, H5Dread_multi_async, H5Dwrite_multi, and
H5Dwrite_multi_async API routines to allow I/O on multiple datasets with a
single API call. Added H5Dread_multi_f and H5Dwrite_multi_f Fortran
wrappers. Updated VOL callbacks for dataset I/O to support multi dataset
I/O.
(NAF - 2022/10/19)
-
Parallel Library:
@ -86,12 +62,8 @@ New Features
Fortran Library:
----------------
- Added pointer based H5Dfill_f API
-
Added Fortran H5Dfill_f, which is fully equivalent to the C API. It accepts pointers,
fill value datatype and datatype of dataspace elements.
(MSB - 2022/10/10, HDFFV-10734.)
C++ Library:
------------
@ -110,7 +82,7 @@ New Features
High-Level APIs:
----------------
-
-
C Packet Table API:
@ -125,11 +97,7 @@ New Features
Documentation:
--------------
- Doxygen User Guide documentation is available when configured and generated.
The resulting documentation files will be in the share/html subdirectory
of the HDF5 install directory.
(ADB - 2022/08/09)
-
Support for new platforms, languages and compilers
@ -137,60 +105,16 @@ Support for new platforms, languages and compilers
-
Bug Fixes since HDF5-1.13.2 release
Bug Fixes since HDF5-1.13.3 release
===================================
Library
-------
- Fixed an issue with variable length attributes
Previously, if a variable length attribute was held open while its file
was opened through another handle, the same attribute was opened through
the second file handle, and the second file and attribute handles were
closed, attempting to write to the attribute through the first handle
would cause an error.
(NAF - 2022/10/24)
- Fixed an issue with hyperslab selections
Previously, when combining hyperslab selections, it was possible for the
library to produce an incorrect combined selection.
(NAF - 2022/09/25)
- Fixed an issue with attribute type conversion with compound datatypes
Previously, when performing type conversion for attribute I/O with a
compound datatype, the library would not fill the background buffer with
the contents of the destination, potentially causing data to be lost when
only writing to a subset of the compound fields.
(NAF - 2022/08/22, GitHub #2016)
- Memory leak
A memory leak was observed with variable-length fill value in
H5O_fill_convert() function in H5Ofill.c. The leak is
manifested by running valgrind on test/set_extent.c.
Previously, fill->buf is used for datatype conversion
if it is large enough and the variable-length information
is therefore lost. A buffer is now allocated regardless
so that the element in fill->buf can later be reclaimed.
(VC - 2022/10/10, HDFFV-10840)
-
Java Library
------------
- Improve variable-length datatype handling in JNI.
The existing JNI read-write functions could handle variable-length datatypes
that were simple variable-length datatype with an atomic sub-datatype. More
complex combinations could not be handled. Reworked the JNI read-write functions
to recursively inspect datatypes for variable-length sub-datatypes.
(ADB - 2022/10/12, HDFFV-8701,10375)
-
Configuration
@ -260,12 +184,6 @@ Platforms Tested
(crusher) GCC 11.2.0
(cmake)
Linux 5.3.18-24-cray_shasta_c cray-mpich/8.1.12
#1 SMP x86_64 GNU/Linux Cray clang 13.0.0
(spock) AMD clang 13.0.0
GCC 8.2.0, 11.2.0
(cmake)
Linux 4.14.0-115.35.1.1chaos openmpi 4.0.5
#1 SMP aarch64 GNU/Linux GCC 9.2.0 (ARM-build-5)
(stria) GCC 7.2.0 (Spack GCC)
@ -278,15 +196,16 @@ Platforms Tested
(cmake)
Linux-4.14.0-115.21.2 spectrum-mpi/rolling-release
#1 SMP ppc64le GNU/Linux clang 8.0.1, 11.0.1
(lassen) GCC 7.3.1
XL 16.1.1.2
#1 SMP ppc64le GNU/Linux clang 12.0.1, 14.0.5
(lassen) GCC 8.3.1
XL 16.1.1.2, 2021,09.22, 2022.08.05
(cmake)
Linux-4.12.14-150.75-default cray-mpich/7.7.10
#1 SMP x86_64 GNU/Linux GCC 7.3.0, 8.2.0
(cori) Intel (R) Version 19.0.3.199
(cmake)
Linux-4.12.14-197.99-default cray-mpich/7.7.14
#1 SMP x86_64 GNU/Linux cce 12.0.3
(theta) GCC 11.2.0
llvm 9.0
Intel 19.1.2
Linux 3.10.0-1160.36.2.el7.ppc64 gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-39)
#1 SMP ppc64be GNU/Linux g++ (GCC) 4.8.5 20150623 (Red Hat 4.8.5-39)
@ -313,10 +232,10 @@ Platforms Tested
Version 19.10-0
(autotools and cmake)
Linux-3.10.0-1127.0.0.1chaos openmpi-4.0.0
Linux-3.10.0-1160.0.0.1chaos openmpi-4.1.2
#1 SMP x86_64 GNU/Linux clang 6.0.0, 11.0.1
(quartz) GCC 7.3.0, 8.1.0
Intel 16.0.4, 18.0.2, 19.0.4
Intel 19.0.4, 2022.2, oneapi.2022.2
Linux-3.10.0-1160.71.1.1chaos openmpi/4.1
#1 SMP x86_64 GNU/Linux GCC 7.2.0
@ -372,10 +291,6 @@ Platforms Tested
Known Problems
==============
Setting a variable-length dataset fill value will leak the memory allocated
for the p field of the hvl_t struct. A fix is in progress for this.
HDFFV-10840
CMake files do not behave correctly with paths containing spaces.
Do not use spaces in paths because the required escaping for handling spaces
results in very complex and fragile build files.