| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
| |
HDF5 library. The Dependencies files are generated by
"make depend".
Tested:
h5committest, also serial in Kagiso is tested.
|
| |
|
|
|
|
|
|
| |
H5Fget_obj_count to ssize_t and modified
C++ and Fortran API functions. This is for bug #1245.
Tested on kagiso - I've tested the same change for the trunk using h5committest.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
H5S_hyper_normalize_offset in
H5D_create_chunk_map. Please see bug report #699 for details.
Tested on kagiso - a minor change.
|
| | |
|
| | |
|
| |
|
|
| |
Tested: kagiso, linew, smirom (h5committest)
|
| | |
|
| |
|
|
|
|
|
|
|
| |
Description:
Changes made to H5O_dtype_encode_helper to always encode arrays with version 2
and always encode all composite types (not just compounds) with version 2 if
there is an array present somewhere below them in the datatype structure.
Tested: kagiso, linew, smirom (h5committest)
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
| |
correctly with nested
compound datatype. The size of compound type's member type wasn't updated. It's
fixed in this commit.
Tested on smirom. The same change was tested on three systems for v1.9.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
| |
Description: cleaning up configure related to removal of --disable-hsizet
flag, which we no longer support. Furthermore, the
H5_HAVE_LARGE_HSIZET macros in the source code have been
removed.
Tested: kagiso
|
| |
|
|
|
|
|
|
|
|
|
| |
Description:
It looks like the mpicc compiler doesn't like "//" style comments, and thus the
daily tests failed due to my changes yesterday. This simple fix changes the new
comments to "/* */" style
Tested:
kagiso
osage
|
| |
|
|
|
|
|
|
|
|
| |
less than size of name
Description:
Backport of the bug found earlier today in HDF5 1.9. The H5G_get_name_by_addr function makes a call to strncat writes an extra null byte when the buffer is smaller than the dataset name. Also, comment out 2 lines that are no longer necessary because of the fix.
Tested:
kagiso
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
| |
1) have several global filters
2) do a check on the verify code about private filter values
Note: some shuffle and szip private symbols were made public
tested: windows, linux, solaris
|
| |
|
|
|
|
| |
updated configuration and documentation files
after the hdf5-1.6.7 release.
|
| |
|
|
|
|
|
|
| |
identifier returned by H5Rdereference. The function would not be able to determine a valid object name.
Fixed it and added some tests in getname.c.
Tested on smirom, kagiso, and linew.
|
| |
|
|
| |
We will try to build release binaries today via "daily tests" procedure
|
| |
|
|
|
|
|
|
| |
releasing source tar ball
to the piblic FTP server.
Platforms tested: None
|
| |
|
|
|
|
| |
creating tar ball for testing
Platforms tested: kagiso
|
| | |
|
| |
|
|
|
|
|
|
| |
Change the 'coord' parameter for H5Sselect_elements() from 'hsize_t **' to
'hsize_t *' in this branch also.
Tested on:
Mac OS X/32 10.5.1 (amazon)
|
| |
|
|
|
|
|
|
| |
Handled truncated files better, when the truncation falls in decoding a
local heap.
Tested on:
Mac OS X/32 10.5.1 (amazon)
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add work-around to allow reading files that were produced with a buggy
earlier version of the library, which could create objects with the wrong
object header message count. There is now a configure flag
"--enable-strict-format-checks" which triggers a failure on reading a file
with this sort of corruption (when enabled) and allows the object to be read
(when disabled). The default value for the "strict-format-checks" flag is
yes when the "debug" flag is enabled and no when the "debug" flag is disabled.
Note that if strict format checks are disabled (allowing objects with
this particular kind of corruption to be read) and the file is opened with
write access, the library will re-write the object header for the corrupt
object with the correct # of object header messages.
This closes bugzilla bug #1010.
Tested on:
Linux/32 2.6 (kagiso)
FreeBSD/64 6.2 (liberty)
|
| |
|
|
|
|
|
|
|
|
| |
dataspace selection went wrong when
the selection of some dimensions are full and these dimensions are optimized through
"flattenning". The calculation of the coordinates wasn't general enough in H5Shyper.c. Also
added a test program for it.
Tested on smirom only because the same code was tested on 3 platforms for v1.8.
|
| | |
|
| | |
|
| |
|
|
| |
removing the stream-vfd.
|
| |
|
|
|
|
|
| |
Removed the stream-vfd from the basic library code.
Platforms tested:
Kagiso (serial and parallel).
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
Minor fixes to avoid memory leaks when 'realloc' fails.
Tested on:
Linux/32 2.6 (chicago)
|
| |
|
|
|
|
|
|
|
| |
Avoid memory leak when realloc() fails during attempt to get larger
buffer as we are decompressing deflated data.
Tested on:
FreeBSD/32 6.2 (duty)
Linux/32 2.6 (kagiso)
|
| |
|
|
|
|
|
|
|
|
|
| |
address if the application
passes in an empty buffer. This is mainly for MPIO programs that some processes may not
have any data to write or read but still participate the I/O. This solution solves some
MPI's problem like the ChaMPIon on tungsten which doesn't support empty buffer.
Tested on tungsten only because the change is simple and the same change for v1.7 has been
tested on multiple machines.
|
