Description: Bump up the version number before giving a tar ball to the MAC HDF5
Fortran user.
Solution: run bin/h5vers on eirene
Platforms tested: N/A
Misc. update:
Bug fix
Description:
Add special-case handling to floating-point conversion tests to avoid
problems with denormalized values on Cray T3E & T90 platforms. (Still not
working on Cray SV1, but at least it's closer).
Solution:
Detect denormalized values and don't try to operate on them on the Crays.
Platforms tested:
FreeBSD 4.9 (sleipnir)
Cray T3E (hubble.cray.com)
Cray T90 (gypsy.cray.com)
Code cleanup
Description:
Note in the release notes that the short MPI-I/O bug has been fixed and
also clean up the configure.in a bit.
Platforms tested:
FreeBSD 4.9 (sleipnir)
too minor to require h5committest
directory. This eliminates the problem that the builder may not
have permission to install in the default install directory.
It also allows multiple builds in the same host or multiple srcdir
using the same source.
Platforms tested:
Eirene plus eyeballing of changes.
Misc. update:
Omnibus floating-point bug fix changes
Description:
There are a number of problems in the floating-point conversion code that
were exposed by Ray's recent int<->float checkin:
- The 'my_isnan' code in test/dtypes.c was broken and would always return
true. The meant that the actual values in the float<->float conversion
tests were _never_ checked, hiding the other bugs included in this
checkin.
- A recent change I made to the type conversion code used "FLT_MIN" instead
of "-FLT_MAX" for the most negative 'float' value for the double->float
conversion, which meant that any the negative number that was converted
from a double to a float would have been mapped to zero, essentially.
- A change that Robb appeared to have made ~2.5 years ago to the "generic"
float->float conversion routine appears to be incorrect and I've backed
it out.
- Floating-point conversions on SGI's which converted denormalized values
would be mapped to zero instead of being propertly preserved in the new
type. This was addressed by an SGI-specific system call to prevent the
behavior.
Solution:
Described above, generally.
Platforms tested:
FreeBSD 4.9 (sleipnir)
h5committest
Misc. update:
release_docs/RELEASE update forthcoming...
Bug fix & code cleanup
Description:
Allowing the library to call malloc with a size of 0 bytes causes problems
for some users, so we check for allocations of 0 bytes and disallow them now.
Cleaned up some code which could call malloc with 0 size.
Changed some code calling HDmalloc directly to call H5MM_malloc(), which
allows us to check for 0 sized allocations.
Platforms tested:
FreeBSD 4.9 (sleipnir)
too minor to require h5committest
Update
Description:
Added check for correctly working basename and xargs programs. Mike
McKay was having problems with broken xargs. The basename check was
just a good idea.
Platforms tested:
Linux & Arabica (trivial change already done in mainline branch).
Misc. update:
Description: Changes version to 1.6.1-post0 and updated
RELEASE.txt and HISTORY.txt filese fro the new version.
Solution: N/A
Platforms tested: N/A
Misc. update:
Description: I run bin/release to create an hdf5-1.6.1 release tar
ball. Now I am checking in modified files before
tagging the release.
Solution: N/A
Platforms tested: N/A
Misc. update:
Description: Bumped the version number to 1.6.1-pre2 after creating
a tar ball for the third round of testing
Platforms tested: bin/h5vers -s 1.6.1-pre2 on eirene
Misc. update:
Description: Bumped up the version number after creating a tar ball
for the second round of testing
Solution: N/A
Platforms tested: done with bin/h5vers on eirene
Misc. update:
Bug fix
Description:
The MPI_File_set_size() routine on ASCI Red is not able to extend files
so that they are larger than 2GB.
Solution:
Add an extra macro which controls whether MPI_File_set_size() can handle
>2GB offsets or if our "older" way of reading a byte, then writing a byte at
the appropriate offset should be used.
Platforms tested:
FreeBSD 4.9 (sleipnir)
h5committest
Description: Run bin/h5vers script to change version to 1.6.0-post0
after creating release tar ball and tagging the release.
Modified HISTORY.txt and RELEASE.txt for
1.6.0-post0
1.6 branch is open for checking in source code.
Solution:
Platforms tested:
Misc. update:
Description: Changed version number to be 1.6.0 with empty substring
for the release
Solution: Used bin/h5vers -s 1.6.0 to update all necessary files.
Platforms tested: verbena
Misc. update:
update for release
Description:
Set the version information to 1.6.0-pre1 to get ready for
v1.6 release.
Platforms tested:
h5committested.
Misc. update:
Bug fix.
Description:
There was a bug fix for AIX machine when Poe is used to
launch programs, that is in parallel mode. The fix is hostname
dependent.
Solution:
Removed the hostname dependence and let the fix apply to all
AIX machines. But put in a safety net--if $HDF5_AIX_NOPATCH
is set to non-null, it will not use the fix but use the
original code. (Don't expect this being used.)
Platforms tested:
Tested in Copper both with and without $HDF5_AIX_NOPATCH set.
Did not run h5committest since this really applies to AIX
systems only.
Misc. update:
Code cleanup
Description:
Make the default for the function stack work like the default for the
API tracing: when debug is enabled, the function stack defaults to on and
when debug is disabled, the function stack defaults to off.
Platforms tested:
FreeBSD 4.8 (sleipnir)
h5committest
