[svn-r16609] Bug fix (#1161): When a family file created with v1.6 library is opened and closed with v1.8 library, v1.8 library writes the driver info block in the superblock. But v1.6 doesn't write it. This caused the data after the superblock to be overwritten. The solution is to use a flag to indicate when the original file doesn't have the driver info, v1.8 library doesn't write it either.Tested on jam. I have some trouble to access smirom and linew using h5committest.
[svn-r16606] Description: Add H5AC_create_flush_dependency() and H5AC_destroy_flush_dependency() wrappers for similarly named routines in H5C layer.Tested on:
FreeBSD/32 6.3 (duty)
Too minor to require h5committest
[svn-r16600] Description: Ensure that metadata cache entries with flush dependencies are written to the file in the correct order (for serial I/O, at least).Tested on:
FreeBSD/32 6.3 (duty) in debug mode
FreeBSD/64 6.3 (liberty) w/C++ & FORTRAN, in debug mode
Linux/32 2.6 (jam) w/PGI compilers, w/C++ & FORTRAN, w/threadsafe,
in debug mode
Linux/64-ia64 2.6 (cobalt) w/Intel compilers, w/C++ & FORTRAN,
in production mode
Linux/64-ia64 2.4 (tg-login...
[svn-r16599] added the noteFortran High-Level APIs:
------
- Lite: The h5ltget_dataset_info_f function (gets information about a dataset)
was not correctly returning the dimension array (PVN - 2009/3/23)
[svn-r16597] #1047 (B1) The h5lt info routines are returning data in transposed form. ISSUE : the dimension array of the function h5ltget_dataset_info_f was not transposed (because of C-FORTRAN storage order, the FORTRAN function calls the C function with the same name). SOLUTION: transpose the array. ACTION: add a test case.tested: h5committest
[svn-r16594] Purpose: fix bug 1189Description:
Some files apparently exist in the wild which have corrupt symbol table messages
on the root group. These files can be opened by 1.6 (which uses the cached
information in the superblock) but not by 1.8. This patch fixes 1.8 and 1.9 so
they can now open these files, and will correct them if necessary. Also fix
some potential (rare) problems with array datatype versions.
Tested: ...
[svn-r16588] 1. #1487 (B1) DS memory leaks ISSUE 1: On a "go to" error condition, previously allocated buffers were not freed. NOTE: these are "potential" memory leaks because typically the error conditions do not occur, so the potential memory leaks also do NOT occur. ISSUE 2: A function used to read dimension scales realistic data (topography of the North Atlantic, latitude and longitude) wa...tested: h5committest
[svn-r16574] Description: Clean up many compiler warnings and make test return non-zero exit code when a failure is detected.Tested on:
FreeBSD/32 6.3 (duty) in debug mode
FreeBSD/64 6.3 (liberty) w/C++ & FORTRAN, in debug mode
Linux/32 2.6 (jam) w/PGI compilers, w/C++ & FORTRAN, w/threadsafe,
in debug mode
Linux/64-amd64 2.6 (smirom) w/Intel compilers w/default API=1.6.x,
w/C++ & FORTRAN, in production mode
Solari...
[svn-r16569] the conf file needs a byte order entry because of the way the tool validates the output with h5dump (comparing the h5dump current output with a h5dump output from a pre-existent h5 file). added the byte order keyword that was removed on the last check intested: linux, solaris
[svn-r16568] #1462 By selecting a compression type, a big endian byte order was being selected. When reading the compression parameter keyword, the compression type read flag was incorrectly set to read, removed this line of code in->configOptionVector[COMPRESS] = 1;Modified one configuration file to have the COMPRESSION-TYPE GZIP
Keyword.
Entered a bug description fix of
- h5import: By selecting a compression type, a big endian byte order was being
selected (PVN - 2009/11/3)
tested: linux
[svn-r16561] Purpose: Bug Fix
Description:
Fixing BZ #1381. The --includedir=DIR configure option, which is used
to specify the installation location of C header files, did not work
correctly as the path was hard-coded in config/commence.am. I'm presuming
this is because an older version of automake didn't know where to put
c header files. In any case, removing this line now defaults the in...
[svn-r16560] Description: Remove another call to H5E_clear_stack() from within the library. Clean up lots of compiler warnings.
Tested on:
Mac OS X/32 10.5.6 (amazon)
(followup on other platforms forthcoming)
[svn-r16554] Purpose: Bug Fix
Description:
Removing the code from configure which strips the '-g' flag from CFLAGS
when in production mode. The current default CFLAGS in production mode
does not include '-g', as intended, but we should allow users to
override this and enable '-g' by setting the CFLAGS environment variable
if desired. Note that this applies to FCFLAGS and CXXFLAGS as well.
...
[svn-r16549] Bug #608: Memory leak in H5DSset_label. Added code to free sub string ptr's belonging to buffer in H5DSset_label and H5DSget_label. Also added free of buffers in error section of both functions. Potential memory leaks may exist elsewhere, and this will not close the bug.Tested:
h5committest
vista 32 VS2008
[svn-r16539] Added more test case for bypassing the cache. In test_big_chunks_bypass_cache, test the correctness of the data when the fill value is defined or not. The library should let the chunks bypass the cache depending on the size of the chunks and whether to write fill value to the chunks.Tested on jam - simple change.
[svn-r16532] Description: Pass the chunk "user data" to H5D_chunk_unlock(), so that chunks with an address already aren't reallocated.Tested on:
FreeBSD/32 6.3 (duty) in debug mode
FreeBSD/64 6.3 (liberty) w/C++ & FORTRAN, in debug mode
Linux/64-ia64 2.4 (tg-login3) w/parallel, w/FORTRAN, in production mode
[svn-r16523] Purpose: Fix bugs related to H5Dset_extent and fill valuesDescription:
In some situations it was possible for the fill value to not be written to parts
of a chunked dataset, particularly when extending and/or shrinking. Prior to
the fix for the chunk cache (1015) these bugs would have been exceedingly rare.
Tested: jam, smirom, linew (h5committest)
[svn-r16521] Changed windows batch file due r16518. As all windows OS are always LE on all platforms, simply added le to the two locations where these files are used.Tested:
Vista 32 VS2008
[svn-r16518] have 2 expected outputs for 2 h5ls runs depending if run on a big or little endian machine. Configure.in was modified to export a variable carrying endianess information to testh5ls.sh. This script then compares the current run with 2 expected outputs, one for a big-endian machine (linew was used to generate the output), other for little endian (jam was used to generate the output)the way h5ls prints types, it starts searching for NATIVE types first. One solution would be h5ls not to detect these native types, using for example the same print datatype function that h5dump does, that would make the output look the same on all platforms ("32-bit little-endian integer" would be printed instead). Drawback, this "native" information would not be available. Other solution is...
[svn-r16516] To improve the performance of querying the info of a link (bug #1404). When the index was set to creation order in query function but there's no creation order indexed in the file, the library tried to build and sort a table of all links. To optimize it, let the library use the B-tree for names of the links.Tested on jam. I tested the same change for v1.8 with h5committest.
[svn-r16511] bug fix: TESTING2 macro introduced recently for the test suite (it adds an extra space at the beginning of output, for indentation) was already available for HL and caused compilation problems on AIX. Replaced the name with TESTING_2tested: h5committest
[svn-r16499] Description: Cache chunk info for newly created chunk.Tested on:
FreeBSD/32 6.3 (duty)
(Tests included in upcoming revise_chunks branch changes)
[svn-r16489] Fixed bug #1459 by eliminating the macro long_long and replacing all instances with long long.Tested:
h5comittest
fedora 10 x64
Vista 32, VS2005, IVF101
XP32, Cygwin
[svn-r16488] Description: Clean up code and eliminate resource leaks. Also avoid "null" I/O when chunk doesn't exist and we can skip it.Tested on:
Mac OS X/32 10.5.6 (amazon)
(too minor to require h5committest)
[svn-r16483] Description: Clean up (i.e. remove) more internal calls to H5E_clear_stack(), along with some other minor code cleanups.Tested on:
Mac OS X/32 10.5.6 (amazon)
(too minor to require h5committest)
[svn-r16480] Purpose: Improve chunk cacheDescription:
The meaning of the "nbytes" field in H5D_rdcc_t was not clear, and some places
assumed it was the maximum size of the chunk cache, while some assumed it was
the current size of the chunk cache. The end result was that only 1 chunk could
be held in cache at a time. This field has been replaced by "nbytes_max" and
"nbytes_used". Performance of cached I/O should improve greatly.
T...
[svn-r16477] Purpose: Fix problem with opening an attribute multiple times through multiple file handles.Description:
An attribute's "oloc" field which specifies the file it resides in was located
in the attribute's "shared" structure. So when an attribute was opened multiple
times all of the handles for that attribute pointed to the same file id, even if
different file id's were used to open the different handles for the attribute.
The "oloc" has been moved to the top level H5A_t struct.
Tested...
[svn-r16475] Purpose: Fix rare error when adding a new object header messageDescription:
Since the new object header format, it has been possible for a situation to be
created where none of the messages are large enough to hold a continuation
message and there are no null messages to merge with. This makes it impossible
to add a new object header chunk. This case will now be handled by moving every
message in the last chunk to the newly allocated one, except for null...
Raymond Lu
Quincey Koziol
Pedro Vicente Nunes
Neil Fortner
Larry Knox
Mike McGreevy
Allen Byrne
Private HDF
Elena Pourmal