| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
| |
Purpose:
Arrange codes for avoiding windows warnings
Description:
Solution:
put windows including header files into H5private.h
Platforms tested:
win 2000, confirmed at eirene
|
|
|
|
|
|
|
|
|
|
| |
Purpose:
Avoid windows warnings
Description:
Solution:
put some windows specified headers into this file
Platforms tested:
Win 2000, confirmed by eirene
|
|
|
|
|
|
|
|
|
|
|
| |
Code cleanup for C++
Description:
'xor' is a keyword in C++, causing problems compiling the library with a
C++ compiler.
Solution:
Change variables and structure fields from 'xor' to 'xor_val'
Platforms tested:
FreeBSD 4.2 (hawkwind)
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Typo fix and comment
Description:
The FUNC_ENTER of H5FD_mpio_flush had a wrong function name. Corrected
it. Also filled in the missing original author name.
Added a 'this is collective.' to all collective functions.
Platforms tested:
It was just editing. Can't go wrong. :-)
|
|
|
|
|
|
|
|
| |
Bug fix
Description:
Type-o
Solution:
uint should be uintn
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Code cleanup.
Description:
Fixed _lots_ (I mean _tons_) of warnings spit out by the gcc with the
extra warnings. Including a few show-stoppers for compression on IRIX
machines.
Solution:
Changed lots of variables' types to more sensible and consistent types,
more range-checking, more variable typecasts, etc.
Platforms tested:
FreeBSD 4.2 (hawkwind), IRIX64-64 (modi4)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Bug fix
Description:
H5P_DATASET_XFER was the name from the beginning through 1.2. It was
changed to H5P_DATA_XFER on v1.3.0. Then it was changed back to
H5P_DATASET_XFER right before the release of v1.4.0-beta2.
Define an alias here to help applications that had ported to v1.3.
Should be removed in later version.
#define H5P_DATA_XFER H5P_DATASET_XFER
Also removed the v1_2 compat condition since it is a v1.3 compat
issue now.
Platforms tested:
modi4 -64 parallel.
|
|
|
|
|
|
|
|
|
|
|
| |
Purpose:
several warning and bug fix for windows
Description:
different system calls on windows
Solution:
for win32, use only those system calls
Platforms tested:
windows 2000
|
|
|
|
|
|
|
|
|
| |
Purpose:
a warning fix for windows
Description:
Solution:
Platforms tested:
windows 2000
|
|
|
|
|
|
|
|
| |
Clean up code.
Description:
Cleaned up various compiler warnings.
Platforms tested:
FreeBSD 4.2 (hawkwind)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Purpose:
a bug fix
Description:
delete the line for unused defined variables on windows.
Solution:
delete the line.
Platforms tested:
windows 2000
[machines you have tested the changed version. This is absolute
important. Test it out on at least two or three different platforms
such as Big-endian-32bit (SUN/IRIX), little-endian-32(LINUX) and
64-bit (IRIX64/UNICOS/DEC-ALPHA) would be good.]
|
|
|
|
|
|
|
|
|
|
|
| |
Purpose:
a bug fix
Description:
Get rid of warning information for comments on windows(**/* */)
Solution:
add a space between ** and /*. Now it is ** /*
Platforms tested:
windows 2000
|
|
|
|
|
|
|
|
|
| |
Improved debugging output
Description:
Added a little more descriptive information to the output for h5debug
when debugging B-trees in the file.
Platforms tested:
FreeBSD 4.2 (hawkwind)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Bug fixes
Description:
Fix two bugs:
- Datasets with vlen datatype which were created but not written to
were not being read back in correctly from the file.
- If an existing space conversion path was found for a conversion, it
was possible that the optimized read/write routines would be used
inappropriately.
Solution:
Patched vlen datatype conversion code to correctly handle zero-length
sequences.
Added a check to the space conversion code to make certain that the
optimized conversion routines are still appropriate when an existing
path is found.
Platforms tested:
FreeBSD 4.2 (hawkwind)
|
|
|
|
|
| |
2000-12-29 14:13:43 Robb Matzke <matzke@llnl.gov>
*: Removed API tracing code from internal functions.
|
|
|
|
|
|
|
| |
2000-12-29 08:59:03 Robb Matzke <matzke@llnl.gov>
* H5FD_stream_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:57:58 Robb Matzke <matzke@llnl.gov>
* H5FD_stdio_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:56:44 Robb Matzke <matzke@llnl.gov>
* H5FD_srb_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:56:22 Robb Matzke <matzke@llnl.gov>
* H5FD_sec2_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 09:06:25 Robb Matzke <matzke@llnl.gov>
* H5FD_query: Marked `flags' argument as /*out*/
|
|
|
|
|
|
|
| |
2000-12-29 08:55:42 Robb Matzke <matzke@llnl.gov>
* H5FD_multi_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 13:26:28 Robb Matzke <matzke@llnl.gov>
* H5FD_mpio_write: Avoid MPI_Get_count() when using the LAM implementation of MPI.
This code must have other problems anyway because Kim
Yates has a similar kludge in place to avoid negative
return values from the same function.
2000-12-29 13:25:30 Robb Matzke <matzke@llnl.gov>
* H5FD_mpio_read: Avoid MPI_Get_count() when using the LAM implementation of MPI.
This code must have other problems anyway because Kim
Yates has a similar kludge in place to avoid negative
return values from the same function.
2000-12-29 11:28:13 Robb Matzke <matzke@llnl.gov>
* H5FD_mpio_flush: Read and rewrite the last allocated byte of the file to insure
that EOF>=EOA.
2000-12-29 09:32:49 Robb Matzke <matzke@llnl.gov>
* H5FD_mpio_write: Removed unused variable.
2000-12-29 09:32:15 Robb Matzke <matzke@llnl.gov>
* H5FD_mpio_write: Fixed a failure return value that should have been FAIL instead
of NULL.
2000-12-29 09:31:47 Robb Matzke <matzke@llnl.gov>
* H5FD_mpio_read: Removed unused variable.
2000-12-28 16:09:31 Robb Matzke <matzke@llnl.gov>
* H5FD_mpio_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:55:06 Robb Matzke <matzke@llnl.gov>
* H5FD_log_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:54:15 Robb Matzke <matzke@llnl.gov>
* H5FD_gass_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: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.
|
|
|
|
|
| |
2000-12-29 08:51:49 Robb Matzke <matzke@llnl.gov>
*: Just lined up a comment.
|
|
|
|
|
|
|
|
|
|
|
| |
2000-12-29 09:06:02 Robb Matzke <matzke@llnl.gov>
* H5FD_query: Marked `flags' argument as /*out*/
2000-12-29 09:05:49 Robb Matzke <matzke@llnl.gov>
* H5FDquery: Marked `flags' argument as /*out*/
2000-12-29 09:03:39 Robb Matzke <matzke@llnl.gov>
* H5FD_open: Reindented a line or two.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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)
|
|
|
|
|
|
|
|
|
| |
'beta3-snap0'
to indicate it is before beta3 release may be attempted.
Platform Tested:
eirene--compiled without errors.
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
Changed version number to beta3, now that beta2 is out.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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:
Set the background buffer type to different values for compound vs. vlen
& array datatypes.
Platforms tested:
Cray J90 (killeen)
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
| |
Code cleanup
Description:
Remove some warnings...
Platforms tested:
FreeBSD 4.2 (hawkwind) & IRIX64 6.5 (modi4)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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)
|