2000-12-29 08:53:43 Robb Matzke <matzke@llnl.gov>
* H5FD_family_query: The `flags' argument is advertised to be output only. Therefore I
added code to zero its value before the feature bits
are assigned.
2000-12-29 08:52:45 Robb Matzke <matzke@llnl.gov>
* H5FD_dpss_query: The `flags' argument is advertised to be output only. Therefore I
added code to zero its value before the feature bits
are assigned.
Updating debugging information for new features, etc.
Description:
Lots of the new features added to the library during the last year or so
have been added without updating the debugging routines used by h5debug.
Solution:
Added more of the new features (although not all of them) to the debugging
routines for h5debug. Also included some more information to expand on
the information printed from h5debug.
Platforms tested:
FreeBSD 4.2 (hawkwind)
Bug Fix
Description:
The #ifdef ... #else statement had no line breaks in it. This
caused the compiler on Sangamon to freak out saying the #ifdef
was invalid.
Solution:
Put line breaks in it.
Platforms tested:
Sangamon
Removal of spurious warnings
Description:
On HP-UX systems, the compiler would warn of a redeclaration of
H5G_entry_t in the H5Sprivate.h header.
Solution:
Removed the prototype declaration since H5Oprivate.h includes the
H5Gprivate.h header file already.
Purpose:
a windows bug fix
Description:
so that sec2 driver can support >2 G file on windows NTFS
Solution:
using lseek_i64 for windows platform
Platforms tested:
tested on windows 2000, confirmed on eirene and arabica
Purpose:
a windows bug fix
Description:
support > 2G file on windows NTFS
Solution:
using fsetpos to seek the address
Platforms tested:
windows 2000, confirmed on arabica and eirene.
Bug Fix
Description:
If the library was compiled with 'NDEBUG' defined, but the user's program
(the fortran API in this case) was compiled with 'NDEBUG' not defined, the
IDs returned from the library would appear to be incorrect.
Solution:
Removed 'ifndef NDEBUG' from around "H5I_TEMPLAX_MAX" definition and error
checking.
Platforms tested:
Linux 2.2 (eirene) & FreeBSD 4.2 (hawkwind)
Prepare for 1.4.0beta1 release
README:
src/H5public.h:
Updated with 1.4.0beta1 version information.
configure.in:
Changed default setting to --enable-production --disable-debug.
configure:
Derived from configure.in via autoconf.
Platforms tested:
Eirene (linux) running just the configure command and compared
difference with previous configure output to verify expected
difference.
Bug Fix
Description:
More descrimination is necessary for the type of background buffer needed.
Compound types need H5T_BKG_TEMP and vlen & array types need H5T_BKG_YES.
Solution:
Make the internal routine be more specific about the background type set.
Platforms tested:
FreeBSD 4.2 (hawkwind)
Bug fix
Description:
Non-optimized conversions have a memory overwrite bug when the destination
size of a compound datatype is greater than the source size.
Solution:
Corrected direction of walking through the destination array for final
copying.
Platforms tested:
FreeBSD 4.2 (hawkwind) & Cray J90 (killeen)
Bug fix
Description:
In H5FD_mpio_open, there was a mem-xfree of the file variable
before it ever gets alloc'ed. This is inside a failure condition
that rarely happened. But if it happens, it would be freeing
a null pointer.
Solution:
Removed the error code.
Platforms tested:
Modi4 -64 parallel. (Everything still works. :-)
Bug Fix
Description:
Compound datatypes weren't reading background data properly when used
with array or vlen fields.
Solution:
Changed to always read background information from file in those situations.
Platforms tested:
FreeBSD 4.2 (hawkwind)
Feature
Description:
H5Eprint used to print "thread 0" even in MPI-application.
Added code to print MPI-process rank ID (as in MPI_COMM_WORLD) to
give more information of which process is printing the messages.
Platforms tested:
IRIX64-64, both serial and parallel.
Bug fix.
Description:
Cray T3E (and J90?) was failing on partial I/O tests. The bug was in
the optimized hyperslab routines for cases where a hyperslab filled the
temporary datatype conversion buffer and the optimized hyperslab routine
needed to start in the middle of a hyperslab.
Solution:
Corrected code to detect the situation and read in the correct amount of
elements in the hyperslab.
Platforms tested:
Cray T3E (mcurie.nersc.gov)
Purpose:
Bugfix
Description:
Under SunOS 5.5 the symbol FIONBIO wasn't known.
Solution:
Include <sys/filio.h> which defines this symbol under Solaris.
Also put the UNUSED qualifier in the right place in a function
argument list (gcc 2.7.2 didn't like it before the type name).
Platforms tested:
SunOS 5.5 (hatteras), SunOS 5.6 t(thor.sistec.kp.dlr.de)
Bug fix
Description:
Compiler on Cray T3E has a weird problem with operations on size_t
variables.
Solution:
Change comparison to make Cray T3E happy.
Platforms tested:
Cray T3E (mcurie)
Bug fix
Description:
"UNUSED" macro was in wrong place for older versions of gcc
Solution:
Moved the "UNUSED" macro to the right of the H5FD_t type declaration and
the compiler was happy...
Platforms tested:
Solaris X86 2.5 (hatteras)
Purpose:
fix a bug
Description:
add <windows.h> for WIN32
Solution:
Add the following lines at the beginning of the file
#ifdef WIN32
#include <windows.h>
#endif
Platforms tested:
NT4.0,5.0, and LINUX
Code addition
Description:
The dumper needs to know when a datatype needs to be reclaimed, so I
added a small helper function to detect if a particular datatype is or
contains a particular class of datatypes.
Platforms tested:
Linux 2.2.16-3smp (eirene)
Patch on the patch of my code cleanup... :-)
Description:
Fix compiler problems with previous code patching...
Platforms tested:
Linux 2.2.16-3smp (eirene)
Bug fixes
Description:
Patch things back up from incompletely changing some variables in
yesterday's code cleanup, this should fix the compiler errors that Kent
and Bill have found in the CVS version of the code.
Also, fix a bug buried in the datatype conversions when compound datasets
were nested inside an array or variable-length datatype. Internally
require that any datatype which contains a compound datatype sets the
"need_bkg" conversion flag so a background buffer to pass to the compound
datatype conversion is allocated.
Platforms tested:
FreeBSD 4.2 (hawkwind) & Solaris 2.6 (baldric)
Bug fix
Description:
When the v1.2 compatibility code was turned on, internal functions in the
library were getting confused.
Solution:
Separated guts of H5Pget_driver call into an API function (the definition
of which depends on the compatibility switch) and an internal function
which always behaves like the v1.3/4 function. Replaced API function calls
in the library code with the internal function.
Platforms tested:
FreeBSD 4.2 (hawkwind)
Code cleanup
Description:
Several places in the code were using -2 as a default value for various
features. However, when a default value is returned from a function that
is supposed to return negative on failure, it was causing confusion and
extra work for users to check for the special value.
Solution:
Replaced hard-coded -2 values in the code with symbolic names, then changed
symbolic names to 0 instead of -2.
Platforms tested:
FreeBSD 4.2 (hawkwind)
Bug fix
Description:
Fixed some typo that cause compiling errors in parallel mode.
Also added a default case in the H5Pget_xfer code to catch
potential future added data transfer mode.
Platforms tested:
IRIX64-64, parallel.
Backward compatibility code
Description:
Add in code to allow the library to emulate the v1.2 API and behavior.
Platforms tested:
FreeBSD 4.2 (hawkwind)
Bug fix
Description:
The optimized MPI-IO calls, H5S_mpio_spaces_write/H5S_mpio_spaces_read,
are changed for collective data transfer only since they
call H5FD_mpio_setup to do setup to eveually call MPI_File_set_view
in H5FD_mpio_read or H5FD_mpio_write. MPI_File_set_view is a
collective call. Letting independent data transfer use this
route would result in hanging.
Solution:
For now, the checking is being done in
H5D_write and H5D_read before H5S_mpio_spaces_write/H5S_mpio_spaces_read
is called because the checking code in H5S_mpio_spaces_xfer, though with
the right idea, is not correct yet.
Platforms tested:
IRIX64-64 parallel.
Purpose:
Bug fix
Description:
H5S_mpio_spaces_xfer() did not do clean up all the times especially
the MPI_type freeing.
Solution:
Include the MPI_type freeing as part of cleanup code. Replaced
most HRETURN_ERROR(...) with HGOTO_ERROR so that cleanup code
will be executed.
Platforms tested:
IRIX64-64.
Purpose:
make mtime test available on windows
Description:
calculating time zone difference on windows
Solution:
1.Use /#if WIN32 #endif/ to make sure the modification will not affect other platforms.
2. use <sys/types.h> and <sys/timeb.h> on NT to obtain time zone difference.
Platforms tested:
windows 2000
Bug fix (feature, kind of)
Description:
The library used to hang if a collective dataset read/write request
does not have the same number of eventual MPIO request. Part of the
reason is that H5FD_read/H5FD_write immediately returns succeess
if it sees the request size is 0. This caused problem since other
processes with I/O to do would be hanging by waiting for the early
returned process(es).
Solution:
H5FD.c: disable the early return code in parallel mode. Make it
go on even with "nothing" to transfer.
H5D.c: the optimized MPIO xfer routines can handle collect calls correctly
when the condition is right (e.g., no conversion). When the COLLECTIVE
request cannot be handled correctly without the risk of hanging, the
COLLECTIVE is changed to INDEPENDENT calls for the eventual MPIO
calls.
Platforms tested:
IRIX64 parallel (-64, n32), IRIX64 -64 sequential, Linux sequential.
