HDF5 HISTORY ============ This file contains history of the HDF5 libraries releases CONTENTS 22. Release Information for hdf5-1.6.8 21. Release Information for hdf5-1.6.7 20. Release Information for hdf5-1.6.6 19. Release Information for hdf5-1.6.5 18. Release Information for hdf5-1.6.4 17. Release Information for hdf5-1.6.3 16. Release Information for hdf5-1.6.2 15. Release Information for hdf5-1.6.1 14. Release Information for hdf5-1.6.0 13. Release Information for hdf5-1.4.5 12. Release Information for hdf5-1.4.4 11. Release Information for hdf5-1.4.3 10. Release Information for hdf5-1.4.2 9. Release Information for hdf5-1.4.1 8. Release Information for hdf5-1.4.0 7. Release Information for hdf5-1.2.2 6. Release Information for hdf5-1.2.1 5. Release Information for hdf5-1.2.0 4. Changes from Release 1.0.0 to Release 1.0.1 3. Changes from the Beta 1.0.0 Release to Release 1.0.0 2. Changes from the Second Alpha 1.0.0 Release to the Beta 1.0.0 Release 1. Changes from the First Alpha 1.0.0 Release to the Second Alpha 1.0.0 Release [Search on the string '%%%%' for per-release section breaks.] %%%%1.6.8%%%% Release Information for hdf5-1.6.8 (10/November/2008) HDF5 version 1.6.8 released on Mon Nov 10 15:36:46 CST 2008 ================================================================================ INTRODUCTION ============ This document describes the differences between HDF5-1.6.7 and HDF5-1.6.8. It contains information on the platforms tested and known problems in HDF5-1.6.8. For more details, check the HISTORY.txt file in the HDF5 source. HDF5 documentation can be found in the distributed release source code in the subdirectory doc/html/ or on the THG (The HDF Group) FTP server: ftp://ftp.hdfgroup.org/HDF5/docs/ Documentation for the current release in the HDF5 Release 1.6.x series is also on the HDF web site: http://hdfgroup.org/HDF5/doc1.6/ For more information, see the HDF5 home page: http://hdfgroup.org/products/hdf5/ If you have any questions or comments, please see the HDF Support page for a list of available resources: http://hdfgroup.org/services/support.html CONTENTS ======== - New Features - Support for New Platforms, Languages and Compilers - Bug Fixes since HDF5-1.6.7 - Documentation - Platforms Tested - Supported Configuration Features Summary - Known Problems New Features ============ Configuration: ------------------------- - Added no-repeat test feature from v1.8 to this branch. What it does is that if a test has passed in previous "make check", it will not run again unless its executable has changed. This can be overridden by "make check-clean" which removes all check-success markers and let all tests run again. AKC - 2008/2/22. Library: -------- - Added support for $(DESTDIR) to the install feature. AKC - 2008/10/13. - Added version compatibility macros for functions changed in 1.8. For example, H5Gcreate1 will work the same in both 1.6 and 1.8. NAF - 2008/10/11 Parallel Library: ----------------- None Tools: ------ - h5repack and h5diff changed command line parameter syntax to be similar to h5dump, adding also long switch names. PVN - 2008/2/13 - h5repack now supports adding multiple filters to all objects. PVN - 2008/2/13 - h5import imports string (text) data. PVN - 2008/2/19 - h5dump: add a printing of the compression ratio of uncompressed and compressed sizes for cases where compression filters are present. PVN - 2008/05/01 - h5dump: added an option to allow a user defined formatting string for printf regarding floating point numbers. PVN - 2008/05/06 - h5repack: add a userblock to an HDF5 file during the repack. PVN - 2008/08/26 - h5repack: copy userblock from HDF5 file during the repack. PVN - 2008/08/26 - h5diff: return 1 for file differences when both file graphs differ by any object. Error return code was changed to 2 from -1. PVN - 2008/10/30 - h5import: TEXTFPE (scientific format) was deprecated. Use TEXTFP instead. PVN - 2008/10/30 F90 API: -------- None C++ API: -------- - These member functions were added as wrapper for H5Rdereference to replace the incorrect IdComponent::dereference(). void H5Object::dereference(H5Object& obj, void* ref, H5R_type_t ref_type=H5R_OBJECT) void H5Object::dereference(H5File& h5file, void* ref, H5R_type_t ref_type=H5R_OBJECT) void H5Object::dereference(Attribute& obj, void* ref, H5R_type_t ref_type=H5R_OBJECT) In addition, these constructors were added to create the associated objects by way of dereference: DataSet(H5Object& obj, void* ref, H5R_type_t ref_type=H5R_OBJECT) DataSet(H5File& file, void* ref, H5R_type_t ref_type=H5R_OBJECT) DataSet(Attribute& attr, void* ref, H5R_type_t ref_type=H5R_OBJECT) Group(H5Object& obj, void* ref, H5R_type_t ref_type=H5R_OBJECT) Group(H5File& obj, void* ref, H5R_type_t ref_type=H5R_OBJECT) Group(Attribute& attr, void* ref, H5R_type_t ref_type=H5R_OBJECT) DataType(H5Object& obj, void* ref, H5R_type_t ref_type=H5R_OBJECT) DataType(H5File& file, void* ref, H5R_type_t ref_type=H5R_OBJECT) DataType(Attribute& attr, void* ref, H5R_type_t ref_type=H5R_OBJECT) BMR - 2008/10/29 Support for New Platforms, Languages and Compilers ================================================== None Bug Fixes since HDF5-1.6.7 Release ================================== Library ------- - Changed the return value of H5Fget_obj_count from INT to SSIZE_T. Also changed the return value of H5Fget_obj_ids from HERR_T to SSIZE_T and the type of the parameter MAX_OBJS from INT to SIZE_T. SLU - 2008/09/26 Configuration ------------- - Fixed error with 'make check install' failing due to h5dump needing other tools built first. MAM - 2008/10/22. - Fixed error with exampples/ph5example getting built even in serial mode. Will now only get built and tested if parallel is enabled. MAM - 2008/09/18 - The file libhdf5_fortran.settings is not installed since its content is included in libhdf5.settings now. AKC - 2008/10/21 - The GASS and SRB virtual file drivers have been retired and removed from the HDF5 library. AKC - 2008/9/26 Performance ------------- None Tools ----- - h5import bug on Windows w/binary datasets. fread in windows needs a binary file to be open with 'rb' instead of 'r' otherwise it terminates execution if an end of file character is found on the input file. Besides that the binary file generated needs to be open with 'wb', otherwise an end of line character is read twice. PVN - 2008/2/19 - Fixed h5diff regarding the display of NaN (Not a Number) values. PVN - 2008/03/04 - Fixed h5dump regarding the display of array indices and block selections in subsetting. PVN - 2008/03/10 - Fixed bug in h5dump that caused binary output to be made only for the first dataset, when several datasets were requested. PVN - 2008/04/07 - h5dump: when doing binary output (-b), the stdout printing of attributes was done incorrectly. Removed printing of attributes when doing binary output. PVN - 2008/06/05 Documentation ------------- None F90 API ------- None C++ API ------- - Fixed a design bug which allowed an Attribute object to create/modify attributes (bugzilla #1068). The API class hierarchy was revised to address the problem. Classes AbstractDS and Attribute are moved out of H5Object. Class Attribute now multiply inherits from IdComponent and AbstractDs and class DataSet from H5Object and AbstractDs. In addition, the data member IdComponent::id was moved into subclasses: Attribute, DataSet, DataSpace, DataType, H5File, Group, and PropList. BMR - 2008/08/10 - IdComponent::dereference was incorrect and replaced as described in "New Features" section. BMR - 2008/08/10 Documentation ============= HDF5 documentation can be found in the distributed release source code in the subdirectory doc/html/ (start with index.html) or on the THG (The HDF Group) FTP server: ftp://ftp.hdfgroup.org/HDF5/docs/ Online documentation for the current release in the HDF5 Release 1.6.x series can be found on the THG web site: http://hdfgroup.org/HDF5/doc1.6/ A listing of interface changes from release to release can be found in the document "HDF5 Software Changes from Release to Release": http://hdfgroup.org/HDF5/doc1.6/ADGuide/Changes.html Since the stream I/O driver is not included in this release, the functions H5Pset_fapl_stream and H5Pget_fapl_stream and the stream ENUM value H5FD_STREAM have been removed from the documentation. Platforms Tested ================ AIX 5.3 xlc 7.0.0.8 xlf 09.01.0000.0008 xlC 7.0.0.8 mpcc_r 7.0.0.8 mpxlf_r 09.01.0000.0008 FreeBSD 6.3-STABLE i386 gcc 3.4.6 [FreeBSD] 20060305 (duty) g++ 3.4.6 [FreeBSD] 20060305 gcc 4.2.5 20080702 g++ 4.2.5 20080702 gfortran 4.2.5 20080702 FreeBSD 6.3-STABLE amd64 gcc 3.4.6 [FreeBSD] 20060305 (liberty) g++ 3.4.6 [FreeBSD] 20060305 gcc 4.2.5 20080702 g++ 4.2.5 20080702 gfortran 4.2.5 20080702 IRIX64 6.5 MIPSpro cc 7.4.4m (ucar mop1 64 & n32) F90 MIPSpro 7.4.4m (64 only) C++ MIPSpro cc 7.4.4m Linux 2.6.9-42.0.10.ELsmp #1 gcc (GCC) 3.4.6 SMP i686 i386 G95 (GCC 4.0.3 (g95 0.92!) April 18 2007) (kagiso) PGI C, Fortran, C++ 7.2-1 32-bit Intel(R) C Compiler for 32-bit applications, Version 10.1 Intel(R) C++ Compiler for 32-bit applications, Version 10.1 Intel(R) Fortran Compiler for 32-bit applications, Version 10.1 Absoft 32-bit Fortran 95 10.0.4 MPICH mpich-1.2.7 compiled with gcc 3.4.6 and G95 (GCC 4.0.3 (g95 0.92!) MPICH mpich2-1.0.6p1 compiled with gcc 3.4.6 and G95 (GCC 4.0.3 (g95 0.92!) Linux 2.6.16.46-0.12-debug #1 Intel(R) C++ Version 10.0.025 SMP ia64 GNU/Linux Intel(R) Fortran Itanium(R) Version 10.0.025 (ucar hir1) Linux 2.6.16.46-0.14-smp #1 Intel(R) C++ for Intel(R) EM64T Ver. 10.1.013 SMP x86_64 GNU/Linux Intel(R) Fortran Intel(R) EM64T Ver. 10.1.013 (smirom) PGI C, Fortran, C++ Version 7.2-1 for 64-bit target on x86-64 MPICH mpich-1.2.7 compiled with gcc 4.1.2 and G95 (GCC 4.0.3 (g95 0.92!) MPICH mpich2-1.0.7 compiled with gcc 4.1.2 and G95 (GCC 4.0.3 (g95 0.92!) tested for both 32- and 64-bit binaries Linux 2.6.16.54-0.2.5 #1 Intel(R) C++ Version 10.1.017 Altix SMP ia64 Intel(R) Fortran Itanium(R) Version 10.1.017 (cobalt) SGI MPI 1.16 SunOS 5.10 32- and 64-bit Sun WorkShop 6 update 2 C 5.8 (linew) Sun WorkShop 6 update 2 Fortran 95 8.2 Sun WorkShop 6 update 2 C++ 5.8 Patch 121019-06 Xeon Linux 2.6.9-42.0.10.EL_lustre-1.4.10.1smp (abe) Intel(R) C++ Version 10.0.026 Intel(R) Fortran Compiler Version 10.0.026 Open MPI 1.2.2 MVAPICH2-0.9.8p28p2patched-intel-ofed-1.2 compiled with icc v10.0.026 and ifort 10.0.026 IA-64 Linux 2.4.21-309.tg1 #1 SMP ia64 gcc (GCC) 3.2.2 (NCSA tg-login) Intel(R) C++ Version 8.1.037 Intel(R) Fortran Compiler Version 8.1.033 mpich-gm-1.2.7p1..16-intel-8.1.037-r1 Windows XP Visual Studio 6.0 Visual Studio .NET (with Intel Fortran 9.1) Visual Studio 2005 (with Intel Fortran 9.1) cygwin (gcc 3.4.4) Windows Vista Visual studio 2005 Mac OS X Intel 10.5.4 i686-apple-darwin9-gcc-4.0.1 (GCC) 4.0.1 g95 0.91 Supported Configuration Features Summary ======================================== Key: y = Tested and supported n = Not supported or not tested in this release C = Cluster W = Workstation ( ) = Footnote appears below second table Platform C F90 F90 C++ zlib SZIP parallel parallel Solaris2.10 32-bit n y n y y y Solaris2.10 64-bit n y n n y y IRIX64_6.5 32-bit n n n n y y IRIX64_6.5 64-bit n y n n y y WinXP Visual Studio 6.0 n n n y y y WinXP CYGWIN n n n y y y WinXP 2005 n y n y y y WinXP .Net n y n y y y WinVista 2005 n n n y y y Mac OS X 10.4.10 n y n y y y AIX 5.3 32-bit n y n y y n FreeBSD 6.3 32- and 64-bit n n n y y y RedHat EL4 2.6.9-42 i686 GNU (1) W y y y y y y RedHat EL4 2.6.9-42 i686 Intel W n y n y y n RedHat EL4 2.6.9-42 i686 PGI W n y n y y n SuSE Linux 2.6.16 x86_64 GNU (1) W y y n y y y SuSE Linux 2.6.16 x86_64 Intel W n y n y y n SuSE Linux 2.6.16 x86_64 PGI W n y n y y n RedHat EL 4 2.6.9 Xeon Lustre C n y n y y y SuSE Linux 2.4.21 ia64 C y y y y y y SuSe Linux 2.6.16 SGI Altix ia64 C n y n y y y Platform Shared static- Thread- libraries(4) exec safe Solaris2.10 32- and 64-bit y n y IRIX64_6.5 32-bit y n y IRIX64_6.5 64-bit y n y WinXP Visual Studio 6.0 y n n WinXP CYGWIN y n n WinXP 2005 y n n WinXP .Net y n n WinVista 2005 y n n Mac OS X 10.4.10 y n n AIX 5.3 32-bit n n n FreeBSD 6.3 32- and 64-bit y n n RedHat EL4 2.6.9-42 i686 GNU (1) W y n y RedHat EL4 2.6.9-42 i686 Intel W y n n RedHat EL4 2.6.9-42 i686 PGI W n n n SuSE Linux 2.6.16 x86_64 GNU (1) W y n y SuSE Linux 2.6.16 x86_64 Intel W y n n SuSE Linux 2.6.16 x86_64 PGI W n n n RedHat EL4 2.6.9 Xeon Lustre C y n n SuSE Linux 2.4.21 ia64 C y n n SuSe Linux 2.6.16 SGI Altix ia64 C n n n Compiler versions for each platform are listed in the "Platforms Tested" table found elsewhere in this file (RELEASE.txt). Unless otherwise noted, compilers used are the system compilers. Footnotes: (1) Fortran compiled with g95. Known Problems ============== * We discovered two problems when running collective IO parallel HDF5 tests with chunking storage with the ChaMPIon MPI compiler on tungsten, a Linux cluster at NCSA. Under some complex selection cases, 1) MPI_Get_element returns the wrong value. 2) MPI_Type_struct also generates the wrong derived datatype and corrupt data may be generated. This only happens when turning on collective IO with chunking storage with some complex selections. We haven't found these problems on other MPI-IO compilers. If you encounter these problems, you may use Independent IO instead. To avoid this problem, change the following line in your code: H5Pset_dxpl_mpio(xfer_plist, H5FD_MPIO_COLLECTIVE); to H5Pset_dxpl_mpio(xfer_plist, H5FD_MPIO_INDEPENDENT); KY - 2007/08/24 * QSC (an HP alpha-based OSF1 cluster) does not create h5pfc correctly. It does not include the -lmpi properly. This will be fixed in the next release. AKC - 2007/08/07. * On IRIX64 6.5 (UCAR SGI mop1), when testing HDF5 tools with an HDF5 shared library, especially for h5repacktst and h52gifgentst, the following (or a similar) error message may appear: "523648:lt-h5repacktst: rld: Fatal Error: Cannot Successfully map soname 'libh5test.so.1' under any of the filenames .......(bunch of directories) " And the testing will fail. We believe this is a libtool problem. One way to get rid of this is to add the paths of libh5test.so.1 and libh5.so.1 to the shared library path. You may do this, under csh: setenv LD_LIBRARYN32_PATH [full path of HDF5 directory/test/.libs]:[full path of HDF5 directory/src/.libs]:(existing paths)... NOTE: This problem ONLY affects the testing of the HDF5 library when you build from source. It won't affect any applications that would like to link with the HDF5 shared library since the shared library path needs to be set anyway. KY - 2007/8/2 * QSC (an HP alpha-based OSF1 cluster) failed the testpar/testphdf5 sub-test "calloc". All other tests passed. This indicates that a dataset using chunked storage created by serial HDF5 may not work properly with parallel HDF5. The calloc test can be skipped by running "prun ... testphdf5 -x calloc". AKC - 2007/7/12. * When testing parallel HDF5 with the C compiler version MIPSpro 7.4.3 on IRIX 6.5, set the environment variable MPI_TYPE_MAX to be a bigger number, for example 120000, in order to pass the complicated collective IO tests inside the parallel HDF5 library. This is not a problem inside the parallel HDF5 library. You can always set a bigger number on your system. KY - 2005/10/6 * A contiguous or chunked dataset created by a sequential version of HDF5 might not be able to be modified with a parallel version of the library. Use the H5Pset_alloc_time function with H5D_ALLOC_TIME_EARLY to set up the dataset creation property list to avoid the problem. EIP - 2005/09/09 * A dataset created or rewritten with the v1.6.3 library or after can't be read with the v1.6.2 library or before when Fletcher32 EDC (a filter) is enabled. There was a bug in the calculating code of the Fletcher32 checksum in the library before v1.6.3. The checksum value wasn't consistent between big-endian and little-endian systems. This bug was fixed in Release 1.6.3. However, after fixing the bug, the checksum value is no longer the same as before on little-endian system. HDF5 library releases after 1.6.4 can still read datasets created or rewritten with an HDF5 library of v1.6.2 or before. SLU - 2005/7/8 * test/big fails sometimes with the message "Possible overlap with another region." The test selects regions randomly, and this error occurs when two regions overlap each other; it is a bug in the test and not in HDF5. Since the error is triggered by a random situation, it will usually disappear if the test is re-run. * Newer SGI MIPSpro compilers (version 7.4.x) support C99 features but have a "guard" statement in stdint.h that will #error and skip the rest of the header file if the C99 option is not used explicitly. Hardsetting $CC to c99 will resolve the problem. AKC - 2004/12/13 * On IBM AIX systems, parallel HDF5 mode will fail some tests with error messages like "INFO: 0031-XXX ...". This is from the command poe. Set the environment variable MP_INFOLEVEL to 0 to minimize the messages and run the tests again. The tests may also fail with messages like "The socket name is already in use". HDF5 does not use sockets. This is due to problems of the poe command trying to set up the debug socket. Check whether there are many old /tmp/s.pedb.* files staying around. These are sockets used by the poe command and left behind due to failed commands. Ask your system administrator to clean them out. Lastly, request IBM to provide a means to run poe without the debug socket. * The h5dump tests may fail to match the expected output on some platforms (e.g. parallel jobs, Windows) where the error messages directed to "stderr" do not appear in the "right order" with output from stdout. This is not an error. * The --enable-static-exec configure flag fails to compile for Solaris platforms. This is due to the fact that not all of the system libraries on Solaris are available in a static format. The --enable-static-exec configure flag also fails to correctly compile on the IBM SP2 platform for the serial mode. The parallel mode works fine with this option. The --enable-static-exec configure flag also fails to correctly compile on the HPUX 11.00. It is suggested that you don't use this option on these platforms during configuration. * Use the --disable-shared configure flag if building with an Absoft Fortran compiler. * Information about building with PGI and Intel compilers is available in INSTALL file sections 5.7 and 5.8. * In LANL QSC, the new cc compiler has problems converting small values of long long (absolute values less than 1**-308) to double. This triggers the test/dtypes to report failure in the following test: Testing random sw long double -> double conversions If -ieee is used, the converted doubles spread over the range 0.0 to 10**-308. If -ieee is not used, the converted double values are mostly 0.0, but occasionally appear as 10**-308. This has been reported to the system staff. All other tests have passed. %%%%1.6.7%%%% Release Information for hdf5-1.6.7 (31/January/2008) HDF5 version 1.6.7 released on Thu Jan 31 21:09:10 CST 2008 ================================================================================ INTRODUCTION ============ This document describes the differences between HDF5-1.6.6 and HDF5-1.6.7 It contains information on the platforms tested and known problems in HDF5-1.6.7. For more details, check the HISTORY.txt file in the HDF5 source. HDF5 documentation can be found in the distributed release source code in the subdirectory doc/html/ or on the THG (The HDF Group) FTP server: ftp://ftp.hdfgroup.org/HDF5/docs/ Documentation for the current release in the HDF5 Release 1.6.x series is also on the HDF web site: http://hdfgroup.org/HDF5/doc1.6/ For more information, see the HDF5 home page: http://hdfgroup.org/products/hdf5/ If you have any questions or comments, please see the HDF Support page for a list of available resources: http://hdfgroup.org/services/support.html CONTENTS ======== - New Features - Support for New Platforms, Languages and Compilers - Bug Fixes since HDF5-1.6.6 - Documentation - Platforms Tested - Supported Configuration Features Summary - Known Problems New Features ============ Configuration: ------------------------- '--enable-stream-vfd' and '--disable-stream-vfd' are no longer valid configure options because the stream I/O driver has ben removed from the distribution. Source code distribution ======================== Library: -------- The stream I/O driver is not included with the HDF5 Library in this release. The source code files hdf5/src/H5FDstream.c and hdf5/src/H5FDstream.h and the driver ENUM value H5FD_STREAM have been removed. Parallel Library: ----------------- None Tools: ------ None F90 API: -------- None C++ API: -------- None Support for New Platforms, Languages and Compilers ================================================== No new platorms, languages, or compilers are supported in this release. Bug Fixes since HDF5-1.6.6 Release ================================== Library ------- - H5Iget_name could not be used with an object identifier returned by H5Rdereference; the function would not be able to determine a valid object name. It has been fixed. SLU - 2008/1/30 - Changed library's behavior for reading files that might have corrupted object header information from a previous (buggy) version of the library. By default, the library now rebuilds the correct object header information instead of issuing an error. Previous "strict" file format interpretation can be enabled with the "--enable-strict-format-checks" configure option. QAK - 2008/01/13 - Fixed bug in H5Epush() which was clearing the error stack before pushing new error value. QAK - 2007/08/23 - Fixed bug in H5Ewalk() which was not passing back the return value from error stack walking callback. QAK - 2007/08/23 Configuration ------------- None Performance ------------- None Tools ----- None Documentation ------------- None F90 API ------- None C++ API ------- None Documentation ============= HDF5 documentation can be found in the distributed release source code in the subdirectory doc/html/ (start with index.html) or on the THG (The HDF Group) FTP server: ftp://ftp.hdfgroup.org/HDF5/docs/ Online documentation for the current release in the HDF5 Release 1.6.x series can be found on the THG web site: http://hdfgroup.org/HDF5/doc1.6/ A listing of interface changes from release to release can be found in the document "HDF5 Software Changes from Release to Release": http://hdfgroup.org/HDF5/doc1.6/ADGuide/Changes.html Since the stream I/O driver is not included in this release, the functions H5Pset_fapl_stream and H5Pget_fapl_stream and the stream ENUM value H5FD_STREAM have been removed from the documentation. Platforms Tested ================ AIX 5.2 (32/64 bit) xlc 8.0.0.11 (datastar) xlC 8.0 xlf 10.01.0000.0002 FreeBSD 6.2 (32- and 64-bit) gcc and g++3.4.6 (duty and liberty) gcc and g++ 4.2.1 IRIX64 6.5 MIPSpro cc 7.4.4m (ucar mop1 64 & n32) F90 MIPSpro 7.4.4m (64 only) C++ MIPSpro cc 7.4.4m Linux 2.4.21-47.ELsmp #1 SMP gcc 3.2.3 i686 i386 GNU/Linux (osage) Linux 2.6.9-42.0.10.ELsmp #1 gcc (GCC) 3.4.6 SMP i686 i386 G95 (GCC 4.0.3 (g95 0.91!) April 18 2007) (kagiso) PGI C, Fortran, C++ 7.0-7 32-bit Intel(R) C Compiler for 32-bit applications, Version 9.1 Intel(R) C++ Compiler for 32-bit applications, Version 9.1 Intel(R) Fortran Compiler for 32-bit applications, Version 9.1 Absoft 32-bit Fortran 95 10.0.4 MPICH mpich2-1.0.6p1 compiled with gcc 4.2.1 and G95 (GCC 4.0.3 (g95 0.91!) Linux 2.6.16.46-0.12-debug #1 Intel(R) C++ Version 10.0.025 SMP ia64 GNU/Linux Intel(R) Fortran Itanium(R) Version 10.0.025 (ucar hir1) Linux 2.6.16.46-0.14-smp #1 Intel(R) C++ for Intel(R) EM64T Ver. 9.1.037 SMP x86_64 GNU/Linux Intel(R) Fortran Intel(R) EM64T Ver. 9.1.031 (smirom) PGI C, Fortran, C++ Version 7.0-7 for 64-bit target on x86-64 tested for both 32- and 64-bit binaries Linux 2.6.5-7.287.3-sn2 #1 Intel(R) C++ Version 9.0 Altix SMP ia64 Intel(R) Fortran Itanium(R) Version 9.0 (cobalt) SGI MPI SunOS 5.8 32- and 64-bit Sun WorkShop 6 update 2 C 5.3 (sol) Sun WorkShop 6 update 2 Fortran 95 6.2 Sun WorkShop 6 update 2 C++ 5.3 SunOS 5.10 32- and 64-bit Sun WorkShop 6 update 2 C 5.8 (linew) Sun WorkShop 6 update 2 Fortran 95 8.2 Sun WorkShop 6 update 2 C++ 5.8 Patch 121019-06 Xeon Linux 2.4.21-32.0.1.ELsmp-perfctr-lustre (tungsten) Intel(R) C++ Version 9.0 Intel(R) Fortran Compiler Version 9.0 PGI C Version 6.0-5 PGI C++ Version 6.0-5 PGI Fortran Version 6.0-5 gcc (GCC) 3.2.2 (Red Hat Linux 3.2.2-5) Xeon Linux 2.6.9-42.0.10.EL_lustre-1.4.10.1smp (abe) Intel(R) C++ Version 10.0 Intel(R) Fortran Compiler Version 10.0 Open MPI 1.2.2 IA-64 Linux 2.4.21-309.tg1 #1 SMP ia64 gcc (GCC) 3.2.2 (NCSA tg-login) Intel(R) C++ Version 8.1 Intel(R) Fortran Compiler Version 8.1 mpich-gm-1.2.6..14-intel-r2 Windows XP Visual Studio 6.0 Visual Studio .NET (with Intel Fortran 9.1) Visual Studio 2005 (with Intel Fortran 9.1) cygwin (gcc 3.4.4) Windows Vista Visual studio 2005 MAC OS X Intel Darwin 8.10.1 i686-apple-darwin8-gcc-4.0.1 (GCC) 4.0.1 g95 0.91 Supported Configuration Features Summary ======================================== Key: y = Tested and supported n = Not supported or not tested in this release C = Cluster W = Workstation ( ) = Footnote appears below second table Platform C F90 F90 C++ zlib SZIP parallel parallel Solaris2.8 32-bit n y n y n y Solaris2.8 64-bit n y n n y y Solaris2.10 32-bit n y n y y y Solaris2.10 64-bit n y n n y y IRIX64_6.5 32-bit n n n n y y IRIX64_6.5 64-bit n y n n y y WinXP Visual Studio 6.0 n n n y y y WinXP CYGWIN n n n y y y WinXP 2005 n y n y y y WinXP .Net n y n y y y WinVista 2005 n n n y y y Mac OS X 10.4.10 n y n y y y AIX-5.2 & 5.3 32- and 64-bit y y y y y y FreeBSD 6.2 32- and 64-bit n n n y y y RedHat Linux 2.4.21 W n n n n y n RedHat Linux 2.6.9-42 i686 GNU (1) W y y y y y y RedHat Linux 2.6.9-42 i686 Intel W n y n y y n RedHat Linux 2.6.9-42 i686 PGI W n y n y y n SuSE Linux 2.6.16 x86_64 GNU (1) W y y n y y y SuSE Linux 2.6.16 x86_64 Intel W n y n y y n SuSE Linux 2.6.16 x86_64 PGI W n y n y y n RHEL 4 Linux 2.6.9 Xeon Lustre C n y n y y y RedHat Linux 2.4 Xeon Lustre C n y n y y n SuSE Linux 2.4 ia64 C y y y y y y SuSe Linux 2.6.5 SGI Altix ia64 n y n y y y Platform Shared static- Thread- libraries(4) exec safe Solaris2.8 32- and 64-bit y n y Solaris2.10 32- and 64-bit y n y IRIX64_6.5 32-bit y n y IRIX64_6.5 64-bit y n y WinXP Visual Studio 6.0 y n n WinXP CYGWIN y n n WinXP 2005 y n n WinXP .Net y n n WinVista 2005 y n n Mac OS X 10.4.10 y n n AIX-5.2 & 5.3 32- and 64-bit n n n FreeBSD 6.2 32- and 64-bit y n n RedHat Linux 2.4.21 W y n n SuSE Linux 2.6.9-42 i686 GNU (1) W y n y SuSE Linux 2.6.9-42 i686 Intel W y n n SuSE Linux 2.6.9-42 i686 PGI W n n n SuSE Linux 2.6.16 x86_64 GNU (1) W y n y SuSE Linux 2.6.16 x86_64 Intel W y n n SuSE Linux 2.6.16 x86_64 PGI W n n n RHEL 4 Linux 2.6.9 Xeon Lustre C y n n RedHat Linux 2.4 Xeon Lustre C y n n SuSE Linux 2.4 ia64 C y n n SuSe Linux 2.6.5 SGI Altix ia64 n n n Compiler versions for each platform are listed in the "Platforms Tested" table found elsewhere in this file (RELEASE.txt). Unless otherwise noted, compilers used are the system compilers. Footnotes: (1) Fortran compiled with g95. Known Problems ============== * We discovered two problems when running collective IO parallel HDF5 tests with chunking storage with the ChaMPIon MPI compiler on tungsten, a Linux cluster at NCSA. Under some complex selection cases, 1) MPI_Get_element returns the wrong value. 2) MPI_Type_struct also generates the wrong derived datatype and corrupt data may be generated. This only happens when turning on collective IO with chunking storage with some complex selections. We haven't found these problems on other MPI-IO compilers. If you encounter these problems, you may use Independent IO instead. To avoid this problem, change the following line in your code: H5Pset_dxpl_mpio(xfer_plist, H5FD_MPIO_COLLECTIVE); to H5Pset_dxpl_mpio(xfer_plist, H5FD_MPIO_INDEPENDENT); KY - 2007/08/24 * QSC (an HP alpha-based OSF1 cluster) does not create h5pfc correctly. It does not include the -lmpi properly. This will be fixed in the next release. AKC - 2007/08/07. * On IRIX64 6.5 (UCAR SGI mop1), when testing HDF5 tools with an HDF5 shared library, especially for h5repacktst and h52gifgentst, the following (or a similar) error message may appear: "523648:lt-h5repacktst: rld: Fatal Error: Cannot Successfully map soname 'libh5test.so.1' under any of the filenames .......(bunch of directories) " And the testing will fail. We believe this is a libtool problem. One way to get rid of this is to add the paths of libh5test.so.1 and libh5.so.1 to the shared library path. For 32-bit: You may do this, under csh: setenv LD_LIBRARYN32_PATH .......(existing paths):[full path of HDF5 directory/test/.libs]:[full path of HDF5 directory/src/.libs] For 64-bit: setenv LD_LIBRARY64_PATH ......(existing paths):[full path of HDF5 directory/test/.libs]:[full path of HDF5 directory/src/.libs] NOTE: This problem ONLY affects the testing of the HDF5 library when you build from source. It won't affect any applications that would like to link with the HDF5 shared library since the shared library path needs to be set anyway. KY - 2007/8/2 * QSC (an HP alpha-based OSF1 cluster) failed the testpar/testphdf5 sub-test "calloc". All other tests passed. This indicates that a dataset using chunked storage created by serial HDF5 may not work properly with parallel HDF5. The calloc test can be skipped by running "prun ... testphdf5 -x calloc". AKC - 2007/7/12. * The Intel C Compiler for the Linux x86_64 platform (EM64T-based, v8.1) has an optimization error in the datatypes conversion code. Before running configure, edit the file config/intel-flags by changing the setting of PROD_CFLAGS from -O3 to -O0. Then run configure. AKC - 2005/11/10. * When testing parallel HDF5 with the C compiler version MIPSpro 7.4.3 on IRIX 6.5, set the environment variable MPI_TYPE_MAX to be a bigger number, for example 120000, in order to pass the complicated collective IO tests inside the parallel HDF5 library. This is not a problem inside the parallel HDF5 library. You can always set a bigger number on your system. KY - 2005/10/6 * A contiguous or chunked dataset created by a sequential version of HDF5 might not be able to be modified with a parallel version of the library. Use the H5Pset_alloc_time function with H5D_ALLOC_TIME_EARLY to set up the dataset creation property list to avoid the problem. EIP - 2005/09/09 * A dataset created or rewritten with the v1.6.3 library or after can't be read with the v1.6.2 library or before when Fletcher32 EDC (a filter) is enabled. There was a bug in the calculating code of the Fletcher32 checksum in the library before v1.6.3. The checksum value wasn't consistent between big-endian and little-endian systems. This bug was fixed in Release 1.6.3. However, after fixing the bug, the checksum value is no longer the same as before on little-endian system. HDF5 library releases after 1.6.4 can still read datasets created or rewritten with an HDF5 library of v1.6.2 or before. SLU - 2005/7/8 * For version 6 (6.02 and 6.04) of the Portland Group compiler on AMD Opteron processor, there's a bug in the compiler for optimization(-O2). The library failed in several tests, all related to the multi driver. The problem has been reported to the vendor. * test/big fails sometimes with the message "Possible overlap with another region." The test selects regions randomly, and this error occurs when two regions overlap each other; it is a bug in the test and not in HDF5. Since the error is triggered by a random situation, it will usually disappear if the test is re-run. * Newer SGI MIPSpro compilers (version 7.4.x) support C99 features but have a "guard" statement in stdint.h that will #error and skip the rest of the header file if the C99 option is not used explicitly. Hardsetting $CC to c99 will resolve the problem. AKC - 2004/12/13 * On IBM AIX systems, parallel HDF5 mode will fail some tests with error messages like "INFO: 0031-XXX ...". This is from the command poe. Set the environment variable MP_INFOLEVEL to 0 to minimize the messages and run the tests again. The tests may also fail with messages like "The socket name is already in use". HDF5 does not use sockets. This is due to problems of the poe command trying to set up the debug socket. Check whether there are many old /tmp/s.pedb.* files staying around. These are sockets used by the poe command and left behind due to failed commands. Ask your system administrator to clean them out. Lastly, request IBM to provide a means to run poe without the debug socket. * The h5dump tests may fail to match the expected output on some platforms (e.g. parallel jobs, Windows) where the error messages directed to "stderr" do not appear in the "right order" with output from stdout. This is not an error. * The --enable-static-exec configure flag fails to compile for Solaris platforms. This is due to the fact that not all of the system libraries on Solaris are available in a static format. The --enable-static-exec configure flag also fails to correctly compile on the IBM SP2 platform for the serial mode. The parallel mode works fine with this option. The --enable-static-exec configure flag also fails to correctly compile on the HPUX 11.00. It is suggested that you don't use this option on these platforms during configuration. * Use the --disable-shared configure flag if building with an Absoft Fortran compiler. * Information about building with PGI and Intel compilers is available in INSTALL file sections 5.7 and 5.8. * In LANL QSC, the new cc compiler has problems converting small values of long long (absolute values less than 1**-308) to double. This triggers the test/dtypes to report failure in the following test: Testing random sw long double -> double conversions If -ieee is used, the converted doubles spread over the range 0.0 to 10**-308. If -ieee is not used, the converted double values are mostly 0.0, but occasionally appear as 10**-308. This has been reported to the system staff. All other tests have passed. * On at least one system, SDSC DataStar, the scheduler (in this case LoadLeveler) sends job status updates to standard error when you run any executable that was compiled with the parallel compilers. This causes problems when running "make check" on parallel builds, as many of the tool tests function by saving the output from test runs, and comparing it to an exemplar. The best solution is to reconfigure the target system so it no longer inserts the extra text. However, this may not be practical. In such cases, one solution is to "setenv HDF5_Make_Ignore yes" prior to the configure and build. This will cause "make check" to continue after detecting errors in the tool tests. However, in the case of SDSC DataStar, it also leaves you with some 150 "failed" tests to examine by hand. A second solution is to write a script to run serial tests and filter out the text added by the scheduler. A sample script used on SDSC DataStar is given below, but you will probably have to customize it for your installation. Observe that the basic idea is to insert the script as the first item on the command line which executes the test. The script then executes the test and filters out the offending text before passing it on. #!/bin/csh set STDOUT_FILE=~/bin/serial_filter.stdout set STDERR_FILE=~/bin/serial_filter.stderr rm -f $STDOUT_FILE $STDERR_FILE ($* > $STDOUT_FILE) >& $STDERR_FILE set RETURN_VALUE=$status cat $STDOUT_FILE tail +3 $STDERR_FILE exit $RETURN_VALUE You get the HDF5 make files and test scripts to execute your filter script by setting the environment variable "RUNSERIAL" to the full path of the script prior to running configure for parallel builds. Remember to "unsetenv RUNSERIAL" before running configure for a serial build. Note that the RUNSERIAL environment variable exists so that we can prefix serial runs as necessary on the target system. On DataStar, no prefix is necessary. However, on an MPICH system, the prefix might have to be set to something like "/usr/local/mpi/bin/mpirun -np 1" to get the serial tests to run at all. In such cases, you will have to include the regular prefix in your filter script. JM - 2004/9/15 %%%%1.6.6%%%% Release Information for hdf5-1.6.6 (16/August/07) HDF5 version 1.6.6 released on Thu Aug 16 11:17:10 CDT 2007 ================================================================================ INTRODUCTION ============ This document describes the differences between HDF5-1.6.5 and HDF5-1.6.6 It contains information on the platforms tested and known problems in HDF5-1.6.6. For more details, check the HISTORY.txt file in the HDF5 source. HDF5 documentation can be found in the distributed release source code in the subdirectory doc/html/ or on the THG (The HDF Group) ftp server (ftp.hdfgroup.org) in the directory: /HDF5/docs/ Documentation for the current release is also on the HDF web site: http://hdfgroup.org/HDF5/doc/ For more information, see the HDF5 home page at: http://hdfgroup.org/HDF5/ If you have any questions or comments, please send them to: help@hdfgroup.org CONTENTS ======== - New Features - Support for New Platforms, Languages and Compilers - Bug Fixes since HDF5-1.6.5 - Documentation - Platforms Tested - Supported Configuration Features Summary - Known Problems New Features ============ Configuration: ------------------------- - HDF5 now uses autoconf 2.61 to generate configure. MAM - 2007/7/25. Source code distribution ======================== Library: -------- - None Parallel Library: ----------------- - None Tools: ------ - h52gif and gif2h5: Both these tools were revised to include High Level Image API support. Tests were added to /hl/tools/gif2h5. PVN - 2007/04/13 - h5dump: Added support for double long type H5T_NATIVE_LDOUBLE. PVN - 2007/03/13 - h5dump: Added support for binary output; see usage. PVN 2007/03/13 - h5repack: Added support for reading and writing by hyperslabs for large files. PVN - 2007/03/01 - h5repack: A new option allows the copy to use the source file type (default) instead of the previous conversion to native type. PVN - 2007/03/01 - h5repack: Added output of the percentage of compression achieved. PVN - 2007/03/01 - h5diff: Added support for comparing dataset regions. PVN - 2007/02/20 - h5diff: Added support for reading and comparing by hyperslabs for large files. PVN - 2007/02/20 - h5diff: Added printing of dataset dimensions along with dataset name. PVN - 2007/02/19 F90 API: -------- - None C++ API: -------- - Added support for Szip: DSetCreatPropList::setSzip - BMR 2007/01/24 Support for New Platforms, Languages and Compilers ================================================== - Added support for MAC Intel (Darwin 8.8.2) (gcc 4.0.1 and g95 0.91) EIP - 2007/02/13 - Added support for GNU C compiler version 4.2.1 for FreeBSD 6.2 (32- and 64-bit) Bug Fixes since HDF5-1.6.5 Release ================================== Library ------- - Fixed several bugs with writing fill values for datasets that have a variable-length datatype or component datatype. QAK - 2007/06/19 - STDIO driver didn't support files bigger than 2GB because the OFFSET parameter of fseek is of type LONG INT, not big enough for big files. Use fseeko instead for big files if it's available on the system. SLU - 2007/4/5 - Relaxed restrictions on attribute operations to allow a file ID to be used as the "location ID". If a file ID is used, the attribute operation will occur on the root group of the file. QAK - 2007/02/09 - Fixed a bug in H5Sselect_valid() that caused an incorrect value to be returned (0) instead of FAIL on error conditions such as the selection or extent not being defined. CMC - 2007/01/05 - Fixed potential file corruption bug which could overwrite a portion of an object's header when an attribute was renamed. If the new name for the attribute was longer than the old name, it was possible that the attribute would grow enough to overwrite another message in the object's header. QAK - 2007/01/02 - Fixed file corruption bug which could write an incorrect number of messages to an object's header under certain circumstances. Generally, the sequence of actions to generate this bug looks like this: - Create an object. - Close the file. - Re-open the file. - Add 2 (or more) attributes to the object. - Close the file. - Re-open the file. - Delete one of the attributes on the object. - Add a smaller attribute to the object. - Delete the smaller atttribute on the object. - Add a larger attribute on the object. After this, the number of header messages stored for the object will be off by one. Other sequences of modifying attributes on an object could also trigger this bug. If you are opening an object and the bottom few messages of the HDF5 error stack resembles the following, the object has been affected by this bug: #007: ../../hdf5_v1.6/src/H5C.c line 3887 in H5C_load_entry(): unable to load entry major(08): Meta data cache layer minor(40): Unable to load metadata into cache #008: ../../hdf5_v1.6/src/H5Ocache.c line 332 in H5O_load(): corrupt object header - too few messages major(12): Object header layer minor(40): Unable to load metadata into cache Specifically, "corrupt object header" is the best string to search for in the HDF5 error stack output. If your files have been affected by this bug, or you are concerned that your files might have been, please contact the HDF Helpdesk at help@hdfgroup.org for a tool to detect and repair files affected by this problem. QAK - 2006/6/16 - Fixed various problems with retrieving names of objects, especially with mounted files. QAK - 2005/12/25 Configuration ------------- - Changed to default to --disable-shared if parallel is enabled. AKC - 2007/5/12 - Corrected a coding error in configure when it tries to locate the needed MPI and MPI-IO library for the fortran interface. AKC - 007/5/9. - Changed default fortran compiler to g95 when gcc is used. AKC - 007/2/17. - Configure can now use any tr command. No more need for defining the variable TR, nor is it supported. AKC - 2006/05/20 Performance ------------- - None Tools ----- - Fixed a bug in h5dump regarding the display of named datatypes attributes. PVN - 2007/03/13 - Fixed a bug in h5dump regarding the display of group comments. PVN - 2007/03/13 - Fixed a bug in h5dump regarding the display of hardlinks pointing to the root group. PVN - 2007/03/13 - Fixed a bug in the h5diff percentage option -p. PVN - 2007/03/05 - Fixed a bug in h5dump that caused array indices greater than 2^32-1 not to be printed correctly. PVN - 2007/2/19 Documentation ------------- - Corrected errors and extended the descriptions in Reference Manual entries for several functions. F90 API ------- - None C++ API ------- - Changed StrType::StrType(const size_t& size); to StrType::StrType(const int dummy, const size_t& size); because the first one clashed with StrType::StrType(const hid_t existing_id); - BMR 2007/05/03 - Wrappers of H5Rcreate had incorrect prototypes. Added these overloaded functions: IdComponent::reference(void* ref, const char* name, DataSpace& dataspace, H5R_type_t ref_type = H5R_DATASET_REGION) IdComponent::void reference(void* ref, const char* name) IdComponent::reference(void* ref, const H5std_string& name) and will remove these incorrect member functions: DataSet::Reference DataType::Reference Group::Reference H5File::Reference - Added wrappers for H5Rdereference as constructors: DataSet(IdComponent& obj, void* ref); Group(IdComponent& obj, void* ref); DataType(IdComponent& obj, void* ref); Documentation ============= HDF5 documentation can be found in the distributed release source code in the subdirectory doc/html/ (start with index.html) or on the THG (The HDF Group) ftp server (ftp.hdfgroup.org) in the directory: /HDF5/docs/ Online documentation for the current release can be found on the THG web site: http://hdfgroup.org/HDF5/doc/ Platforms Tested ================ AIX 5.2 (32/64 bit) xlc 6.0.0.8 (datastar) xlC 6.0.0.9 xlf 8.1.1.7 mpcc_r 6.0.0.8 mpxlf_r 8.1.1.7 AIX 5.3 (32/64 bit) xlc 7.0.0.0 (copper) xlC 7.0. xlf 9.1.0.3 FreeBSD 6.2 (32- and 64-bit) gcc and g++3.4.6 (duty and liberty) gcc and g++ 4.2.1 HP-UX B.11.23 HP aC++/ANSI C B3910B A.06.02 (sirius) HP F90 v3.1 (32-bit only) HP aC++/ANSI C B3910B A.06.02 IRIX64 6.5 MIPSpro cc 7.4.4m (ucar mop1 64 & n32) F90 MIPSpro 7.4.4m (64 only) C++ MIPSpro cc 7.4.4m Linux 2.4.21-47.ELsmp #1 SMP gcc 3.2.3 i686 i386 GNU/Linux (osage) Linux 2.6.9-42.0.10.ELsmp #1 gcc (GCC) 3.4.6 SMP i686 i386 G95 (GCC 4.0.3 (g95 0.91!) Nov 21 2006) (kagiso) PGI C, Fortran, C++ 6.2-5 32-bit icc (ICC) 9.1 Intel(R) C++ Compiler for 32-bit applications, Version 9.1 Intel(R) Fortran Compiler for 32-bit applications, Version 9.1 Absoft 32-bit Fortran 95 10.0.4 MPICH mpich2-1.0.4p1 compiled with gcc 3.4.6 and G95 (GCC 4.0.3 (g95 0.91!) Linux 2.6.16.46-0.12-debug #1 SMP ia64 GNU/Linux Intel(R) C++ Version 10.0.025 (ucar hir1) Intel(R) Fortran Itanium(R) Version 10.0.025 Linux 2.6.16.46-0.14-smp #1 Intel(R) C++ for Intel(R) EM64T Ver. 9.1.037 SMP x86_64 GNU/Linux Intel(R) Fortran Intel(R) EM64T Ver. 9.1.031 (smirom) PGI C, Fortran, C++ Version 6.2-5 for 64-bit target on x86-64 tested for both 32- and 64-bit binaries Linux 2.6.5-7.283-rtgfx Altix SMP ia64 Intel(R) C++ Version 9.0 (cobalt) Intel(R) Fortran Itanium(R) Version 9.0 SGI MPI OSF1 V5.1 (QSC) Compaq C V6.5-011 (See "Known Problems.") HP Fortran V5.5A-3548 Compaq C++ V6.5-036 MPIX200_64_r13.4 SunOS 5.8 32- and 64-bit Sun WorkShop 6 update 2 C 5.3 (sol) Sun WorkShop 6 update 2 Fortran 95 6.2 Sun WorkShop 6 update 2 C++ 5.3 SunOS 5.10 32- and 64-bit Sun WorkShop 6 update 2 C 5.8 (linew) Sun WorkShop 6 update 2 Fortran 95 8.2 Sun WorkShop 6 update 2 C++ 5.8 Patch 121019-06 Xeon Linux 2.4.21-32.0.1.ELsmp-perfctr-lustre (tungsten) Intel(R) C++ Version 9.0 Intel(R) Fortran Compiler Version 9.0 PGI C Version 6.0 PGI C++ Version 6.0 PGI Fortran Version 6.0 gcc (GCC) 3.2.2 (Red Hat Linux 3.2.2-5) Xeon Linux 2.6.9-42.0.10.EL_lustre-1.4.10.1smp (abe) Intel(R) C++ Version 10.0 Intel(R) Fortran Compiler Version 10.0 Open MPI 1.2.2 IA-64 Linux 2.4.21.SuSE_292.til1 ia64 gcc (GCC) 3.2.2 (NCSA tg-login) Intel(R) C++ Version 8.0 Intel(R) Fortran Compiler Version 8.0 mpich-gm-1.2.5..10-intel-r2 Windows XP Visual Studio 6.0 Visual Studio .NET (with Intel Fortran 9.0) Visual Studio 2005 (with Intel Fortran 9.0) cygwin (gcc 3.4.4) MAC OS X Intel Darwin 8.10.1 i686-apple-darwin8-gcc-4.0.1 (GCC) 4.0.1 g95 0.91 Supported Configuration Features Summary ======================================== Key: y = Tested and supported n = Not supported or not tested in this release C = Cluster W = Workstation ( ) = Footnote appears below second table Platform C F90 F90 C++ zlib SZIP parallel parallel Solaris2.8 32- and 64-bit n y n y y y Solaris2.10 32- and 64-bit n y n y y y IRIX64_6.5 32-bit n n n n y y IRIX64_6.5 64-bit n y n n y y HPUX11.23-32bit n y n y y y HPUX11.23-64bit n n n y y y WinXP Visual Studio 6.0 n n n y y y WinXP CYGWIN n n n y y y WinXP 2005 n y n y y y WinXP .Net n y n y y y Mac OS X 10.4.10 n y n y y y AIX-5.2 & 5.3 32- and 64-bit y y y y y y FreeBSD 6.2 32- and 64-bit n n n y y y RedHat Linux 2.4.21 W n n n y y y SuSE Linux 2.6.9-42 i686 GNU (1) W y y y y y y SuSE Linux 2.6.9-42 i686 Intel W n y n y y y SuSE Linux 2.6.9-42 i686 PGI W n y n y y y SuSE Linux 2.6.16 x86_64 GNU (1) W y y y y y y SuSE Linux 2.6.16 x86_64 Intel W n y n y y y SuSE Linux 2.6.16 x86_64 PGI W n y n y y y RHEL 4 Linux 2.6.9 Xeon Lustre C y y y y y y RedHat Linux 2.4 Xeon Lustre C n y n y y y SuSE Linux 2.4 ia64 C y y y y y y SuSe Linux 2.6.16 SGI Altix ia64 n y n y y y SuSe Linux 2.6.5 SGI Altix ia64 n y n y y y OSF1 v5.1 y y y y y n Platform Shared static- Thread- STREAM- libraries(4) exec safe VFD Solaris2.8 32- and 64-bit y n y y Solaris2.10 32- and 64-bit y n y y IRIX64_6.5 32-bit y n y y IRIX64_6.5 64-bit y n y y HPUX11.23-32bit y (3) n n y HPUX11.23-64bit y (3) n n y WinXP Visual Studio 6.0 y n n n WinXP CYGWIN y n n n WinXP 2005 y n n n WinXP .Net y n n n Mac OS X 10.4.10 y n n y AIX-5.2 & 5.3 32- and 64-bit n n n y FreeBSD 6.2 32- and 64-bit y n n y RedHat Linux 2.4.21 W y n n y SuSE Linux 2.6.9-42 i686 GNU (1) W y n y y SuSE Linux 2.6.9-42 i686 Intel W y n n y SuSE Linux 2.6.9-42 i686 PGI W n n n y SuSE Linux 2.6.16 x86_64 GNU (1) W y n n y SuSE Linux 2.6.16 x86_64 Intel W y n n y SuSE Linux 2.6.16 x86_64 PGI W n n n y RHEL 4 Linux 2.6.9 Xeon Lustre C y n n y RedHat Linux 2.4 Xeon Lustre C y n n y SuSE Linux 2.4 ia64 C y n n y SuSe Linux 2.6.16 SGI Altix ia64 n n n y SuSe Linux 2.6.5 SGI Altix ia64 n n n y OSF1 v5.1 n n n y Compiler versions for each platform are listed in the "Platforms Tested" table found elsewhere in this file (RELEASE.txt). Unless otherwise noted, compilers used are the system compilers. Footnotes: (1) Fortran compiled with g95. (2) In most cases, shared libraries are provided only for the C library, except on Windows where they are provided for C, C++, and Fortran. (3) C++ works only with static libraries. Known Problems ============== * QSC (an HP alpha-based OSF1 cluster) does not create h5pfc correctly. It does not include the -lmpi properly. This will be fixed in the next release. AKC - 2007/08/07. * On IRIX64 6.5 (UCAR SGI mop1), when testing HDF5 tools with an HDF5 shared library, especially for h5repacktst and h52gifgentst, the following (or similar) error message may appear: "523648:lt-h5repacktst: rld: Fatal Error: Cannot Successfully map soname 'libh5test.so.1' under any of the filenames .......(bunch of directories) " And the testing will fail. We believe this is a libtool problem. One way to get rid of this is to add the paths of libh5test.so.1 and libh5.so.1 to the shared library path. For 32-bit: You may do this, under csh: setenv LD_LIBRARYN32_PATH .......(existing pathes):[full path of HDF5 directory/test/.libs]:[full path of HDF5 directory/src/.libs] For 64-bit: setenv LD_LIBRARY64_PATH ......(existing pathes):[full path of HDF5 directory/test/.libs]:[full path of HDF5 directory/src/.libs] NOTE: This problem ONLY affects the testing of the HDF5 library when you build from source. It won't affect any applications that would like to link with the HDF5 shared library since the shared library path needs to be set anyway. KY - 2007/8/2 * QSC (an HP alpha-based OSF1 cluster) failed the testpar/testphdf5 sub-test "calloc". All other tests passed. This indicates that a dataset using chunked storage created by serial HDF5 may not work properly with parallel HDF5. The calloc test can be skipped by running "prun ... testphdf5 -x calloc". AKC - 2007/7/12. * The Intel C Compiler for the Linux x86_64 platform (EM64T-based, v8.1) has an optimization error in the datax types conversion code. Before running configure, edit the file config/intel-flags by changing the setting of PROD_CFLAGS from -O3 to -O0. Then run configure. AKC - 2005/11/10. * When testing parallel HDF5 with the C compiler version MIPSpro 7.4.3 on IRIX 6.5, set the environment variable MPI_TYPE_MAX to be a bigger number, for example 120000, in order to pass the complicated collective IO tests inside the parallel HDF5 library. This is not a problem inside the parallel HDF5 library. You can always set a bigger number on your system. KY - 2005/10/6 * A contiguous or chunked dataset created by a sequential version of HDF5 might not be able to be modified with a parallel version of the library. Use the H5Pset_alloc_time function with H5D_ALLOC_TIME_EARLY to set up the dataset creation property list to avoid the problem. EIP - 2005/09/09 * The dataset created or rewritten with the v1.6.3 library or after can't be read with the v1.6.2 library or before when Fletcher32 EDC (a filter) is enabled. There was a bug in the calculating code of the Fletcher32 checksum in the library before v1.6.3. The checksum value wasn't consistent between big-endian and little-endian systems. This bug was fixed in Release 1.6.3. However, after fixing the bug, the checksum value is no longer the same as before on little-endian system. The library release after 1.6.4 can still read the dataset created or rewritten with the library of v1.6.2 or before. SLU - 2005/7/8 * For version 6 (6.02 and 6.04) of the Portland Group compiler on AMD Opteron processor, there's a bug in the compiler for optimization(-O2). The library failed in several tests, all related to the multi driver. The problem has been reported to the vendor. * test/big fails sometimes with the message "Possible overlap with another region." The test selects regions randomly, and this error occurs when two regions overlap each other; it is a bug in the test and not in HDF5. Since the error is triggered by a random situation, it will usually disappear if the test is re-run. * Newer SGI MIPSpro compilers (version 7.4.x) support C99 features but have a "guard" statement in stdint.h that will #error and skip the rest of the header file if the C99 option is not used explicitly. Hardsetting $CC to c99 will resolve the problem. AKC - 2004/12/13 * On IBM AIX systems, parallel HDF5 mode will fail some tests with error messages like "INFO: 0031-XXX ...". This is from the command poe. Set the environment variable MP_INFOLEVEL to 0 to minimize the messages and run the tests again. The tests may also fail with messages like "The socket name is already in use". HDF5 does not use sockets (except for stream-VFD). This is due to problems of the poe command trying to set up the debug socket. Check whether there are many old /tmp/s.pedb.* files staying around. These are sockets used by the poe command and left behind due to failed commands. Ask your system administrator to clean them out. Lastly, request IBM to provide a means to run poe without the debug socket. * The h5dump tests may fail to match the expected output on some platforms (e.g. parallel jobs, Windows) where the error messages directed to "stderr" do not appear in the "right order" with output from stdout. This is not an error. * The stream-vfd test uses ip port 10007 for testing. If another application is already using that port address, the test will hang indefinitely and has to be terminated by the kill command. To try the test again, change the port address in test/stream_test.c to one not being used in the host. * The --enable-static-exec configure flag fails to compile for Solaris platforms. This is due to the fact that not all of the system libraries on Solaris are available in a static format. The --enable-static-exec configure flag also fails to correctly compile on the IBM SP2 platform for the serial mode. The parallel mode works fine with this option. The --enable-static-exec configure flag also fails to correctly compile on the HPUX 11.00. It is suggested that you don't use this option on these platforms during configuration. * The Stream VFD is not supported under Windows. * Use the --disable-shared configure flag if building with Absoft Fortran compiler. * Information about building with PGI and Intel compilers is available in INSTALL file sections 5.7 and 5.8. * In LANL QSC, the new cc compiler has problems converting small values of long long (absolute values less than 1**-308) to double. This triggers the test/dtypes to report failure in the following test: Testing random sw long double -> double conversions If -ieee is used, the converted doubles spread over the range 0.0 to 10**-308. If -ieee is not used, the converted double values are mostly 0.0, but occasionally appear as 10**-308. This has been reported to the system staff. All other tests have passed. * On at least one system, SDSC DataStar, the scheduler (in this case LoadLeveler) sends job status updates to standard error when you run any executable that was compiled with the parallel compilers. This causes problems when running "make check" on parallel builds, as many of the tool tests function by saving the output from test runs, and comparing it to an exemplar. The best solution is to reconfigure the target system so it no longer inserts the extra text. However, this may not be practical. In such cases, one solution is to "setenv HDF5_Make_Ignore yes" prior to the configure and build. This will cause "make check" to continue after detecting errors in the tool tests. However, in the case of SDSC DataStar, it also leaves you with some 150 "failed" tests to examine by hand. A second solution is to write a script to run serial tests and filter out the text added by the scheduler. A sample script used on SDSC DataStar is given below, but you will probably have to customize it for your installation. Observe that the basic idea is to insert the script as the first item on the command line which executes the test. The script then executes the test and filters out the offending text before passing it on. #!/bin/csh set STDOUT_FILE=~/bin/serial_filter.stdout set STDERR_FILE=~/bin/serial_filter.stderr rm -f $STDOUT_FILE $STDERR_FILE ($* > $STDOUT_FILE) >& $STDERR_FILE set RETURN_VALUE=$status cat $STDOUT_FILE tail +3 $STDERR_FILE exit $RETURN_VALUE You get the HDF5 make files and test scripts to execute your filter script by setting the environment variable "RUNSERIAL" to the full path of the script prior to running configure for parallel builds. Remember to "unsetenv RUNSERIAL" before running configure for a serial build. Note that the RUNSERIAL environment variable exists so that we can prefix serial runs as necessary on the target system. On DataStar, no prefix is necessary. However, on an MPICH system, the prefix might have to be set to something like "/usr/local/mpi/bin/mpirun -np 1" to get the serial tests to run at all. In such cases, you will have to include the regular prefix in your filter script. JM - 2004/9/15 %%%%1.6.5%%%% Release Information for hdf5-1.6.5 (10/November/05) HDF5 version 1.6.5 released on Thu Nov 10 18:17:53 CST 2005 ================================================================================ INTRODUCTION ============ This document describes the differences between HDF5-1.6.4 and HDF5-1.6.5. It contains information on the platforms tested and known problems in HDF5-1.6.5. For more details, check the HISTORY.txt file in the HDF5 source. The HDF5 documentation can be found on the NCSA ftp server (ftp.ncsa.uiuc.edu) in the directory: /HDF/HDF5/docs/ Documentation for the current release is also on the HDF web site: http://hdf.ncsa.uiuc.edu/HDF5/doc/ For more information look at the HDF5 home page at: http://hdf.ncsa.uiuc.edu/HDF5/ If you have any questions or comments, please send them to: hdfhelp@ncsa.uiuc.edu CONTENTS ======== - New Features - Support for New Platforms, Languages and Compilers - Bug Fixes since HDF5-1.6.4 - Documentation - Platforms Tested - Supported Configuration Features Summary - Known Problems New Features ============ Configuration: ------------------------- - Added yodconfigure, a configure tool, that patches up the configure file to allow configure to launch executable via the proper launching command like "yod -sz 1". AKC - 2005/11/10 - Configure now recognizes the TR variable as the location of the tr utility. JML 2005/10/20 Source code distribution: ------------------------- - Added g95 as a testing "platform" informally. AKC - 2005/10/04. - Added MD5 checksumming to snapshot releases. Releases will now produce an .md5 file as well as a .tar archive. md5sum can be used to verify the arvhice with the .md5 checksum. -JL 2005/09/06 Library: -------- - Added HSYS_ERROR which retrieves the system error message and pushes it to the error stack. This provides more information regarding the failed system call. AKC - 2005/08/04 - Added H5F_OBJ_LOCAL flag to H5Fget_obj_count() & H5Fget_obj_ids(), to allow querying for objects in a file that was opened with a particular file ID, instead of all objects opened in the file with any file ID. QAK - 2005/06/01 Parallel Library: ----------------- - Added mpich2 as a testing "platform" informally. AKC - 2005/10/04. - HDF5 supports collective MPI-IO for irregular selection with HDF5 dataset. Irregular selection is when users use API H5Sselect_hyperslab more than once for the same dataset. Currently, not all MPI-IO packages support the complicated MPI derived datatypes used in the implementation of irregular selections INSIDE HDF5. 1) DEC 5.x wdoes not support complicated derived datatypes. 2) For AIX 5.1: If your poe version number is 3.2.0.20 or lower, please edit powerpc-ibm-aix5.x in the directory hdf5/config/. Find the line with << hdf5_mpi_complex_derived_datatype_works >> and UNCOMMENT this line before the configure. check poe version with the following command: lpp -l all | grep ppe.poe 3) For Linux cluster,: If mpich version is 1.2.5 or lower, collective irregular selection IO is not supported; internally independent IO is used. 4) For IRIX 6.5: if C compiler version is 7.3 or lower, collective irregular selection IO is not supported; internally independent IO is used. 5) For platforms which internally used mpich: If the mpich version is 1.2.5 or lower, please find the corresponding config (in hdf5/config) file and add hdf5_mpi_complex_derived_datatype_works='no' at the end of the configuration file. For example, on the NCSA SGI Altix, the internal mpich library is 1.2.5. So hdf5_mpi_complex_derived_datatype_works='no' should be added at the end of the config file ia64-linux-gnu. KY - 2005/09/12 Tools: ------ - Removed obsolete pdb2hdf tool. JML - 2005/10/28 - Sped up h5dump on files with large numbers of objects. QAK - 2005/08/25 F90 API: -------- - Added missing h5tget_member_class_f function EIP 2005/04/06 C++ API: -------- - Added missing member functions: H5::CompType::getMemberArrayType H5::CompType::getMemberVarLenType H5::AbstractDs::getArrayType H5::AbstractDs::getVarLenType H5::CommonFG::openArrayType H5::CommonFG::openVarLenType H5::PropList::copyProp -- this will replace the current H5::PropList::copyProp in later releases due to incorrect prototype. BMR - 2005/07/27 Support for New Platforms, Languages and Compilers ================================================== - Added support for RedStorm platform (serial only.) AKC 2005/11/10 - Added support for BG/L platform (serial only.) LA 2005/11/10 - Added support for HPUX 11.23 (IA64); only C and C++ are supported with the +DD64 flag EIP 2005/10/05 Configuration ------------- - Added support for Cray X1. JML 2005/10/03 Bug Fixes since HDF5-1.6.4 Release ================================== Library ------- - Fixed collective IO in chunking-storage. HDF5 may have called the wrong routine when the shape of the dataspace in the file and in the bufferred chunk were different. This bug was fixed to make sure the correct routine is called. KY - 2005/10/19 - Fixed core dump when closing root groups opened through two different file handles that operate on the same actual file. QAK - 2005/10/02 - The ./dsets tests used to fail in the TFLOPS machine if the test program, dsets.c, was compiled with the -O option. The HDF5 library still worked correctly with the -O option. Only the ./dsets failed. It is fixed. AKC - 2005/09/14 - Corrected errors when performing various operations on a group opened by dereferencing an object reference. QAK - 2005/07/30 - Fixed a bug with named datatypes where a copy of a named datatype used to create a dataset would accidentally use the original named datatype for the dataset's datatype. QAK - 2005/07/23 - Made H5Fget_name() to be consistent and always return name of actual file the ID is in. (Instead of the name of the top file in a file mounting hierarchy). QAK - 2005/07/19 - Reworked internal file mounting semantics to hopefully eliminate mounting problems. We now require that files that are mounting together all have the same "file close degree". QAK - 2005/07/19 - More bug fixes on holding open files that are mounted and have IDs open. QAK - 2005/07/14 - Dataset sieve buffer cache was inadvertantly disabled; it has been re-enabled. QAK - 2005/07/08 - Don't unmount child files until the parent file actually closes. (Previously, if an object was holding open a file, the child files would get unmounted too early). QAK - 2005/07/05 - Fixed bug where unmounted files could cause the library to go into an infinite loop when shutting down. QAK - 2005/06/30 - Fixed bug with hyperslab selections that use selection offsets and operate on chunked datasets going into infinite loop or dumping core. QAK - 2005/06/17 - Corrected memory leak and possible corruption when opening a group. QAK - 2005/06/17 - Added check for opaque datatype tags being too long (check against H5T_OPAQUE_TAG_MAX, currently set to 256). QAK - 2005/06/14 - Fixed various errors in maintaining names for open objects in the face of unusual mount & unmount operations. QAK - 2005/06/08 - "SEMI" and "STRONG" file close degree settings now apply only to the particular file ID being closed, instead of operating on all open file IDs for a given file. QAK - 2005/06/01 - Fixed error in opening object in a group that was opened in a mounted file which has been unmounted. QAK - 2005/03/17 Configuration ------------- - Configure can recognize -lmpich as a form of MPI library. -AKC- 2005/9/28. - Changed default C++ compiler for the IA64 platform from icc to icpc which is the preferred compiler for Intel Compiler version 8. AKC - 2005/09/02 Performance ------------- - Optimized I/O for enumerated datatypes that are a superset of a source enumerated datatype. QAK - 2005/03/19 Tools ----- Documentation ------------- F90 API ------- - h5pget_driver_f was returning information that could not be interpreted by a Fortran application program; fixed. EIP - 2005/04/10 C++ API ------- - Several member functions' prototype changed due to the "int -> unsigned" change in the main library. They are: H5::CompType::getMemberDataType(unsigned member_num) H5::CompType::getMemberCompType(unsigned member_num) H5::CompType::getMemberEnumType(unsigned member_num) H5::CompType::getMemberIntType(unsigned member_num) H5::CompType::getMemberFloatType(unsigned member_num) H5::CompType::getMemberStrType(unsigned member_num) BMR - 2005/07/27 Platforms Tested ================ AIX 5.1 (32 and 64-bit) xlc 6.0.0.6 xlf 8.1.1.3 xlC 6.0.0.6 mpcc_r 6.0.0.6 mpxlf_r 8.1.1.3 xlc 5.0.2.5 xlf 7.1.1.2 xlC 5.0.2.5 mpcc_r 5.0.2.5 mpxlf_r 7.1.1.2 AIX 5.2 (32/64 bit) xlc 6.0.0.8 xlC 6.0.0.9 xlf 8.1.1.7 mpcc_r 6.0.0.8 mpxlf_r 8.1.1.7 AIX 5.2 (32/64 bit, LLNL frost) xlc 6.0.0.8 xlC 6.0.0.8 xlf 8.1.1.7 mpcc_r 6.0.0.8 mpxlf_r 8.1.1.7 AIX 5.3 (32/64 bit) xlc 7.0.0.0 xlC 7.0. xlf 9.1.0.3 Cray X1 water 3.0.35 Cray Standard C Version 5.4.0.7.4 Cray Fortran 5.4.0.7.3 Cray C++ 5.4.0.7.4 FreeBSD 4.11 gcc 2.95.4 g++ 2.95.4 gcc 3.2.3, 3.3.6, 3.4.4, 4.0.0 HP-UX B.11.00 HP C HP92453-01 A.11.01.20 HP F90 v2.4 HP ANSI C++ B3910B A.03.13 HP-UX B.11.23 HP aC++/ANSI C B3910B A.06.00 HP F90 v2.9 HP aC++/ANSI C B3910B A.06.00 IRIX64 6.5 (tesla -64) MIPSpro cc 7.4.2m F90 MIPSpro 7.4.2m C++ MIPSpro cc 7.4.2m IRIX64 6.5 (64 & n32) MIPSpro cc 7.3.1.3m F90 MIPSpro 7.3.1.3m (64 only) C++ MIPSpro cc 7.3.1.3m mpt 1.6 Linux 2.4.20-28.7 gcc 2.96 (eirene, verbena) gcc 3.3.2 PGI compilers (pgcc, pgf90, pgCC) version 5.2-1 Absoft Fortran compiler v9.0 Intel(R) C++ 32-bit Version 8.1 Intel(R) Fortran 32-bit Version 8.1 MPIch 1.2.6 Linux 2.4.21-268-smp x86_64 gcc 3.3.1 (SuSE Linux, AMD) (mir) PGI 5.2-1 C and F90 (with k3-32) Intel(R) C++ 32-bit Version 8.1 Intel(R) Fortran 32-bit Version 8.1 Linux 2.4.21-sgi306rp21 Altix SMP ia64 Intel(R) C++ Version 8.1 (cobalt) Intel(R) Fortran Itanium(R) Version 8.1 SGI MPI OSF1 V5.1 (QSC) Compaq C V6.5-011 HP Fortran V5.5A-3548 Compaq C++ V6.5-036 MPIX200_64_r13.4 OSF1 V5.1 (PSC) Compaq C V6.5-303 HP Fortran V5.5A-3548 Compaq C++ V6.5-040 SunOS 5.8 32,46 Sun WorkShop 6 update 2 C 5.3 (Solaris 2.8) Sun WorkShop 6 update 2 Fortran 90 Sun WorkShop 6 update 2 C++ 5.3 SunOS 5.9 32,64 Sun C 5.6 2004/07/15 (Solaris 2.9) Sun Fortran 95 8.0 2004/07/15 Sun C++ 5.6 2004/07/15 SunOS 5.10 Sun WorkShop 6 update 2 C 5.3 Sun WorkShop 6 update 2 Fortran 95 6.2 Sun WorkShop 6 update 2 C++ 5.3 Patch 111685-13 Xeon Linux 2.4.21-32.0.1.ELsmp-perfctr-lustre (tungsten) Intel(R) C++ Version 9.0 Intel(R) Fortran Compiler Version 9.0 IA-64 Linux 2.4.21.SuSE_292.til1 ia64 (NCSA tg-login) Intel(R) C++ Version 8.0 Intel(R) Fortran Compiler Version 8.0 mpich-gm-1.2.5..10-intel-r2 Windows XP MSVC++.NET MSVC++ 6.0 Intel 8.1 C++ MAC OS X Darwin 7.5 gcc and g++ Apple Computer, Inc. GCC version 1175, based on gcc version 3.3.2 IBM XL Fortran version 8.1 Absoft Fortran compiler v8.2 Supported Configuration Features Summary ======================================== Key: y = tested and supported n = not supported or not tested in this release x = not working in this release dna = does not apply ( ) = footnote appears below second table Platform C F90 F90 C++ zlib SZIP parallel parallel IBM BG/L (16) n n n n y y Solaris2.8 64-bit y y y(1) y y y Solaris2.8 32-bit y y y(1) y y y Solaris2.9 64-bit y(1) y y(1) y y y Solaris2.9 32-bit y(1) y y(1) y y y Solaris2.10 64-bit y(1) y n y y y Solaris2.10 32-bit y(1) y n y y y IRIX64_6.5 64-bit y(2) y y y y y IRIX64_6.5 32-bit y(2) n n n y y HPUX11.00 y(1) y y y y y HPUX11.23-32bit n y n y y y HPUX11.23-64bit n n n y y y OSF1 v5.1 y y y y y y X1 y y y y y n AIX-5.1, 5.2 & 5.3 32-bit y y y y y y AIX-5.1, 5.2 & 5.3 64-bit y y y y y y WinXP Visual Studio 6.0 n n(9) n y y y WinXP .Net n n n y(8) y y Mac OS X 10.3 n y(10) n y y y FreeBSD 4.11 n n n y y y RedHat 7.3 W (3) y(1) y(11) n y y y RedHat 7.3 W Intel (3) n y n y y y RedHat 7.3 W PGI (3) n y n y y y RedStorm (16) n y n y y n SuSe x86_64 gcc (3,13) n y(12) n y y y SuSe x86_64 icc (3,13) n y(14) n y y y Linux 2.4 Xeon C Lustre Intel (3,6) n y n y y y Linux 2.4 SuSE ia64 C Intel (3,7) y y y y y y Linux 2.4 SGI Altix ia64 Intel (3) y y y y y y Platform Shared static- Thread- STREAM- libraries(4) exec safe VFD IBM BG/L n y n n Solaris2.8 64-bit y x y y Solaris2.8 32-bit y x y y Solaris2.9 64-bit y x y y Solaris2.9 32-bit y x y y Solaris2.10 64-bit y x y y Solaris2.10 32-bit y x y y IRIX64_6.5 64-bit y y y y IRIX64_6.5 32-bit y y y y HPUX11.00 y x n y HPUX11.23 y y n y OSF1 v5.1 y y n y X1 n y n y AIX-5.1, 5.2 & 5.3 32-bit n y n y AIX-5.1, 5.2 & 5.3 64-bit n y n y WinXP Visual Studio 6.0 y y n n WinXP .Net y y n n Mac OS X 10.3 y y n y FreeBSD 4.11 y y y y RedHat 7.3 W (3) y y y y RedHat 7.3 W Intel (3) n y n y RedHat 7.3 W PGI (3) n y n y RedStorm n y n y SuSe x86_64 gcc (3,13) n y n y SuSe x86_64 icc (3,13) y y(15) n y Linux 2.4 Xeon C Lustre Intel (3,6) y y n y Linux 2.4 SuSE ia64 C Intel (3,7) y y n n Linux 2.4 SGI Altix ia64 Intel (3) y y n y Compiler versions for each platform are listed in the "Platforms Tested" table found elsewhere in this file (RELEASE.txt). Unless otherwise noted, compilers used are the system compilers. Footnotes: (1) Using mpich 1.2.6 (2) Using mpt and mpich 1.2.6. (3) Linux 2.4 with GNU, Intel, and PGI compilers, as indicated. W or C indicates workstation or cluster, respectively. (4) Shared libraries are provided only for the C library, except on Windows where they are provided for C and C++. (5) Using mpt. (6) Linux 2.4.21-32.0.1. Xeon cluster with ELsmp-perfctr-lustre and Intel compilers (7) Linux 2.4.21, SuSE_292.til1. Ia64 cluster with Intel compilers (8) Intel 8.1 (9) One test of this release failed with Compaq Visual Fortran 6.6c. No binary fortran release will be provided. Users should build the library by themselves and use it at their own risk. We recommend that users use HDF5 1.7 instead or use Compaq Visual Fortran 6.0. (10) IBM XLF and Absoft (11) PGI, Absoft. No shared libraries with Absoft; use '--disable-shared'. (12) PGI and Intel compilers for both C and Fortran (13) AMD Opteron x86_64 (14) ifort (15) Yes with C and Fortran, but not with C++ (16) Only serial is ported. PFS does not work for PHDF5 yet. FMB/EIP - 2005/11/10 Known Problems ============== * Intel Compilers for Linux x86_86 platforms (EM64T-based, v8.1) has optimization error in the data types conversion code. Before running configure, edit the file config/intel-flags by changing the setting of PROD_CFLAGS from -O3 to -O0, then run configure. AKC - 2005/11/10. * Fortran testing and compiling failures on windows XP 1. Compaq visual fortran 6.6c with VS 6.0 The Fortran tests failed for both release, release dll, debug and debug dll. The failure is a random one. We won't provide fortran libraries. The same test passed with the 1.7.51 snapshot. You may find the 1.7.51 snapshot under ftp://hdf.ncsa.uiuc.edu/pub/outgoing/hdf5/snapshots/. 2. Intel fortran 8.1 under .Net environment The fortran library cannot even be compiled. Some users have pointed this to intel forum. * When testing parallel HDF5 with the C compiler version MIPSpro 7.4.3 at IRIX 6.5, set enviroment variable MPI_TYPE_MAX to be a bigger number, for example 120000, in order to pass the complicated collective IO tests inside parallel HDF5 library. This is not a problem inside parallel HDF5 library. You can always set a bigger number in your system. KY - 2005/10/6 * A contiguous or chunked dataset created by a sequential version may not be modified with a parallel version of the library. Use the H5Pset_alloc_time function with H5D_ALLOC_TIME_EARLY to set up the dataset creation property list to avoid the problem. EIP - 2005/09/09 * The dataset created or rewritten with the v1.6.3 library or after can't be read with the v1.6.2 library or before when Fletcher32 EDC(filter) is enabled. There was a bug in the calculating code of the Fletcher32 checksum in the library before v1.6.3. The checksum value wasn't consistent between big-endian and little-endian systems. This bug was fixed in Release 1.6.3. However, after fixing the bug, the checksum value is no longer the same as before on little-endian system. The library release after 1.6.4 can still read the dataset created or rewritten with the library of v1.6.2 or before. SLU - 2005/7/8 * For version 6 (6.02 and 6.04) of the Portland Group compiler on AMD Opteron processor, there's a bug in the compiler for optimization(-O2). The library failed in several tests but all related to multi driver. The problem has been reported to the vendor. * test/big fails sometimes with the message "Possible overlap with another region." The test selects regions randomly, and this error occurs when two regions overlap each other; it is a bug in the test and not in HDF5. Since the error is triggered by a random situation, it will usually disappear if the test is re-run. * Newer SGI MIPSpro compilers (version 7.4.x) support C99 features but it has a "guard" statement in stdint.h that will #error and skip the rest of the header file if C99 option is not used explicitly. Hardset $CC to c99 will resolve the problem. AKC - 2004/12/13 * On IBM AIX systems, parallel HDF5 mode will fail some tests with error messages like "INFO: 0031-XXX ...". This is from the command poe. Set the environment variable MP_INFOLEVEL to 0 to minimize the messages and run the tests again. The tests may fail with messages like "The socket name is already in use". HDF5 does not use sockets (except for stream-VFD). This is due to problems of the poe command trying to set up the debug socket. Check if there are many old /tmp/s.pedb.* staying around. These are sockets used by the poe command and left behind due to failed commands. Ask your system administrator to clean them out. Lastly, request IBM to provide a means to run poe without the debug socket. * Two h5dump xml tests(h5dump --xml thlink.h5 and h5dump --xml tmany.h5) failed on windows xp with .NET for debug and debug dll. Release and Release dll work fine. * The h5dump tests may fail to match the expected output on some platforms (e.g. parallel jobs, Windows) where the error messages directed to "stderr" do not appear in the "right order" with output from stdout. This is not an error. * The stream-vfd test uses ip port 10007 for testing. If another application is already using that port address, the test will hang indefinitely and has to be terminated by the kill command. To try the test again, change the port address in test/stream_test.c to one not being used in the host. * The --enable-static-exec configure flag fails to compile for Solaris platforms. This is due to the fact that not all of the system libraries on Solaris are available in a static format. The --enable-static-exec configure flag also fails to correctly compile on IBM SP2 platform for the serial mode. The parallel mode works fine with this option. The --enable-static-exec configure flag also fails to correctly compile on the HPUX 11.00. It is suggested that you don't use this option on these platforms during configuration. * The Stream VFD was not tested yet under Windows. * Before building HDF5 F90 Library from source on Crays replace H5Aff.f90, H5Dff.f90 and H5Pff.f90 files in the fortran/src subdirectory in the top level directory with the Cray-specific files from the site: ftp://ftp.ncsa.uiuc.edu/HDF/HDF5/current/src/patches/ * Use --disable-shared configure flag if building with Absoft Fortran compiler. * Information about building with PGI and Intel compilers is available in INSTALL file sections 5.7 and 5.8. * In LANL QSC, the new cc compiler has problems converting small values of long long (absolute values less than 1**-308) to double. This triggers the test/dtypes to report failure in the Testing random sw long double -> double conversions If -ieee is used, the converted doubles spread over the range 0.0 to 1**-308. If -ieee is not used, the converted double values are mostly 0.0 but occasionally as 1**-308. This has been reported to the system staff. All other tests have passed. * Fortran release DLL randomly failed with Compaq Visual Fortran 6.6c on Windows. * Fortran DLL built with Intel 8.1 in .NET environment crushed the compiler, Building Fortran static library with Intel 8.1 in .NET environment requires manually setting the project file. Please contact to hdfhelp@ncsa.uiuc.edu if you need to build Fortran static library with Intel 8.1 with .NET environment. * On at least one system, SDSC DataStar, the scheduler (in this case LoadLeveler) sends job status updates to standard error when you run any executable that was compiled with the parallel compilers. This causes problems when running "make check" on parallel builds, as many of the tool tests function by saving the output from test runs, and comparing it to an exemplar. The best solution is to reconfigure the target system so it no longer inserts the extra text. However, this may not be practical. In such cases, one solution is to "setenv HDF5_Make_Ignore yes" prior to the configure and build. This will cause "make check" to continue after detecting errors in the tool tests. However, in the case of SDSC DataStar, it also leaves you with some 150 "failed" tests to examine by hand. A second solution is to write a script to run serial tests and filter out the text added by the scheduler. A sample script used on SDSC DataStar is given below, but you will probably have to customize it for your installation. Observe that the basic idea is to insert the script as the first item on the command line which executes the test. The script then executes the test and filters out the offending text before passing it on. #!/bin/csh set STDOUT_FILE=~/bin/serial_filter.stdout set STDERR_FILE=~/bin/serial_filter.stderr rm -f $STDOUT_FILE $STDERR_FILE ($* > $STDOUT_FILE) >& $STDERR_FILE set RETURN_VALUE=$status cat $STDOUT_FILE tail +3 $STDERR_FILE exit $RETURN_VALUE You get the HDF make files and test scripts to execute your filter script by setting the environment variable "RUNSERIAL" to the full path of the script prior to running configure for parallel builds. Remember to "unsetenv RUNSERIAL" before running configure for a serial build. Note that the RUNSERIAL environment variable exists so that we can prefix serial runs as necessary on the target system. On DataStar, no prefix is necessary. However, on an MPICH system, the prefix might have to be set to something like "/usr/local/mpi/bin/mpirun -np 1" to get the serial tests to run at all. In such cases, you will have to include the regular prefix in your filter script. %%%%1.6.4%%%% Release Information for hdf5-1.6.4 (15/March/05) HDF5 version 1.6.4 released on Tue Mar 15 20:38:48 CST 2005 ================================================================================ INTRODUCTION ============ This document describes the differences between HDF5-1.6.3 and HDF5-1.6.4, and contains information on the platforms tested and known problems in HDF5-1.6.4. For more details check the HISTORY.txt file in the HDF5 source. The HDF5 documentation can be found on the NCSA ftp server (ftp.ncsa.uiuc.edu) in the directory: /HDF/HDF5/docs/ For more information look at the HDF5 home page at: http://hdf.ncsa.uiuc.edu/HDF5/ If you have any questions or comments, please send them to: hdfhelp@ncsa.uiuc.edu CONTENTS ======== - New Features - Support for new platforms and languages - Bug Fixes since HDF5-1.6.3 - Documentation - Platforms Tested - Supported Configuration Features Summary - Known Problems New Features ============ Source code distribution: ------------------------- The High-Level (HL) C APIs were added to the source code distribution. For HL documentation, see http://hdf.ncsa.uiuc.edu/HDF5/hdf5_hl/doc/RM_hdf5hl.html. The HL library, libhdf5_hl.a(so), is built and installed by default. Use --disable-hl configure flag to disable the HL library. Library: -------- - We recommend you to use SZIP v2.0 with this release. For more information see http://hdf.ncsa.uiuc.edu/doc_resource/SZIP/ - The compound datatype has been enhanced with a new feature of size adjustment. The size can be increased and decreased (without cutting the last member). No API change is involved. SLU - 2004/10/1 - Removed PABLO support. 2005/01/20 EIP Parallel Library: ----------------- - Allow compressed, chunked datasets to be read in parallel. QAK - 2004/10/04 Tools: ------ - New tool, h5jam. See HDF5 Reference Manual. 2004/10/08 F90 API: -------- No new features in this release. C++ API: -------- - Started using C library's reference counting in place of the class RefCounter, which existed before the C mechanism was available. As a result, RefCounter has been removed. 2005/03/12 BMR Support for new platforms, languages and compilers. ======================================= Configuration ------------- - Upgraded from GNU autoconf 2.53 to autoconf 2.59. JML - 2005/01/31 Bug Fixes since HDF5-1.6.3 release ================================== Library ------- - Fixed a racing condition in MPIPOSIX virtual file drive close function. Now all processes must completed the close before any of them is returned. This prevents some "faster" processes start accessing the file for another purpose (e.g., open with truncate) while other "slower" processes have not closed the same file with the previous purpose. AKC - 2005/03/01 - H5Tget_member_value calls for enum datatype didn't return correct value if H5Tenum_valueof was called first. It's fixed. SLU - 2005/02/08 - For variable-length string, H5Tget_class returned H5T_STRING as its class. But H5Tdetect_class and H5Tget_member_class considered it as H5T_VLEN. This is fixed to let all these 3 functions treat it as H5T_STRING. SLU - 2005/02/08 - The byte order of all 1-byte integer types was fixed as little-endian even on a big-endian machine. It's corrected. SLU - 2005/02/07 - Fixed segmentation fault when calling H5Fflush with an attribute that hasn't had a value written to it open. QAK - 2004/10/18 - Backed out support for bitfield and time types in H5Tget_native_type. Leave it to future support. The function simply returns error message of "not support" for bitfield and time types. SLU - 2004/10/5 - Fixed address check in Core VFL driver to avoid spurious address/size overflows for odd valued addresses and/or sizes. QAK - 2004/09/27 - Fixed problem where chunked datasets were not able to be deleted from a file under certain circumstances. QAK - 2004/09/27/ Configuration ------------- - IRIX64 MIPSpro compiler of 7.4.x supports C99 features. Default to use the 'c99' compiler if available. AKC - 2004/12/13 - Intel v8.0 compiler would infinite loop when compiling some test code with -O3 option. Changed enable-production default compiler option to -O2. AKC - 2004/12/06 - Long double is assumed to be a supported C data type. It is a standard C89 type. AKC - 2004/10/22 Performance ------------- Many changes were made to the library to improve performance, especially for the variable-length datatypes and metadata cache. Tools ----- - h5fc and h5c++ work correctly when -c compiler flag is used. EIP - 2005/03/14 - Fixed h5dump to print attributes data in ASCII if -r option is used. AKC - 2004/11/18 - Fixed space utilization reported in h5ls to correct error in formula used. QAK - 2004/10/22 Documentation ------------- F90 API ------- - On windows, previously Fortran DLL built and tested failed. Now Fortran DLL has been built and tested successfully with Dec Fortran 6.6c or Dec Fortran 6.0. C++ API ------- Documentation ============= HDF5 Library documentation -------------------------- No substantive changes to the structure or types of content in the HDF5 Library documentation. Windows installation documentation ---------------------------------- 1. On Windows zlib has been updated to 1.2.2. You may find the binary at either http://www.zlib.net/zlib122-dll.zip or ftp://hdf.ncsa.uiuc.edu/lib-external/zlib/bin/windows 2. Only DLLs of external libraries (zlib and szip) are linked with the HDF5 Library. We will no longer provide binary to link static library with HDF5. For details, please check INSTALL_Windows in this directory. Platforms Tested ================ AIX 5.1 (32 and 64-bit) xlc 6.0.0.6 xlf 8.1.1.3 xlC 6.0.0.6 mpcc_r 6.0.0.6 mpxlf_r 8.1.1.3 xlc 5.0.2.5 xlf 7.1.1.2 xlC 5.0.2.5 mpcc_r 5.0.2.5 mpxlf_r 7.1.1.2 AIX 5.2 (32/64 bit) xlc 6.0.0.8 xlC 6.0.0.9 xlf 8.1.1.7 mpcc_r 6.0.0.8 mpxlf_r 8.1.1.7 AIX 5.2 (32/64 bit, LLNL frost) xlc 6.0.0.8 xlC 6.0.0.8 xlf 8.1.1.7 mpcc_r 6.0.0.8 mpxlf_r 8.1.1.7 Cray T90 sn7001 10.0.0md Cray Standard C Version 6.4.0.3 Cray Fortran Version 3.4.0.0 Cray SV1 sn9617 10.0.1.2 Cray Standard C Version 6.6.0.3.6 Cray Fortran Version 3.6.0.3.1 FreeBSD 4.9 gcc 2.95.4 g++ 2.95.4 gcc 3.2.3, 3.3.6, 3.4.4, 4.0.0 HP-UX B.11.00 HP C HP92453-01 A.11.01.20 HP F90 v2.4 HP ANSI C++ B3910B A.03.13 MPIch 1.2.4 IRIX64 6.5 (tesla -64) MIPSpro cc 7.4.2m F90 MIPSpro 7.4.2m C++ MIPSpro cc 7.4.2m IRIX64 6.5 (64 & n32) MIPSpro cc 7.3.1.3m F90 MIPSpro 7.3.1.3m (64 only) C++ MIPSpro cc 7.3.1.3m mpt 1.6 Linux 2.4.20-28.7 gcc 2.96 (eirene, verbena) gcc 3.3.2 PGI compilers (pgcc, pgf90, pgCC) version 5.2-1 Absoft Fortran compiler v9.0 Intel(R) C++ 32-bit Version 8.1 Intel(R) Fortran 32-bit Version 8.1 MPIch 1.2.6 Linux 2.4.21-268-smp x86_64 gcc 3.3.1 (SuSE Linux, AMD) (mir) PGI 5.2-1 C and F90 (with k3-32) Intel(R) C++ 32-bit Version 8.1 Intel(R) Fortran 32-bit Version 8.1 Linux 2.4.21-sgi303r2 Altix SMP ia64 Intel(R) C++ Version 8.1 (cobalt) Intel(R) Fortran Itanium(R) Version 8.1 SGI MPI OSF1 V5.1 (QSC) Compaq C V6.5-011 HP Fortran V5.5A-3548 Compaq C++ V6.5-036 MPIX200_64_r13.4 OSF1 V5.1 (PSC) Compaq C V6.5-303 HP Fortran V5.5A-3548 Compaq C++ V6.5-040 MPIX200_64_r13.4 FORTRAN 90 2.0 Patch 107356-04 SunOS 5.8 32,46 Sun WorkShop 6 update 2 C 5.3 (Solaris 2.8) Sun WorkShop 6 update 2 Fortran 90 Sun WorkShop 6 update 2 C++ 5.3 SunOS 5.9 32,64 Sun C 5.6 2004/07/15 (Solaris 2.9) Sun Fortran 95 8.0 2004/07/15 Sun C++ 5.6 2004/07/15 TFLOPS r1.0.4 v4.5.2 i386 pgcc Rel 3.1-4i with mpich-1.2.4 with local modifications Xeon Linux 2.4.20-31.9smp_perfctr_lustre (tungsten) Intel(R) C++ Version 8.0 Intel(R) Fortran Compiler Version 8.0 IA-64 Linux 2.4.21.SuSE_128.bef1 ia64 (NCSA tg-login) Intel(R) C++ Version 8.0 Intel(R) Fortran Compiler Version 8.0 mpich-gm-1.2.5..intel Windows XP MSVC++.NET MSVC++ 6.0 Compaq Visual Fortran 6.6C Intel 8.1 C++ MAC OS X Darwin 7.5 gcc and g++ Apple Computer, Inc. GCC version 1175, based on gcc version 3.3.2 IBM XL Fortran version 8.1 Absoft Fortran compiler v8.2 Supported Configuration Features Summary ======================================== Key: y = tested and supported n = not supported or not tested in this release x = not working in this release dna = does not apply ( ) = footnote appears below second table Platform C F90 F90 C++ zlib SZIP parallel parallel Solaris2.8 64-bit y y y(1) y y y Solaris2.8 32-bit y y y(1) y y y Solaris2.9 64-bit y(1) y y(1) y y y Solaris2.9 32-bit y(1) y y(1) y y y IRIX64_6.5 64-bit y(2) y y y y y IRIX64_6.5 32-bit y(2) n n n y y HPUX11.00 y(1) y y y y y OSF1 v5.1 y y y y y y T90 IEEE n y n n y n SV1 y(5) y y(5) n y n TFLOPS y(1) n n n y n AIX-5.1 & 5.2 32-bit y y y y y y AIX-5.1 & 5.2 64-bit y y y y y y WinXP Visual Studio 6.0 n y(9) n y y y WinXP .Net n n n y(8) y y Mac OS X 10.3 n y(10) n y y y FreeBSD 4.9 y(1) n n y y y RedHat 7.3 W (3) y(1) y(11) n y y y RedHat 7.3 W Intel (3) n y n y y y RedHat 7.3 W PGI (3) n y n y y y SuSe x86_64 gcc (3,13) n y(12) n y y y SuSe x86_64 icc (3,13) n y(14) n y y y Linux 2.4 Xeon C Lustre Intel (3,6) n y n y y y Linux 2.4 SuSE ia64 C Intel (3,7) y y y y y y Linux 2.4 SGI Altix ia64 Intel (3) y y y y y y Platform Shared static- Thread- STREAM- libraries(4) exec safe VFD Solaris2.8 64-bit y x y y Solaris2.8 32-bit y x y y Solaris2.9 64-bit y x y y Solaris2.9 32-bit y x y y IRIX64_6.5 64-bit y y y y IRIX64_6.5 32-bit y y y y HPUX11.00 y x n y OSF1 v5.1 y y n y T90 IEEE n y n y SV1 n y n y TFLOPS n y n n AIX-5.1 & 5.2 32-bit n y n y AIX-5.1 & 5.2 64-bit n y n y WinXP Visual Studio 6.0 y y n n WinXP .Net y y n n Mac OS X 10.3 y y n y FreeBSD 4.9 y y y y RedHat 7.3 W (3) y y y y RedHat 7.3 W Intel (3) n y n y RedHat 7.3 W PGI (3) n y n y SuSe x86_64 gcc (3,13) n y n y SuSe x86_64 icc (3,13) y y(15) n y Linux 2.4 Xeon C Lustre Intel (3,6) y y n y Linux 2.4 SuSE ia64 C Intel (3,7) y y n n Linux 2.4 SGI Altix ia64 Intel (3) y y n y Compiler versions for each platform are listed in the "Platforms Tested" table found elsewhere in this file (RELEASE.txt). Unless otherwise noted, compilers used are the system compilers. Footnotes: (1) Using mpich 1.2.6 (2) Using mpt and mpich 1.2.6. (3) Linux 2.4 with GNU, Intel, and PGI compilers, as indicated. W or C indicates workstation or cluster, respectively. (4) Shared libraries are provided only for the C library, except on Windows where they are provided for C and C++. (5) Using mpt. (6) Linux 2.4.20-31.9. Xeon cluster with smp_perfctr_lustre and Intel compilers (7) Linux 2.4.21, SuSE_128.befl. Ia64 cluster with Intel compilers (8) Intel 8.1 (9) Compaq Visual Fortran 6.6C (10) IBM XLF and Absoft (11) PGI, Absoft. No shared libraries with Absoft; use '--disable-shared'. (12) PGI and Intel compilers for both C and Fortran (13) AMD Opteron x86_64 (14) ifort (15) Yes with C and Fortran, but not with C++ FMB/EIP - 2005/03/15 Known Problems ============== * test/big fails sometimes with the message "Possible overlap with another region." The test selects regions randomly, and this error occurs when two regions overlap each other; it is an bug in the test and not in HDF5. Since the error is triggered by a random situation, it will usually disappear if the test is re-run. * Cray SV1 fails to correctly convert between floating-point and "long double" for software conversion. Problem is being investigated. SLU - 2005/03/04 * Newer SGI MIPSpro compilers (version 7.4.x) support C99 features but it has a "guard" statement in stdint.h that will #error and skip the rest of the header file if C99 option is not used explicitly. Hardset $CC to c99 will resolve the problem. AKC - 2004/12/13 * On IBM AIX systems, parallel HDF5 mode will fail some tests with error messages like "INFO: 0031-XXX ...". This is from the command poe. Set the environment variable MP_INFOLEVEL to 0 to minimize the messages and run the tests again. The tests may fail with messages like "The socket name is already in use". HDF5 does not use sockets (except for stream-VFD). This is due to problems of the poe command trying to set up the debug socket. Check if there are many old /tmp/s.pedb.* staying around. These are sockets used by the poe command and left behind due to failed commands. Ask your system administrator to clean them out. Lastly, request IBM to provide a mean to run poe without the debug socket. * Fortran subroutine h5pget_driver_f doesn't return a correct driver information. * There are two h5dump xml tests(h5dump --xml thlink.h5 and h5dump --xml tmany.h5) failed on windows xp with .NET for debug and debug dll. Release and Release dll work fine. * The h5dump tests may fail to match the expected output on some platforms (e.g. parallel jobs, Windows) where the error messages directed to "stderr" do not appear in the "right order" with output from stdout. This is not an error. * The stream-vfd test uses ip port 10007 for testing. If another application is already using that port address, the test will hang indefinitely and has to be terminated by the kill command. To try the test again, change the port address in test/stream_test.c to one not being used in the host. * The --enable-static-exec configure flag fails to compile for Solaris platforms. This is due to the fact that not all of the system libraries on Solaris are available in a static format. The --enable-static-exec configure flag also fails to correctly compile on IBM SP2 platform for the serial mode. The parallel mode works fine with this option. It is suggested that you don't use this option on these platforms during configuration. * The Stream VFD was not tested yet under Windows. It is not supported in the TFLOPS machine. * The ./dsets tests failed in the TFLOPS machine if the test program, dsets.c, is compiled with the -O option. The hdf5 library still works correctly with the -O option. The test program works fine if it is compiled with -O1 or -O0. Only -O (same as -O2) causes the test program to fail. * Certain platforms give false negatives when testing h5ls: - Cray T90IEEE give errors during testing when displaying some floating-point values. These are benign differences due to the different precision in the values displayed. h5ls appears to be dumping floating-point numbers correctly. * Before building HDF5 F90 Library from source on Crays replace H5Aff.f90, H5Dff.f90 and H5Pff.f90 files in the fortran/src subdirectory in the top level directory with the Cray-specific files from the site: ftp://ftp.ncsa.uiuc.edu/HDF/HDF5/current/src/patches/ * On some platforms that use Intel and Absoft compilers to build HDF5 fortran library, compilation may fail for fortranlib_test.f90, fflush1.f90 and fflush2.f90 complaining about exit subroutine. Comment out the line IF (total_error .ne. 0) CALL exit (total_error) * Use --disable-shared configure flag if building with Absoft Fortran compiler * Information about building with PGI and Intel compilers is available in INSTALL file sections 5.7 and 5.8 * In LANL QSC, the new cc compiler has problems converting small values of long long (absolute values less than 1**-308) to double. This triggers the test/dtypes to report failure in the Testing random sw long double -> double conversions If -ieee is used, the converted doubles spread over the range 0.0 to 1**-308. If -ieee is not used, the converted double values are mostly 0.0 but occasionally as 1**-308. This has been reported to the system staff. All other tests have passed. * The C++ library's tests fails when compiling with PGI C++ compiler. The workaround until the problem is correctly handled is to use the flag "--instantiate=local" prior to the configure and build steps, as: setenv CXX "pgCC --instantiate=local" for pgCC 5.02 and higher setenv CXX "pgCC -tlocal" for others * Fortran release DLL randomly failed with compaq visual fortran 6.6c on windows. * Fortran DLL built with Intel 8.1 in .NET environment crushed the compiler, To build Fortran Static library with Intel 8.1 in .NET environment needs manually setting the project file, please contact to hdfhelp@ncsa.uiuc.edu if you need to build fortran static library with Intel 8.1 with .NET environment. * On at least one system, (SDSC DataStar), the scheduler (in this case LoadLeveler) sends job status updates to standard error when you run any executable that was compiled with the parallel compilers. This causes problems when running "make check" on parallel builds, as many of the tool tests function by saving the output from test runs, and comparing it to an exemplar. The best solution is to reconfigure the target system so it no longer inserts the extra text. However, this may not be practical. In such cases, one solution is to "setenv HDF5_Make_Ignore yes" prior to the configure and build. This will cause "make check" to continue after detecting errors in the tool tests. However, in the case of SDSC DataStar, it also leaves you with some 150 "failed" tests to examine by hand. A second solution is to write a script to run serial tests and filter out the text added by the scheduler. A sample script used on SDSC DataStar is given below, but you will probably have to customize it for your installation. Observe that the basic idea is to insert the script as the first item on the command line which executes the test. The script then executes the test and filters out the offending text before passing it on. #!/bin/csh set STDOUT_FILE=~/bin/serial_filter.stdout set STDERR_FILE=~/bin/serial_filter.stderr rm -f $STDOUT_FILE $STDERR_FILE ($* > $STDOUT_FILE) >& $STDERR_FILE set RETURN_VALUE=$status cat $STDOUT_FILE tail +3 $STDERR_FILE exit $RETURN_VALUE You get the HDF make files and test scripts to execute your filter script by setting the environment variable "RUNSERIAL" to the full path of the script prior to running configure for parallel builds. Remember to "unsetenv RUNSERIAL" before running configure for a serial build. Note that the RUNSERIAL environment variable exists so that we can can prefix serial runs as necessary on the target system. On DataStar, no prefix is necessary. However on an MPICH system, the prefix might have to be set to something like "/usr/local/mpi/bin/mpirun -np 1" to get the serial tests to run at all. In such cases, you will have to include the regular prefix in your filter script. %%%%1.6.3%%%% Release Information for hdf5-1.6.3 (22/September/04) HDF5 version 1.6.3 released on Wed Sep 22 11:30:11 CDT 2004 ================================================================================ INTRODUCTION This document describes the differences between HDF5-1.6.2 and HDF5-1.6.3, and contains information on the platforms tested and known problems in HDF5-1.6.3. For more details check the HISTORY.txt file in the HDF5 source. The HDF5 documentation can be found on the NCSA ftp server (ftp.ncsa.uiuc.edu) in the directory: /HDF/HDF5/docs/ For more information look at the HDF5 home page at: http://hdf.ncsa.uiuc.edu/HDF5/ If you have any questions or comments, please send them to: hdfhelp@ncsa.uiuc.edu CONTENTS - New Features - Support for new platforms and languages - Bug Fixes since HDF5-1.6.2 - Documentation - Platforms Tested - Supported Configuration Features Summary - Known Problems New Features ============ Configuration: -------------- - Added some initial support for making purify (or similar memory checking products) happier by initializing buffers to zero and disabling the internal free list code. To take advantage of this, define 'H5_USING_PURIFY' in your CFLAGS when building the library. QAK - 2004/07/23 - WINDOWS building,testing and installing improvements - On Windows, FORTRAN,C++ and C projects are merged into one zip file, users can choose an option to build either FORTRAN or C++ or both with basic C library.For detailed information, please read INSTALL_Windows.txt. - On Windows, szip compression library with or without encoder can be easily turned off or on when building HDF5. For detailed information, please read INSTALL_Windows.txt, especially section V. - On Windows, an optional procedure for building,testing and installing HDF5 from command line is provided. This procedure is supposed to be convenient for experienced users, please read INSTALL_windows_From_Command_Line.txt for details. - On Windows, an alternative short instruction document for building, testing and installing HDF5 is provided. This instruction is supposed to be convenient for general users, please read INSTALL_Windows_Short.txt for details. - On Windows, h5repack,h5diff,h5ls and h5import tool tests have been added. KY - 2004/9/16 Library: -------- - Modified the way how HDF5 calculates 'pixels_per_scanline' parameter for SZIP compression. Now there is no restriction on the size and shape of the chunk except that the total number of elements in the chunk cannot be bigger than 'pixels_per_block' parameter provided by the user. EIP - 2004/07/21 - HDF5 can now link to SZIP with or without szip's encoder. The new API function H5Zget_filter_info can be used to check szip's status. Attempting to assign szip to a dataset property list or attempting to write with szip will generate an error if szip's encoder is disabled. JL/NF - 2