Bug fix.
Description:
The ${TR}, though avoid the error, is inconvenient. It is needed
because configure.in use the char range in the style of 'a-z'.
The other style of '[a-z]' is more commonly accepted by all tr
but autoconf tends to strip away [], making the syntax rather
clumsy.
Solution:
Learned from autoconf that it avoids the use of character range
by just spell all the letters out. Changed our tr commands to
use those variables defined by autoconf. Also removed the
definition of ${TR} since it will cause inconsistancy when
autoconf also use plain 'tr' in its generated code.
The Makefile.in are changed because the elimination of ${TR} from
configure triggered its removal from all Makefil.in. That is okay
because ${TR} is not used at all in Makefile.
Platforms tested:
h5committested. (sol failed to connected). also tested in shanti
using both /usr/ucb/tr and /bin/tr (the bad one before.)
Misc. update:
Updated both INSTALL and RELEASE files.
Updating project file
Description:
Due to the new added source codes under hdf5/src.
Solution:
Project file has to be changed to reflect this
Platforms tested:
VS 6.0 ( Failed during compiling because of compiler failure)
VS 7.0
Everything okay except that several h5repack tests get skipped.
Don't know whether this happens on other platforms.
h5repack -i test_scaleoffset.h5 -o out.test_scaleoffset.h5 -f dset_none:S+O=31 -
SKIPED-
h5repack -i test_scaleoffset.h5 -o out.test_scaleoffset.h5 -SKIP
ED-
h5repack -i test_scaleoffset.h5 -o out.test_scaleoffset.h5 -f dset_scaleoffset:N
ONE -SKIPED-
h5repack -i test_all.h5 -o out.test_all.h5 -SKIP
ED-
Misc. update:
Updating project file
Description:
New source code has been added,
project files need to be updated.
Solution:
Platforms tested:
VS 6.0(build failed due to compiler problem)
VS 7.1(.Net 2003)
Everything okay except that several h5repack tests get skipped.
Don't know whether this happens on other platforms.
h5repack -i test_scaleoffset.h5 -o out.test_scaleoffset.h5 -f dset_none:S+O=31 -
SKIPED-
h5repack -i test_scaleoffset.h5 -o out.test_scaleoffset.h5 -SKIP
ED-
h5repack -i test_scaleoffset.h5 -o out.test_scaleoffset.h5 -f dset_scaleoffset:N
ONE -SKIPED-
h5repack -i test_all.h5 -o out.test_all.h5 -SKIP
ED-
Misc. update:
new function
Description:
added H5LTfind_attribute as a public function, a wrapper for the already existing private function
H5LT_find_attribute
Solution:
Platforms tested:
linux
solaris
Misc. update:
Description: Yesterday, a definition of the macro YY_BUF_SIZE of 256KB
was committed in, but copper complained it can't be redefined.
Solution: Added #ifdef and #undef to make sure the macro is undefined
first. Also integrated a complicated compound type test. It reads
input from a text file. The datatype is unusually large, of 101 member
fields.
Platforms tested: h5committest and fuss.
Description: The default size for input buffer of Lex is only 8K. Some
application has input string far bigger than it.
Solution: Increase the size by defining YY_BUFFER_SIZE to be 256K (262144)
in H5LTanalyze.l
Platforms tested: fuss - simple change.
Code checkpoint
Description:
Checkpoint fractal heap improvements, as well as move the free space
manager code that it's using into a separate package.
Platforms tested:
FreeBSD 4.11 (sleipnir)
Linux 2.4/64 (mir) w/C++ & FORTRAN
Linux 2.4/32 (heping)
Solaris 2.9 (shanti)
AIX 5.? (copper) w/FORTRAN & parallel
Bug fix.
Description:
Some machines (e.g., HPUX) will have off64_t defined but no support
for stat64 unless certain LargeFile macro is turned on. This caused
the last fix on H5private not quite right which caused compiling failures.
Solution:
Added stat64 and fstat64 tests and then will use them only if they
are supported.
Platforms tested:
Tested on kelgia, copper and heping (pll).
(Compiling alright but tests for kelgia and heping are not done.
expect no problems.)
Description: When --enable-group-revision flag was used, h5fget_filesize_f
function returned different value from expected one. Test failed
with false negative result.
Solution: Added Fortran function h5_group_revision_f and its
C stub to check if macro H5_GROUP_REVISION is defined.
Expected value from h5fget_filesize_f is set up accordingly.
Platforms tested: copper, shanti and heping with and without
--enable-group-revision configuration flag
Misc. update:
Description: Added support for Zlib compression on VMS
Solution: Modified command files to add compilation and linking with
the ZLIB library.
Platforms tested: VMS servere with the VAX floating datatype;
will test IEEE option later
Misc. update:
Description: Function prototype H5E_walk_t and structure H5E_error_t wasn't backward
compatible.
Solution: Make them compatible with v1.6 and provide new definitions of H5E_walk_stack_t
and H5E_error_stack_t.
Platforms tested: fuss and h5committest.
Bug fix.
Description:
C++ testhdf5 failed when it tried to inspect the size of a file
via the HDstat call. The reason was that the CFLAGS has -D_LARGE_FILES
hardset in it while the CXXFLAGS does not. So, C is using an off_t
that is 8 bytes while C++ is using off_t as 4 bytes. C is using
a version of 64bits stat/off_t/etc while C++ uses the 32 bits version.
Thus a failure.
Solution:
Added -D_LARGE_FILES to $CXXFLAGES so that both C and C++ are using
the same version of stat/off_t/etc.
Platforms tested:
Tested in Copper only, both 32 and 64 bits since the changes affected
the AIX platform only.
Bug fix for collective chunk IO
Description:
Several options have been provided inside HDF5 library for
obtaining chunk addresses when doing collective chunk IO.
One option is to obtain chunk addresses for one process and broadcast
to other processes. This option needs all processes to participate.
If using link-chunked IO without any optimizations,
sometimes this is not true due to the random initialization for one variable at mpich 1.2.7.
This is a bug inside the collective chunk IO code.
Solution:
1.Initalize all the variables to some safe numbers,
2. Avoid using MPI broadcast to obtain the chunk address if possible
until more performance studies have been done.
3. Seems okay to obtain chunk addresses individually for each processor.
This option may cover most cases.
Platforms tested:
h5committest(copper is not usable)
NCSA teragrid (mpich 1.2.5)
mir 64-bit linux (mpich 1.2.6)
Misc. update:
bug fix.
Description:
Previous H5private.h would attempt to use the off64_t/stat64/etc
by checking just sizeof __INT64 being 8. This caused errors in
some machines like alpha cluster which is a 64bit machine. Its
compiler supports the type __int64 but it does not support
off64_t since its off_t is already 64bits big. The above code
casued the compiler to complain about the unknown off64_t and
such.
Solution:
H5private.h:
Changed the code to use the pseudo standard of off64_t/stat64/etc
only if sizeof(off_t) is not 64 bits AND sizeof(off64_t) exists
and is 64 bits. This assumes if off64_t is defined, all those
stat64, fstat64, etc are supported too.
configure.in:
configure:
Added the testing of sizeof(off64_t) to support the above solution.
Platforms tested:
h5committested. Also tested at LANL QSC.
Purpose: Maintenance
Description: dtypes.c compilation failed with gcc 4.1 due to the
missing prototype of the opaque_funcs function.
Failure was reported by a user who tried to build
hdf5-1.8.0-alpha2.
I reproduced the failure on sleipnir with gcc41
compiler.
Solution: Added prototype definition.
Platforms tested: sleipnir with gcc41, heping and copper
Misc. update:
Description: Comitting files modified by the bin/release script
before tagging the release.
Solution:
Platforms tested: released tar ball was tested on heping, and copper
64-bit sequential and 32-bit parallel
Misc. update:
Description: Added information about compilation problems on Altix SGI
with Intel v9.0 compilers for testmeta.c test
Marked platforms on which alpha2 was not tested.
Solution:
Platforms tested:
Misc. update:
Updating the windows DLL project file
Description:
new file H5HFiter.c has been added
project file needs to be reflected
Solution:
Platforms tested:
VSMS 6.0
Misc. update:
Updating windows project file
Description:
new file H5HFiter.c has been added
project file needs to be reflected
Solution:
Updating the project file
Platforms tested:
VS 6.0
Misc. update:
work-around solution for special cases in collective IO
Description:
For collective IO
if some processes don't have any contributions to IO, even with the new SGI compiler(7.4.4m), the testing program will be hanged. Previously only thought it didn't work with old compiler. It turned out not to be true.
Solution:
Turned off the special flag: H5_MPI_SPECIAL_COLLECTIVE_IO_WORKS
Platforms tested:
UCAR IRIX 6.5
this file only affects IRIX 6.x system. No need to test at other platforms.
Misc. update:
Purpose: Maintenance
Description: fheap test failed on VMS due to the missing H5HFiter module
Solution: Updated make.com file to include the missing module.
Platforms tested: VMS server with IEEE option.
Misc. update:
Bug fix
Description:
A datatype wasn't being closed in th5s.c
Solution:
This minor oversight caused an error with my Object Header code.
The datatype is now closed in the test.
Platforms tested:
windows, mir, copper
Purpose: Bug fix for VMS
Description: I am not sure why I didn't see this bug before ;-O.
H5_HAVE_FILE_VERSIONS macro was added (by me) to the wrong place
causing test program to get creation property list from a non-existing
file object. As a result test program failed with access violation
error.
Solution: Fixed.
Platforms tested: VMS server and copper (just in case)
Misc. update:
Purpose:
Bug fix
Description:
The Daily Test errors were due to H5_CFLAGS not being included when
configure tested the sizes of some values.
Rolled back the offending changes.
Solution:
There is a "correct" solution to this problem, which is to ensure that
the H5_CFLAGS are included in autoconf's tests.
This rollback is only temporary until the "real" fix can be applied.
Platforms tested:
copper (problem only in aix config file)
Description: Compilation of most of the Fortran files depends on existance
of three module files. On VMS the dependency was enforced by
listing source files for compilation command in the correct order.
It looks like that this approach doesn't always work and compilation fails
sometimes.
Solution: Hardcoded compilation of the threee files in the make.com file
Platforms tested: VMS server with IEEE option
Misc. update:
Description: Some VMS command files were broken, some needed
an update to catch up with the current code distribution.
Solution: Fixed
Platforms tested: VMS server with IEEE option. Will do more testing after
checking out a fresh CVS version.
Misc. update:
Bug fix
Description:
Fix two test bugs:
1) Unitialized variable bug in test of H5C_get_entry_status()
(in test/cache.c)
2) Incorrect initialization of constant in t_cache when running
with MPE. (in testpar/t_cache.c)
Solution:
1) Don't test uninitialize variable.
2) Correct initialzation of constant in MPE case.
Platforms tested:
Tested on Heping and Copper.
Misc. update:
Purpose:
Rename feature
Description:
Rename the "function stack" debugging feature to "call stack", so the H5FS*
prefix can be used for free space management code.
Platforms tested:
Not yet, but soon..
Purpose:
H5CC feature
Description:
Made H5_CFLAGS change to several more configuration files.
Solution:
Moved nonessential flags from CFLAGS to H5_CFLAGS for several more
platforms. If my guesses about which flags were nonessential were
wrong, we'll have Daily Test errors.
Platforms tested:
mir, cray, copper, juniper (OS X)
Code checkpoint
Description:
More progress on fractal heap, can now re-open an existing heap, although
the free space algorithm still needs work.
Also, use the new "pinned entry" metadata cache code.
Platforms tested:
FreeBSD 4.11 (sleipnir)
Linux 2.4 (heping)
Solaris 9 (shanti)
Linux 2.4/64 (mir)
Code cleanup/feature twist
Description:
Adjust recent H5AC routines to take H5F_t pointers instead of H5C_t
pointers, to match the rest of the H5AC routines.
This change propagated into a few of the tests, which also had some
compiler warnings cleaned up...
Platforms tested:
FreeBSD 4.11 (sleipnir) w/parallel
Linux 2.4/64 (mir) w/C++ & FORTRAN
Code cleanup, etc.
Description:
Fix some inconsistent coding in the packet table examples
Correct header file issues in C++ packet table wrapper
Platforms tested:
FreeBSD 4.11 (sleipnir) w/C++
Linux 2.4/64 (mir) w/C++ & FORTRAN
Code cleanup
Description:
Big clean up on high-level library code, including:
- Removing include of HDF5 private header file(!)
- Reduce number of compiler warnings
- Untangle header files, etc.
Platforms tested:
FreeBSD 4.11 (sleipnir) w/C++
Linux 2.4/64 (mir) w/C++ & FORTRAN
H5_CFLAGS change
Description:
Made the threadsafe flags in config/freebsd H5_CFLAGS so that they are
not passed on to h5cc.
Solution:
If user applications need the threadsafe flag to link properly against
the threadsafe HDF5 library, we'll see linking errors in make-install
when threadsafe is enabled, and can revert this change.
Platforms tested:
mir only (very minor change)
Add pinned entry capability to cache.
Description:
For frequently accessed cache entries, the protect/unprotect overhead
is sometimes a bottleneck.
Solution:
Allow entries to be pinned in the cache. Pinned entries can't be
evicted, but can be flushed or modified.
Platforms tested:
h5committested -- minus one small typo in test/cache.c whose fix was
tested on copper and heping only.
Misc. update:
Maintenance on Windows
Description:
change delimiter between preprocessor names from " " to ",".
Interl fortran doesn't take " " as delimiter.
Solution:
Platforms tested:
Misc. update:
Maintenance on Windows
Description:
All of the source code files were replaced by a new one.
Solution:
Platforms tested:
Windows XP with VS 6.0
Misc. update:
Bug fix
Description:
Removed some extra compiler flags that were being added in configure
Solution:
After my previous changes, some of autoconf's macros were realizing that
we had no CFLAGS defined and were helpfully supplying some to us, which
were causing errors on some platforms.
Initializing all of the *FLAGS variables prevented this from happening.
Platforms tested:
mir (minor change)
