Bug fix
Description:
When C flags are passed in using $CC variable, this can confuse test
commands in configure (for instance, CC='pgcc -tp k8-32').
Solution:
Previous solution didn't entirely solve problem. Wrote a sed snippit
to strip flags from $CC for purposes of test in configure.
Platforms tested:
mir (just a configure bug)
Feature--to provide a standalone mode for t_mpi.c so that it can
be built outside of PHDF5 environment.
Description:
Move definitions that are common to all parallel test programs
to a new header file called testpar.h.
Leave only Parallel HDF5 tests related definitions in testphdf5.h.
Platforms tested:
heping (pp) and modi4(PP). Copper was down.
Misc. update:
Removed GASS configuration and software packages associated with
it. The following software are no longer configurable.
checking for main in -lcrypto... yes
checking for SSL_get_version in -lssl... yes
checking globus_common.h usability... yes
checking globus_common.h presence... yes
checking for globus_common.h... yes
checking for globus_module_activate in -lglobus_common... yes
checking for main in -lglobus_gass_cache... yes
checking for main in -lglobus_gaa... yes
checking for main in -lglobus_gss... yes
checking for main in -lglobus_gss_assist... yes
checking for main in -lglobus_io... yes
checking for main in -lglobus_gass_transfer_assist... yes
checking for main in -lglobus_gass_transfer... yes
checking for globus_gass_open in -lglobus_gass_file... yes
Platforms tested:
h5committested (but copper was down.) tested in modi4 too.
typo fix and small improvement.
Description:
t_coll_chunk.c:
ccdataset_vrfy() was using a wrong routine name to identify itself.
testphdf5.c:
Add a definition of NFILENAME to be the common dimension size of
FILENAME[] and filenames[][] since they must have the same first
dimension size.
Platforms tested:
h5committested.
Bug fix.
Description:
"testphdf -p" would with data verification errors. The reasons were
that the MPIPOSIX driver file open and close, especially the close
routine provide no "coordination" between processes. The testphdf5
tests reuse the same file for test data file by opening using H5Fcreate
with the HDF5_FCC_TRUNC option. The test routines do not provide any
code to ensure that all processes have finished one test before moving
to the next test. Some "faster" process would have finished verifying
its portion of data as correct and move to the next test which opens
the same file with TRUNCATOIN which truncates the previous data file.
But some "slower" processes are still verifying the "previous" data
file which all of a sudden got truncated by the "faster" process.
Solution:
Technically, the test program should be fixed to ensure all processes
have finished one test before any is allowed to move to the next test.
OTOH, the MPIO VFD has no problem with this test because MPI-IO requires
File open and close be called collectively correct and ensure it is
returned properly.
I choose to fix the MPIPOSIX close routine to provide some sort of
coordination between processes by requiring all processes to have
completed the close of a file before it is returned to user space.
This makes the MPIPOSIX close routine behaves more like the MPIO
close routine, thus provide more protection for user applications
that fail to code in the coordination. But having the barrier
in the MPIPOSIX close routine would penalize applications where
it is "okay" for some processes to close its file handle and race
ahead to do other things since it is not going to access this file,
therefore whether other processes are still using the file is immaterial.
Maybe this protective coordination should be optional and can be turned
off by confident users who need not this sort of protection.
Platforms tested:
"h5committested" and tested in modi4 and tesla.
Misc. update:
Bug fix
Description:
Libtool simply doesn't seem to support shared libraries for pgcc, but
tries to build them anyway.
Solution:
Edited configure to disable shared libraries in libtool script when
pgcc is being used.
This is a more drastic fix than the problem requires, but it is
difficult to detect when this problem will occur. There is
discussion online about shared libraries with pgcc, so hopefully
libtool will support pgcc and this fix will become unneccesary.
Platforms tested:
sol, copper, mir, sleipnir
Misc. update:
Description: Condition check of macro H5_ULLONG_TO_FP_CAST_WORKS was accidentally
taken out in last revision. This macro is defined for Windows because Windows
doesn't support conversion from "unsigned long long" to any floating-point type.
Solution: Added it back to H5T_conv_ullong_xxx() functions(xxx is any of "float",
"double", or "long double").
Platforms tested: tested on Windows.
Bug fix
Description:
A test in configure.in redirected output in a way that made
mir (at least) unhappy (test: too many arguments).
Solution:
Changed the semantics so that mir was happy. This didn't seem to make any
other platforms unhappy, either.
Platforms tested:
eirene, modi4, copper, mir, sleipnir (only tested configure)
bug fix
Description:
H5DSget_scale_name, H5DSget_lablel return wrong value when truncating to 1
character array.
Solution:
fix it.
Platforms tested:
verbena,shanti,copper
Misc. update:
Bug fix.
Description:
The nbit filter does not check error when calling some utility functions
that can return a failure.
Solution:
Add error handling for these utility functions.
Platforms tested:
heping, copper
Misc. update:
Bug fix
Description:
C++ tests would die with strange linking-type errors.
Solution:
C++ build needs to be static, too. Applied -static flags liberally in
c++/src and c++/test directories.
Platforms tested:
sleipnir, heping
Bug fix
Description:
Fortran builds were dying with unknown flags.
Solution:
Fortran builds should be static, not shared. Static flags had been specified
for libraries, but apparently were also needed for executables.
Solved problem by adding static flag to everything in fortran directories.
Platforms tested:
mir, eirene
Purpose:
Bug fix
Description:
Libtool 1.5.14 added some extra flags that needed to be passed from the compiler
to the linker. icc did not handle this correctly and complained when it saw
unknown flags.
Solution:
Set the -Wl flag correctly on freebsd so that icc knows to pass flags through
to the linker.
Platforms tested:
sleipnir (gcc, g++, icc, gcc40)
Bug fix
Description:
h5vers would spit out the output that reconfigure script produced.
Solution:
Sent output from reconfigure to /dev/null. h5vers is now quiet as before.
Platforms tested:
verbena, eirene, heping
Modifications of nbit filter.
Description:
The nbit filter does not support datatypes other than integer,
floating-point as well as array datatype and compound datatype consisting
of integer or floating-point.
Solution:
Change the nbit filter to accept all datatype at the top level, and if
the datatype is not what described above, the filter will not do anything
to the data instead of generating errors.
Slight improvements of the filter's performance.
Platforms tested:
heping, copper
Misc. update:
Bug fix
Description:
Some machines and compilers were having trouble creating fortran libraries
as shared libraries.
Solution:
Added flag in Makefiles.am to create fortran libraries as shared libraries.
(This is how HDF5 was set up before automake changes; I forgot to add
these flags, and it didn't cause a problem until now.)
Platforms tested:
sleipnir, eirene, verbena
Misc. update:
New features & refactor
Description:
Add basic record removal (only handles level-0 B-trees currently)
Add query routine to check the number of records in a B-tree
Add debugging routine to check the address of the root node in the B-tree
Platforms tested:
FreeBSD 4.11 (sleipnir)
Solaris 2.9 (shanti)
Description:
Fixed typo in using namespace; it was mistakenly opening the namespace.
Platforms tested:
Linux 2.4 (heping)
Very minor, and tested 3 platforms for 1.6 branch
change
Description:
Minor changes to Dimension Scale API, to bring into alignment
with specification.
Solution:
Platforms tested:
verbena,shanti, copper64
Misc. update:
Description: Somehow, the hardware conversions between "long double" and other native floating-point
types were left out.
Solution: Added the hardware conversion functions in H5Tconv.c and test cases in dtypes.c.
Platforms tested: h5committest and fuss.
Misc. update: updated MANIFEST to replace bin/reconfigure.sh with bin/reconfigure
Bug fix
Description:
h5vers script called automake without using bin/reconfigure
Solution:
Altered h5vers script to use bin/reconfigure
Also:
***
CHANGED NAME OF reconfigure.sh TO reconfigure !
***
This matches the other scripts in the bin/ directory. Also changed
permissions on reconfigure so it can be executed.
Platforms tested:
eirene
Misc. update:
Description: The library didn't handle incorrect hardware conversion for datatype. It simply did
convert to incorrect data if any hardware didn't handle correctly.
Solution: During configuration, incorrect hardware conversion is detected and some macros are
defined. Use these macros to decide whether to register hardware conversion in H5T.c. If no hardware
conversion function is registered for certain pair of datatypes, software conversion function will
be used as the conversion path. Although slower than hardware conversion, we're more confident
software conversion is accurate.
So in one sentence to describe library's behavior, if some hardware conversion doesn't work well,
software conversion will be used instead.
Platforms tested: h5committest and fuss.
Misc. update: some changes to configure's comments.
Feature
Description:
Added code to dump the beginnng and last few lines of the
test log file if errors have occurred.
Platforms tested:
Tested the code itself separatedly but daily test is where
it is really tested. Should work.
Bug fix & new feature
Description:
Fix errors in tracking the total number of records "below" a node.
Add feature to find the n'th record in a B-tree
Platforms tested:
FreeBSD 4.11 (sleipnir)
Solaris 2.9 (shanti)
New feature, refactor code
Description:
Add call to search for a record in a B-tree by key value
Refactored some of the existing callbacks to simplify them.
Platforms tested:
FreeBSD 4.11 (sleipnir)
Solaris 2.9 (shanti)
Bug fix
Description:
c++/src directory was having trouble finding main HDF5 library.
Solution:
Replaced AM_CPPFLAGS with INCLUDES to include files in main src directory.
Platforms tested:
mir, modi4, verbena
feature
Description:
Starting to add a feature that will print out details from the snapshot
test logfile when the test fails. Only a debug statment is added to
see if snapshot is reporting error status correctly.
Platforms tested:
Not tested. Wait for daily test to show the result.
Bug fixes
Description:
Fix several bugs in B-tree insertion code, which now appears to be fully
functional. (Tested to 1,280,000 records at least...)
Add random record insertion test to shake out boundary conditions, etc.
Platforms tested:
FreeBSD 4.11 (sleipnir)
Solaris 2.9 (shanti)
Description: On some Cray, the size of "short" is 8 byte but only the low-order 4 byte
are over used(precision is 4 byte). The "perm" in struct "detect_t" contains "-1" for
bytes that aren't used, making detection of order invalid in function print_results().
Solution: Use a "for" loop to search through "perm" find the first non "-1" element,
and use it to decide the byte order of the machine.
Platforms tested: fuss - already tested for v1.6
feature
Description:
h5repack support for scaleoffset compression
Checking in early to help debug the filter.
Solution:
Added messages and command line to handle new scale offset filter.
Note: TESTS ARE DISABLED FOR NOW. The filter is not
complete, repack tests may fail due to know problems.
PLEASE DO NOT MESS WITH THE SCALEOFFSET TESTS AT THIS TIME.
They will be enabled when the filter is ready.
Platforms tested:
verbena,copper,shanti
Misc. update:
MANIFEST
Bug fix
Description:
This checkin addresses two bugs.
Firstly, I used the wrong semantics when detecting if $MAKE is defined to
the empty string or undefined.
Secondly, pmake on IRIX does not work well with automake's dependency tracking
if the build is not an in-place build.
Solution:
Fixed semantics in configure.in.
Disabled automatic dependency tracking automatically on IRIX. This is not
the optimal fix, but it should work fine as long as no one is doing HDF5
development on IRIX, and it is much easier than trying to detect the exact
situations in which dependency tracking fails (or than trying to fix dependency
tracking!).
Platforms tested:
heping, modi4 (pmake and gmake)
changed the function H5DSget_scale_name to return the size of the name buffer
added a test
Description:
Solution:
Platforms tested:
linux
solaris
Misc. update:
Bug fix
Description:
Discovered two small bugs.
When MAKE is defined as the empty string, a test in configure incorrectly
identifies it as pmake. Skipped this test if $MAKE is the empty string.
Two .h5 files produced by a test in the hl directory were not cleaned.
Updated the Makefile.am.
Platforms tested:
heping, modi4 (very minor changes)
