Bug fix
Description:
Boot block checksum was being used instead of file driver info checksum
in one calculation.
Also, the offset of the file driver info was hard-coded to the end of the
superblock, instead of using the file driver offset variable.
Solution:
Changed to use file driver checksum and file driver offset variable.
Platforms tested:
FreeBSD 4.8 (sleipnir)
too small for h5committest
Bug fix
Description:
Fix "unaligned access" warning on IA64 (and alpha, probably) machines.
Solution:
Make certain that temporary destination buffer is aligned on correct
boundary for type conversion.
Platforms tested:
IA64 Linux cluster (titan)
too small for h5committest
Code cleanup
Description:
Remove "UNUSED" keyword from function prototypes in header files.
Platforms tested:
IA64 Linux cluster (titan)
too small to need commit test
Update configuration
Description:
Now that we've split the tree (Yea!), change the main trunk back to debug
on and production off.
Also, change the version # to 1.7.0
update for release
Description:
Set the version information to 1.6.0-pre1 to get ready for
v1.6 release.
(Not sure why H5F.c got changed--probably done gmake automatically
during testing.)
Platforms tested:
h5committested.
Misc. update:
Code cleanup
Description:
Add in rest of szip "options mask" macros that were missing. Also made
"raw" options mask set by the library, instead of requiring users to always set
it.
Platforms tested:
FreeBSD 4.8 (sleipnir)
Minor tweaks too small fo h5committest
Code cleanup/Feature removal
Description:
Remove "round robin" writing of metadata in MPI VFDs (and a couple of other
places). This never really worked the way I hoped it would and it causes
problems on certain machines.
Platforms tested:
FreeBSD 4.8 (sleipnir) w/parallel
Too small for triple check.
Purpose: Maintenance
Description: Bumped the version number to 1.5.62 after creating
a tar ball for the fourth round of testing.
Solution: run bin/h5vers -s scipt on arabica
Platforms tested: N/A
Misc. update:
Bug fix
Description:
Alignment of some types (namely 'short's) was still not being correctly
detected on some Crays.
Solution:
Revert part of last change which accidentally got the offset of 'short's
wrong on Crays
Correct check for alignment of 'short's on Crays.
Platforms tested:
FreeBSD 4.8 (sleipnir)
h5committest
Cray SV1 (wind)
Cray T3E (hubble)
Cray T90 (gypsy)
Bug fix
Description:
Aligned data is not being detected by type conversion routines correctly
on some Crays, causing corrupted data during I/O.
Solution:
Add extra checking for strange pointer behavior on Crays.
Platforms tested:
FreeBSD 4.8 (sleipnir)
h5committest
Cray SV1 (wind)
Cray T3E (hubble)
Cray T90 (gypsy)
Bug fix
Description:
Alignment on Cray SV1 machine was not being detected correctly and was
not aligning integer types correctly for type conversion, nor was detecting the
proper internal offset of the data in a 'short' type.
Solution:
Added more checks to detect way Cray aligns pointers in addition to current
checks.
Corrected 'offset' detection on big-endian machines.
Platforms tested:
FreeBSD 4.8 (sleipnir)
h5committest
Bug fix
Description:
Tighten up checks on "index" parameter to H5Aiterate to disallow negative
values and values greater than the number of attributes on an object.
Platforms tested:
FreeBSD 4.8 (sleipnir)
h5committest
Bug fix (backward compatibility)
Description:
Track changes to allow H5Giterate to pass along iterator callback's return
value
Also, improve range checking on "index" parameter to disallow invalid
starting indices (<0 or > the number of objects in a group).
Platforms tested:
FreeBSD 4.8 (sleipnir)
h5committest
Bug fix (backward compatibility)
Description:
Changes we've made during development of the 1.5.x branch had broken the
feature of allowing user's callbacks to H5Giterate to return a value
through the library back to the application which called H5Giterate.
Solution:
Correctly pass along iterator callback return value and adjust internal
library code to conform to this design.
Platforms tested:
FreeBSD 4.8 (sleipnir)
h5committest
Bug fix & code cleanup
Description:
The H5F_get_objects_cb was returning SUCCEED (i.e. 0) to indicate that
the ID iterator should exit early, but the ID iterator needs a non-zero return
from a callback to exit early.
Also, track change to ID iterator "operator data" to be non-const
Solution:
Changed H5F_get_objects_cb() to return "TRUE" instead, to indicate an
early exit for the ID iterator.
Platforms tested:
FreeBSD 4.8 (sleipnir)
h5committest
Code cleanup
Description:
Add another dependency to the API shutdown code to not shut down the ID
management code until the other APIs which use IDs are shut down.
Platforms tested:
FreeBSD 4.8 (sleipnir)
h5committest
Code cleanup
Description:
Change some variables that are keywords in C++ to non-keywords.
Platforms tested:
FreeBSD 4.8 (sleipnir)
too minor to require full h5committest
Bug fix and refactored code
Description:
Return the file space we have allocated already when a dataset creation
fails.
Also track the change to the H5Fget_obj_<foo> APIs
Platforms tested:
FreeBSD 4.8 (sleipnir)
h5committest
Bug fix, refactored code
Description:
Fixed closing objects for "strong" file degree, which previously would
sometime attempt to close the same object twice (when a named datatype and
a dataset which used it were both left open before the file was closed).
Stopped datatype iteration from querying for the group entry of non-named
datatypes.
Added attributes to the list of objects that can be queried by
H5Fget_obj_count and H5Fget_obj_ids, since they can hold open a file also.
Took a suggestion from Robb to return the number of open objects
in the return values of H5Fget_obj_count and H5Fget_obj_ids.
Also, added a "max_objs" parameter to the H5Fget_obj_ids function, so that
it can work well with staticly allocated arrays.
Platforms tested:
FreeBSD 4.8 (sleipnir)
h5committest
Bug fix.
Description:
When a duplicate object was attempted to be created, the library would
leak file memory and object references in the file, potentially causing an
infinite loop when shutting the library down.
Solution:
Clean up after ourselves... :-)
Platforms tested:
FreeBSD 4.8 (sleipnir)
h5committest
Bug fix
Description:
When objects were left open in a file, the API shutdown code would end
up closing property lists "out from underneath" files that were left open
pending the objects in the being closed. This caused problems later when
file objects would try to access their property list and fail to close,
causing an infinite loop in the library shutdown.
Solution:
Create some dependencies in the order that APIs are shut down, trying to
close "higher" level APIs before closing "low" level APIs. This still isn't
precise, but it does work correctly now.
Platforms tested:
FreeBSD 4.8 (sleipnir)
h5committest
Windows portability fix
Description:
Change "long long"s in code to "long_long"s, which is the portable version
of this type.
Platforms tested:
FreeBSD 4.8 (sleipnir)
to small for h5committest
Description: H5Tget_native_type fails on Cray for compound datatype.
Solution: there's size comfusion in the library on H5T_get_native_int function
Platforms tested: Cray, h5committest
Misc. update:
Bug fix
Description:
The fill time in a dataset with no fill value information created with an
older version of the library was getting set to H5D_FILL_TIME_ALLOC instead of
the new default H5D_FILL_TIME_IFSET and was causing H5Dcreate() calls with that
dataset creation property list to fail now.
Solution:
Set the new default in the fill time initialization for missing fill value
information.
Platforms tested:
FreeBSD 4.8 (sleipnir)
h5committest
New feature/Bug fix
Description:
Add new fill time value - H5D_FILL_TIME_IFSET which writes the fill value
to a dataset if the user has defined one, otherwise not writing the fill value
to the dataset.
Platforms tested:
FreeBSD 4.8 (sleipnir) serial & parallel
h5committest
Bug fix
Description:
MPE instrumentation was out of date and wasn't reporting the correct name
of the API functions in the library.
Platforms tested:
IBM p690 (copper)
h5committest not performed because it doesn't test MPE.
Purpose: Maintenance for the third round of testing
Description: Increased the version number to 1.5.59 after creating
a tar ball for testing.
Solution:
Platforms tested:
Misc. update:
Description: H5Tget_native_type fails for multiple kinds of datatype on Cray; it fails
fix-length string type, too.
Platforms tested: Cray, h5committest
Compatibility fix
Description:
The H5P[set|get]_fapl_mpiposix calls changed between v1.4.x and v1.5.x.
Solution:
Wrap them in the v1.4 backward compatibility #ifdefs and update tests, etc.
Platforms tested:
FreeBSD 4.8 (sleipnir) w/paralle & v1.4 compatibility
h5committest pointless
Bug fix
Description:
The dataset's modification time was getting set whenever raw data was
written with H5Dwrite. Unfortunately, this is a metadata change (which are
required to be performed collectively) and H5Dwrite may be called independently
from a parallel program, resulting in metadata cache corruption and/or program
hangs.
Solution:
Don't update the modification time when raw data it written. :-(
Platforms tested:
FreeBSD 4.8 (sleipnir) w/parallel
h5committest
Misc. update:
Noted in release notes and also sent to Frank for updating the docs.
Bug fix
Description:
Chunked datasets with early space allocation and unlimited dimensions were
running into problems where the dataset's "layout" message was marked as
constant too early, preventing the dataset's dimensions from being extended.
Solution:
Change logic for marking the layout message constant to wait a bit longer.
Platforms tested:
FreeBSD 4.8 (sleipnir) w/parallel
h5committest
Bug fix.
Description:
Changed "x=(x++)%y" to "x=(x+1)%y", since the former was not guaranteed to
compile to the latter.
Platforms tested:
Eyeballed.
Misc. update:
Pointed out by: Forsythe, Christi <caforsy@sandia.gov>
