| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
release candidate.
|
| |
|
|
| |
release candidate source tar ball for testing.
|
| |
|
|
|
|
|
|
|
|
| |
Bring r17778 from trunk to 1.6 branch:
Make check for NULL dataspace a bit safer.
Tested on:
FreeBSD/32 6.3 (duty)
(too minor for h5committest)
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Description:
H5HG_load made improper assumptions about the ordering of object indices, namely
that they are in order. Not only is this not guaranteed by the file format
spec, but this condition can be violated if id's "wrap around" which can happen
when overwriting VL data. H5HG_load has been fixed to handle any order of
indices. Also fixed some other bugs involving allocation of global heaps in
memory.
Tested: jam, linew, amani (h5committest)
|
| |
|
|
|
|
|
|
|
| |
Description:
Calling H5Tcommit on a file with read only access would cause an
assertion failure. Added a check to H5T_commit to return a failure in
this case.
Tested: jam (very minor change)
|
| | |
|
| |
|
|
|
|
|
|
|
| |
There was a typo in the H5Pget_preserve that it was returning the wrong value.
Fixed. Also added a test in test/cmpd_dset.c to verify the correctness of
H5Pset_preserve and H5Pget_preserve.
Tested:
h5committest plus jam serial.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Embed the content of libhdf5.settings into the hdf5 executables so that an
"orphaned" executables can display (via the Unix strings command, for example)
the library settings used to build the executables.
configure.in:
Added the --disable-embedded-libinfo option to disable this feature.
configure:
src/H5config.h.in:
fortran/configure
c++/configure
Generated by autotools like automake.
src/H5detect.c:
Implement insert_libhdf5_settings() to insert the contents of
libhdf5.settings into the library as an extern string variable so that it
is included in all HDF5 executable.
test/Makefile.in:
Added test scripts testlibinfo.sh and testcheck_version.sh, test program
tcheck_version. Needed to introduce $PROGS so that tcheck_version is
built but not run automatically.
test/testlibinfo.sh.in:
A new test added to verify the library information is indeed included
in the executables.
H5.c: added code to print the embedded library information when there is
a library versions mis-match occurs. This ensures the library information
string is included in the executable.
Also modifies the code so that the Library mismatch warning string is
included only once in the executable.
H5private.h:
Added a global reference to the libinfo string variable to prepare
for possible stage 3 implementation of a public API.
New test: (Bug ID 1656):
Add new tests (tcheck_version, testcheck_version.sh) to verify H5check_version()
does issue warnings and abort accordingly.
Changed H5check_version() to suppress the warning message totally if
$HDF5_DISABLE_VERSION_CHECK is 2 or higher. (Old behavior treated 3 or higher
the same as 1, that is to print a warning and allows the program to continue.
MANIFEST:
updated with the newly added files.
Tested:
h5committest passed. Also passed jam in serial mode, --enable-static-exec,
--disable-embedded-libinfo.
|
| | |
|
| |
|
|
|
|
|
|
|
| |
Description:
H5Ppublic.h listed H5Pget_filter_by_id as returning H5Z_filter_t, when in fact
it returns herr_t. The header file has been corrected to indicate that it
returns herr_t.
Tested: jam
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Description:
At several places in H5Pint.c properties were being compared using memcmp, not
using the registered "cmp" callback. This could cause memory checkers to
report uninitialized memory errors, and could conceivably cause runtime errors
if memcmp reported false equality (for example if a value pointed to by the
property changed).
The code has been changed to always use the cmp callback. No tests have been
added as the cmp callback is not exposed in the 1.6 API.
Tested: jam, linew, smirom (h5committest)
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
Description:
Previously, when H5Z_filter_info was called for a filter that was not present,
it would succeed and return the information from one position past the end of
the pipeline, possibly causing a segfault. This affected at least
H5Pget_fitler_by_id, and possibly other API functions. Fixed to properly
return failure.
Tested: jam
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Description:
When using H5T_copy on committed datatypes that are already open, H5T_copy would
properly use the already existing shared struct, but would still deep copy all
of the fields in that struct. This would cause memory leaks, and in the case of
a compound containing a vlen (or reference), the change in size would cause the
size of the resulting type to be set to an incorrect value. Changed H5T_copy to
properly avoid deep copies when using a reopened shared struct.
Tested: jam, linew, smirom (h5committest)
|
| | |
|
| | |
|
| |
|
|
|
| |
HISTORY.txt and RELEASE.txt files.
Branch is open for check-ins now.
|
| |
|
|
| |
Tested: h5committested (linew is still in progress.)
|
| |
|
|
| |
check-ins.
|
| |
|
|
|
|
| |
tar ball
for remote testing.
|
| |
|
|
|
|
|
|
| |
Description:
Versioning was just added to H5Z_class_t in 1.8. Therefore, I am adding a H5Z_class1_t
macro to 1.6 to enable backwards compatibility using H5Z_class1_t.
Tested: jam (simple change)
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Description:
The MPE option is not working with the new mpich2. hdf5 configure is looking
for the routine CLOG_Init() in the library liblmpe.a. The old mpich has that
routine but the new mpich2 does not have it. I could not find any reference or
document of what the CLOG_Init() is or why it is needed. The only log message
for adding the requirement for liblmpe.a was for the NCSA old AIX platform
that has retired and could not be used to verify the correctness.
Solution:
Remove the requirement of liblmpe.a.
Tested:
Just parallel with fortran on kagiso, jam and smirom.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
Description:
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.
Tested: jam, smirom (h5committest)
|
| | |
|
| | |
|
| |
|
|
|
|
| |
Changed 'THG' to 'The HDF Group' in various HDF5 source files,
most of which are <subdirectory>/COPYING.
-- Closes Bugzilla entry 1403.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Improvement
Description:
Modified the warning messages from the Version mismatch checking to suggest
the users to try recompiling or checking the shared lib setting.
[Also, adapted the revamp of the H5check_version() done in development
branch long ago.]
Platforms tested:
Tested in Jam only since it was just a simple text string changes.
|
| | |
|
| |
|
|
|
|
|
|
| |
definition of an array in H5D_istore_initialize_by_extent, causing an iteration to continue and an assertion in H5S_hyper_iter_init when trying to initialize a non existing chunk.
Added a test for shrinking to 0 dimemsions
Tested: windows, linux
|
| | |
|
| |
|
|
|
|
|
|
| |
Bug fixes: chunks on the btree were not deleted for the case when the new dimension was on the boundary of the chunk offset (comparison of offset > chunk instead of offset >= chunk). In extending the space, the new size was wrongly compared with the maximum extend possible
Modified H5Dset_extent so that it fails when called for compact datasets and contiguous with no external storage
new test program as 1.8 and 1.9: It adds tests for several ranks, use of fill value or not, compression, different fill value allocation times, use of different storage layouts, and external files
tested: windows, linux
|
| | |
|
| | |
|
| |
|
|
|
|
| |
instead of
snap0; caught by Albert, fixed by policy offender.
|
| |
|
|
|
| |
documentation files after the release. Branch is open
for check-ins.
|
| |
|
|
| |
Will tag the release after binaries are built tonight.
|
| |
|
|
|
|
| |
creating a tar
ball for remote testing
|
