Update RELEASE.txt

* Remove some entries that were released in HDF5 1.14.3
* Update the NVidia compiler optimization known problem with new info
* Tidy 'known problems' section

release_docs/RELEASE.txt

@@ -347,22 +347,6 @@ New Features
       to filtered datasets. The Subfiling VFD now properly handles vector
       I/O requests in their entirety, resulting in fewer I/O calls, improved
       vector I/O performance and improved vector I/O memory efficiency.
-
-    - Added a simple cache to the read-only S3 (ros3) VFD
-
-      The read-only S3 VFD now caches the first N bytes of a file stored
-      in S3 to avoid a lot of small I/O operations when opening files.
-      This cache is per-file and created when the file is opened.
-
-      N is currently 16 MiB or the size of the file, whichever is smaller.
-
-      Addresses GitHub issue #3381
-
-    - Added new API function H5Pget_actual_selection_io_mode()
-
-      This function allows the user to determine if the library performed
-      selection I/O, vector I/O, or scalar (legacy) I/O during the last HDF5
-      operation performed with the provided DXPL.
 
     - Added support for in-place type conversion in most cases
 
@@ -892,15 +876,6 @@ Bug Fixes since HDF5-1.14.3 release
       datatype conversion exceptions. This has now been fixed by not running
       the test when H5_WANT_DCONV_EXCEPTION is not defined.
 
-    - Disabled running of MPI Atomicity tests for OpenMPI major versions < 5
-
-      Support for MPI atomicity operations is not implemented for major
-      versions of OpenMPI less than version 5. This would cause the MPI
-      atomicity tests for parallel HDF5 to sporadically fail when run
-      with OpenMPI. Testphdf5 now checks if OpenMPI is being used and will
-      skip running the atomicity tests if the major version of OpenMPI is
-      < 5.
-
     - Fixed a testing failure in testphdf5 on Cray machines
 
       On some Cray machines, what appears to be a bug in Cray MPICH was causing
@@ -1071,12 +1046,12 @@ Platforms Tested
 Known Problems
 ==============
 
-    When building with the NAG Fortran compiler using the Autotools and libtool
+ -  When building with the NAG Fortran compiler using the Autotools and libtool
     2.4.2 or earlier, the -shared flag will be missing '-Wl,', which will cause
     compilation to fail. This is due to a bug in libtool that was fixed in 2012
     and released in 2.4.4 in 2014.
 
-    When HDF5 is compiled with NVHPC versions 23.5 - 23.9 (additional versions may
+ -  When HDF5 is compiled with NVHPC versions 23.5 - 23.9 (additional versions may
     also be applicable) and with -O2 (or higher) and -DNDEBUG, test failures occur
     in the following tests:
 
@@ -1085,53 +1060,54 @@ Known Problems
         H5TEST-testhdf5-base
         MPI_TEST_t_filters_parallel
 
-    Since these tests pass with an optimization level of -O1 (and -O0) and it is
-    currently unclear whether the test failures are due to issues in HDF5 or issues
-    in the 'nvc' compiler, the maximum optimization level for NVHPC has been set
-    to -O1 until the test failures can be resolved. Note that even at -O1 optimization
-    level, there still appears to be a sporadic test failure in the Java JUnit tests
-    that has occasionally been seen in JUnit-TestH5Pfapl and JUnit-TestH5D. It is also
-    unclear whether this is an issue in HDF5 or with the 'nvc' compiler. Finally, note
-    that NVHPC 23.9 will fail to compile the test/tselect.c test file with a compiler
+    Sporadic failures (even with lower -O levels):
+        Java JUnit-TestH5Pfapl
+        Java JUnit-TestH5D
+
+    Also, NVHPC will fail to compile the test/tselect.c test file with a compiler
     error of 'use of undefined value' when the optimization level is -O2 or higher.
-    Nvidia is aware of this issue and has suggested lowering the optimization level to
-    -O1 for the time being:
+
+    This is confirmed to be a bug in the nvc compiler that has been fixed as of
+    23.11. If you are using an affected version of the NVidia compiler, the
+    work-around is to set the optimization level to -O1.
+
     https://forums.developer.nvidia.com/t/hdf5-no-longer-compiles-with-nv-23-9/269045.
 
-    CMake files do not behave correctly with paths containing spaces.
+ -  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.
 
-    At present, metadata cache images may not be generated by parallel
+ -  At present, metadata cache images may not be generated by parallel
     applications.  Parallel applications can read files with metadata cache
     images, but since this is a collective operation, a deadlock is possible
     if one or more processes do not participate.
 
-    The subsetting option in ph5diff currently will fail and should be avoided.
+ -  The subsetting option in ph5diff currently will fail and should be avoided.
     The subsetting option works correctly in serial h5diff.
 
-    Flang Fortran compilation will fail (last check version 17) due to not yet
+ -  Flang Fortran compilation will fail (last check version 17) due to not yet
     implemented: (1) derived type argument passed by value (H5VLff.F90),
     and (2) support for REAL with KIND = 2 in intrinsic SPACING used in testing.
 
-    Fortran tests HDF5_1_8.F90 and HDF5_F03.F90 will fail with Cray compilers greater than
-    version 16.0 due to a compiler bug. The latest version verified as failing was version 17.0.
+ -  Fortran tests HDF5_1_8.F90 and HDF5_F03.F90 will fail with Cray compilers
+    greater than version 16.0 due to a compiler bug. The latest version verified
+    as failing was version 17.0.
 
-    Several tests currently fail on certain platforms:
+ -  Several tests currently fail on certain platforms:
         MPI_TEST-t_bigio fails with spectrum-mpi on ppc64le platforms.
 
         MPI_TEST-t_subfiling_vfd and MPI_TEST_EXAMPLES-ph5_subfiling fail with
         cray-mpich on theta and with XL compilers on ppc64le platforms.
 
         MPI_TEST_testphdf5_tldsc fails with cray-mpich 7.7 on cori and theta.
 
-    Known problems in previous releases can be found in the HISTORY*.txt files
+ -  File space may not be released when overwriting or deleting certain nested
+    variable length or reference types.
+
+ -  Known problems in previous releases can be found in the HISTORY*.txt files
     in the HDF5 source. Please report any new problems found to
     help@hdfgroup.org.
 
-    File space may not be released when overwriting or deleting certain nested
-    variable length or reference types.
-
 
 CMake vs. Autotools installations
 =================================