Small feature.
Description:
Change the wording for the use of HDF5_PARAPREFIX from Remark to hint.
Also made process 0 be the only one printing the hint rather all
processes duplicating the same hints.
Platforms tested:
Copper, both serial and parallel.
Did not do h5commit test since this is very localized and the above
tests covered both cases already.
Misc. update:
Bug fix
Description:
Fix three (!) bugs in szip filter:
- we were using bytes per pixel instead of bits per pixel
- we were using the size of the slowest changing dimension instead of
the fastest changing dimension to compute the blocks per scanline
parameter
- we swapped two parameters when setting up szip_options block.
Solution:
Addressed bugs above.
Platforms tested:
FreeBSD 4.8 (sleipnir)
h5committest not needed
Code cleanup
Description:
Remove debugging information and match bug-fix changes to szip filter
code.
Platforms tested:
FreeBSD 4.8 (sleipnir)
h5committest not needed.
fixed a typo on the usage message, redone the test files that deal with with
Description:
Solution:
Platforms tested:
Windows 2000 (octopus)
Linux 2.4 (rockaway)
SunOS 5.7 (arabica)
IRIX 6.5 (modi4)
Misc. update:
changes of input/ output format
Description:
on web page /RFC/h5diff
Solution:
Platforms tested:
Windows 2000 (octopus)
Linux 2.4 (rockaway)
SunOS 5.7 (arabica)
IRIX 6.5 (modi4)
Misc. update:
Bug fix
Description:
Raw data I/O on chunked datasets would attempt to allocate data structures
proportional to the number of chunks in the dataset on disk, instead of just
the number of chunks that the I/O operation would interact with, causing
operations on datasets with large #'s of chunks to fail (or become very slow),
even though the actual I/O operation was very modest.
Solution:
This is the "scalability fix" for chunked datasets that I've mentioned
we need to do, althought it's not the complete fix for the issue. Read on
for the details...
Only create data structures for the chunks that the I/O operation will
actually act on, reducing the amount of information allocated in memory,
normally.
I say "normally", because this algorithm has the same problems as the
original algorithm (worse actually, since the data structure for each chunk
is larger now) if _all_ the chunks in a dataset with a lot of chunks are
actually involved in the I/O operation. If that is the case, this code
will fail in a similar way.
To truly fix the problem, we would need to only create data structures for
a particular number of chunks, perform the I/O on just those chunks, then
release the data structures for those chunks and create data structures for
the next set of chunks to access, etc. However, I think this case is pretty
rare right now and we should worry about it after the 1.6.0 release.
Platforms tested:
h5committested
New feature
Description:
Added "fast comparison" code for hsize_t's, since they are used in th
raw data chunking I/O code now.
Platforms tested:
h5committested
Update
Description:
GPFS should only be checked for if the --enable-gpfs flag is used.
Otherwise, it shouldn't.
Platforms tested:
Linux (Configure only fix so only needed to test it to make sure the
configure does the right thing and that the build won't
break. I need to test it on a machine that has GPFS to make
sure it works there...)
Bug Fix
Description:
Lots of things. Mostly, multiple libraries declared on the command
line bothered some compilers. Then the order of the libraries is
important. Then if you are building static, you don't want an
"-lhdf5" flag in your compile line.
Solution:
Various hacks to remove redundant libraries from the compile line and
to keep the order of them and to replace -lhdf5 with the .a file when
building static.
Platforms tested:
Modi4 (Fortran & Parallel)
Verbena (Fortran & C++)
Arabica (Fortran)
Misc. update:
Bug Fix
Description:
The H5HG module had a couple of lines like the following:
HDmemcpy(foo + 1, foo, size);
This would overwrite the first character of "foo" for the total of
"size" bytes.
The H5Pfapl.c is an update of the trace information.
Solution:
Use HDmemmove instead. (Suggested by George Lewandowski at Boeing.
Thanks! :-)
Platforms tested:
Modi4 (Fortran & Parallel)
Verbena (Fortran & C++)
Arabica (Fortran)
Misc. update:
Fix
Description:
The SZLIB stuff was being checked by default. This isn't right as not
everyone will have SZLIB stuff.
Solution:
Made the default "no" instead of "yes"
Platforms tested:
Modi4 (Fortran & Parallel)
Verbena (Fortran & C++)
Arabica (Fortran)
Misc. update:
Code cleanup
Description:
Limit the scope on more function prototypes/macros/typedefs.
Platforms tested:
FreeBSD 4.8 (sleipnir)
h5committest not necessary.
Code cleanup
Description:
Remove special optimization and debugging flags for obsolete versions of
gcc.
Platforms tested:
FreeBSD 4.8 (sleipnir)
h5committest not needed.
Purpose: Maintenance for 1.6 release
Description: Fortran DLLs do not work.
Solution: Disable all DLL projects and build only static fortran library
and tests for 1.6. release
Platforms tested: This is a pure Windows change.
Windows 2000 with MSVC++ and Intel compilers.
Fortran debug SZIP test fails for both compilers.
Misc. update:
Improvement, IMO.
Description:
The parallel tests were run after all tools tests. For some parallel
systems, that could be a long time. Since tools are better tested
in serial mode and one would like to see the results of parallel
tests sooner in parallel mode, I moved the parallel tests before
the tools tests.
Platforms tested:
Only tested in Eirene, both serial and parallel modes.
No need for three platforms test since this is just a simple
Makefile change.
Fix
Description:
The way I was checking for -lfoo flags wasn't rigorous enough.
Solution:
Use a "grep" instead of the "case" statement. Also check that the
full "-lfoo" flag is matched instead of just part of it.
Platforms tested:
Linux (small fix)
Misc. update:
New test
Description:
Added test to check for dangling objects being handled correctly by the
library.
Platforms tested:
FreeBSD 4.8 (sleipnir)
h5committested
Bug fix.
Description:
When the same dataset is opened more than once and those references to the
object are left dangling, the library would not correctly shut down the dataset
API, potentially allowing the file to be truncated.
Solution:
"force" the dataset IDs to be released when the dataset API is being shut
down by the library.
Platforms tested:
FreeBSD 4.8 (sleipnir)
h5committested
Bug fix.
Description:
If the buffer holding the list of interfaces that are attempting to be
closed down becomes full, the library stops recording that an infinite loop has
occurred when shutting down the interfaces.
Solution:
Always return the correct "pending" information.
Also added ellipsis to the string of interfaces to try to make it more
obvious that the buffer became full.
Platforms tested:
FreeBSD 4.8 (sleipnir)
h5committested
Bug fix
Description:
Added missing line for file close degree setting for this VFD.
Platforms tested:
FreeBSD 4.8 (sleipnir)
h5committested
(Unfortunately, none of these tests actually exercised this driver... :-(
Bug fix
Description:
A few groups were left open after they were used.
Solution:
Closed them. :-)
Platforms tested:
FreeBSD 4.8 (sleipnir)
h5committested
A little change for project modification
Description:
libtestD.dll for debug mode is changed to libtestDd.dll to separate
from release version.
Solution:
Platforms tested:
windows 2000
Misc. update:
Bug fix
Description:
Iterating over the attributes of an object without any attributes was
returning FAIL instead of 0 as the RM states.
Solution:
Changed return value of H5Aiterate for objects without attributes to be 0
and added regression tests for this.
Platforms tested:
FreeBSD 4.8 (sleipnir)
h5committest not needed.
Small code cleanup
Description:
Remove redundant sanity check.
Added a note about a potential bug.
Platforms tested:
FreeBSD 4.8 (sleipnir)
h5committest not necessary.
Bug Fix
Description:
Some compilers aren't happy if you specify the same library multiple
times when linking. This caused HDF5 Lite to crash during tests on
Kelgia
Solution:
Modified the script so that the shared libraries are specified only
once for the commandline.
Platforms tested:
Kelgia (small fix).
Misc. update:
Description: when a datatype element size is bigger than I/O datatype
conversion buffer(1MB), library reports failure.
Solution: adjust conversion buffer to be at least equal to one element size
Platforms tested: h5committest
Bug Fix
Description:
When doing a "configure" using the h5cc script as the compiler, it
would fail to accept the "-E" flag as running the preprocessor. The
problem was that it was trying to link the file afterwards. Of
course, the file wouldn't be there, so it would fail.
Solution:
Changed it so that if the -E flag is used, then we don't try to link
(this is how it's done in mpicc...I must have copied it wrongly).
Platforms tested:
Linux & Kelgia (small change not needing full testing)
Misc. update:
Bug Fix
Description:
The newly added H5TEST_DLL{VAR} macros weren't defined if it wasn't
a Windows environment.
Solution:
"#define" them to "" and "extern" if not a WIN32 environment.
Platforms tested:
Linux (small change not needing full testing)
Misc. update:
Feature
Description:
Sometimes the total build process take a long time, especially in
parallel systems. Need some idea if some times are taking way
too long to process.
Solution:
Added timestamps marking the beginning and ending of tests in
one directory. This gives a rough idea of how much time the
tests use.
Platforms tested:
Tested only in Eirene since this is just a makefile thing and only
involve a simple command like echo and date.
Misc. update:
Add decriptions to use libtestD.dll.
Description:
libtestD.dll should be placed to a place that the user can find in order to
test HDF5 DLL within HDF5 workspace.
Solution:
Explained in document.
Platforms tested:
No need
Misc. update:
Add windows specified macro H5_TESTDLL for test routines.
Description:
See the previous CVS message.
Solution:
Platforms tested:
windows2000(will not affect other platforms)
Misc. update:
To add macro HDF5TESTDLL for windows libtest library.
Description:
Many HDF5 tests will use h5test.c.
So we create a libtest library to
1) make tests more organized and
2) make tests more consistent with other platforms
3) reduce compiling times
4) reduce dumplicated warnings possibily generated by h5test.c
However, we didn't create the corresponding libtest DLL correctly,
now, some warnings are generated because of this; so for this release,
we follow exactly DLL-DLL rules, to create an internal libtest DLL for
our test suites.
The application who used HDF5DLL will not have extra burdens to add
HDF5TESTDLL and this will reflect in the release.txt
Solution:
USE DLL import and export library by defining macro HDF5TESTDLL and HDF5TESTUSEDLL
Platforms tested:
Windows 2000(the macro will not affect on non-WIN32 platforms).
Misc. update:
Windows project-rearrangements, shut off warnings
Description:
1. H5Farray.c is no longer used, removed it from hdf5.dsp.
2. libtestD is supposed to be a windows DLL; however it is treated as static library in the past.
change it back to DLL and add HDF5TESTDLL and HDF5USETESTDLL.
Solution:
1. see above.
2. change h5api_adpt.h and h5test.h, add macro HDF5TESTDLL and HDF5TESTUSEDLL.
These changes will not affect other platforms.
Platforms tested:
windows 2000
Misc. update:
changed algorythm
Description:
changed the array_diff function to increment the read buffer with a size selected
by an appropriate native data type.
previously it was assumed, e.g. int size = 4 bytes
Solution:
Platforms tested:
Linux 2.4 (rockaway)
SunOS 5.7 (arabica, 64bit mode)
IRIX 6.5 (modi4)
Misc. update:
