[svn-r2994] Updated with parallel bug fix.

1 files changed, 50 insertions, 44 deletions

diff --git a/RELEASE b/RELEASE
index af42710..000b0e6 100644
--- a/RELEASE
+++ b/RELEASE
@@ -62,67 +62,69 @@ New features
 Release Notes for h4toh5 beta
 =============================
 
-The h4toh5 utility converts an HDF4 file to an HDF5 file.
-See the document, "Mapping HDF4 Objects to HDF5 Objects",
-http://hdf.ncsa.uiuc.edu/HDF5/papers/H4-H5MappingGuidelines.pdf
+    The h4toh5 utility converts an HDF4 file to an HDF5 file.
+    See the document, "Mapping HDF4 Objects to HDF5 Objects",
+    http://hdf.ncsa.uiuc.edu/HDF5/papers/H4-H5MappingGuidelines.pdf
 
-Known Limitations of the h4toh5 beta release
-=============================================
+    Known Limitations of the h4toh5 beta release
+    ---------------------------------------------
 
-1. Error handling
+    1. Error handling
 
-Error reporting is minimal.
+    Error reporting is minimal.
 
-2. String datatype
+    2. String datatype
 
-HDF4 has no 'string' type. String valued data are usually defined 
-as an array of 'char' in HDF4. The h4toh5 utility will generally
-map these to HDF5 'String' types rather than array of char, with
-the following additional rules:
+    HDF4 has no 'string' type. String valued data are usually defined 
+    as an array of 'char' in HDF4. The h4toh5 utility will generally
+    map these to HDF5 'String' types rather than array of char, with
+    the following additional rules:
 
-   * For the data of HDF4 SDS, image, and palette, if the data is
-     declared 'DFNT_CHAR8' it will be assumed to be integer and
-     will be an H5T_INTEGER type.
-   * For attributes of any HDF4 object, data of type 'DFNT_CHAR8'
-     will be converted to an HDF5 'H5T_STRING' type.
-   * For Vdata of HDF4, it is difficult to determine whether data 
-     of type 'DFNT_CHAR8' is intended to be bytes or charaters.
-     The h4toh5 utility will consider them as C character, and
-     will convert them to an HDF5 'H5T_STRING' type.
+       * For the data of HDF4 SDS, image, and palette, if the data is
+	 declared 'DFNT_CHAR8' it will be assumed to be integer and
+	 will be an H5T_INTEGER type.
+       * For attributes of any HDF4 object, data of type 'DFNT_CHAR8'
+	 will be converted to an HDF5 'H5T_STRING' type.
+       * For Vdata of HDF4, it is difficult to determine whether data 
+	 of type 'DFNT_CHAR8' is intended to be bytes or charaters.
+	 The h4toh5 utility will consider them as C character, and
+	 will convert them to an HDF5 'H5T_STRING' type.
 
 
-3. Compression, Chunking and External storage
+    3. Compression, Chunking and External storage
 
-Chunking is supported, but compression and external storage is 
-not.
+    Chunking is supported, but compression and external storage is 
+    not.
 
-An HDF4 object that uses chunking will be converted to an HDF5
-file with analogous chunked storage.
+    An HDF4 object that uses chunking will be converted to an HDF5
+    file with analogous chunked storage.
 
-An HDF4 object that uses compression will be converted to an
-uncompressed HDF5 object.  
+    An HDF4 object that uses compression will be converted to an
+    uncompressed HDF5 object.  
 
-An HDF4 object that uses external storage will be converted to an
-an HDF5 object without external storage.  
+    An HDF4 object that uses external storage will be converted to an
+    an HDF5 object without external storage.  
 
-4. Memory use
+    4. Memory use
 
-The beta version of the h4toh5 utility copies data from HDF4
-objects in a single read followed by a single write to the
-HDF5 object.  For large objects, this requires a very large 
-amount of memory, which may be extremely slow or fail on 
-some platforms.
+    The beta version of the h4toh5 utility copies data from HDF4
+    objects in a single read followed by a single write to the
+    HDF5 object.  For large objects, this requires a very large 
+    amount of memory, which may be extremely slow or fail on 
+    some platforms.
 
-Note that a dataset that has only been partly written will
-be read completely, including uninitialized data, and all the
-data will be written to the HDF5 object.
+    Note that a dataset that has only been partly written will
+    be read completely, including uninitialized data, and all the
+    data will be written to the HDF5 object.
 
-5. Platforms
+    5. Platforms
+
+    The h4toh5 utility requires HDF5.1.4.
+
+    The beta h4toh5 utility has been tested on Solaris 2.6, Solaris 2.5,
+    Irix 6.5, HPUX 11.0, DEC Unix, FreeBSD, and Windows 2000.
 
-The h4toh5 utility requires HDF5.1.4.
 
-The beta h4toh5 utility has been tested on Solaris 2.6, Solaris 2.5,
-Irix 6.5, HPUX 11.0, DEC Unix, FreeBSD, and Windows 2000.
 Bug fixes since HDF5-1.2.0
 
 ==========================
@@ -167,7 +169,11 @@ Library
      object or region references and disallow dereference.
    * "Time" datatypes (H5T_UNIX_D*) were not being stored and retrieved from
      object headers correctly, fixed now.
-
+   * Fixed H5Dread or H5Dwrite calls with H5FD_MPIO_COLLECTIVE requests that
+     may hang because not all processes are transfer the same amount of data.
+     (A.K.A. prematured collective return when zero amount data requested.)
+     Collective calls that may cause hanging is done via the corresponding
+     MPI-IO independent calls.
 
 Configuration
 -------------