| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
| |
Bug Fix (sorta)
Description:
"small" contiguous hyperslabs were not being detected correctly by
H5S_hyper_select_contigous() leading to poorer performance than possible.
Solution:
Corrected check for small hyperslabs. Also cleaned up the H5S_find() code.
Platforms tested:
FreeBSD 4.5 (sleipnir)
|
|
|
|
|
|
|
|
|
|
|
|
| |
Purpose:
Bug fix(#697)
Description:
Variable-length string is not treated as string.
Solution:
Added character set and padding as VL string's attributes. They can be
set and retrieved.
Platforms tested:
Solaris 8, IRIX64 6.5 parallel, and FreeBSD.
|
|
|
|
|
|
|
|
|
|
|
| |
Purpose:
Bug fix(#697)
Description:
Variable-length string wasn't treated as string.
Solution:
Added character set and padding into VL string type.
Platforms tested:
FreeBSD
|
|
|
|
|
|
|
|
|
| |
HDF4 Removal
Description:
There were some testfiles still left after we removed HDF4 from the
HDF5 tree...
Platforms tested:
Linux
|
|
|
|
|
|
| |
Doc Change
Description:
Documented the fix for the 1024 byte object name limitation...
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
feature
Description:
Added -fsize <fsize> option which controls the family file size
used. This can be used to test the file size limits of a machine
or file system.
Platforms tested:
modi4 (passed even 20GB file size).
Eirene (started to fail when 2GB is used. Expected since linux 2.2
does not support large than 2GB file size.)
burrwhite (passed up to 4GB. Expected since Linux 2.4 supports larger
than 2GB file size.) Then it failed at 4GB and beyond. This is
probably a bug in the family file driver.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Purpose:
Bug Fix
Description:
Parallel Fortran wasn't working on Modi4. The tests for parallel
MPI Fortran were failing to find MPI files.
Solution:
Changed the AC_TRY_FLINK() macro so that libraries are included
at the end of the link line so that unresolved symbols can be
found...
Platforms tested:
Modi4
|
|
|
|
|
| |
Merge of name component length limit bugfix from 1.4 branch.
A couple of very minor typos fixed.
|
|
|
|
|
| |
Merge of name component length limit bugfix from 1.4 branch.
A couple of very minor typos fixed.
|
|
|
|
|
| |
Merge of name component length limit bugfix from 1.4 branch.
A couple of very minor typos fixed.
|
|
|
|
|
|
|
|
| |
Merge of name component length limit bugfix from 1.4 branch.
A couple of very minor typos fixed.
2002-03-18 14:30:58 Robb Matzke <matzke@arborea.spizella.com>
* H5B_assert: Fixed typos in comments.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Purpose:
Bug Fix
Description:
Hrm...When I was restoring the LDFLAGS variable after a failure, I
fergot to put a $ on the saved_LDFLAGS variable during the
assignment.
DOH!
Solution:
Added the $.
Platforms tested:
Modi4
|
|
|
|
|
|
|
|
| |
Purpose:
add hdf5cpptest.bat in the all.zip
Description:
Solution:
Platforms tested:
|
|
|
|
|
|
|
|
|
|
|
|
| |
Purpose:
rearrange project setting
Description:
by default, no c++ library or tests will be built. User will enable by checking dependencies by themselves to build c++ library.
The old all.zip somehow build c++ libraries.
Solution:
correct it by disable c++ dependency.
Platforms tested:
windows 2000
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Purpose:
fix a windows bug
Description:
1. To create a >4GB file, fstati64 has to be used instead of fstat.
change fstat to fstati64 for WIN32 macroes. Some discussions are going on
the general issue on how to better handle with WIN32 or other similar platform.
This check-in is just a reminder not to forget the windows bug.
2. erase a WIN32 macro(include winsock2.h) at h5detect.c. It is not a problem now.
Solution:
use fstati64 instead of fstat for win32.
Platforms tested:
windows2000(confirmed at linux machine eirene)
|
|
|
|
|
|
|
| |
New Feature
Description:
Added support for the IBM PowerPC AIX architecture. Really just a
copy of the RS6000 AIX config file...
|
|
|
|
|
|
| |
Update release notes
Description:
Document H5Gget_objinfo() bug fix (fixes bug #732)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Bug Fix
Description:
Regression test for following bug:
The H5Gget_objinfo() function was not setting the 'fileno' field in the
H5G_stat_t struct passed in.
Solution:
Added a "file serial number" to each file currently open in the library
and put that in the 'fileno' field. If a file is opened twice (with
H5Fopen) and the VFL driver detects that it is the same file (i.e. the
two file structures have the same "shared file info" in the library's
memory structures), they will have the same serial number.
This serial number has two drawbacks:
- If a VFL driver doesn't/can't detect that two calls to H5Fopen with
the same file actually _are_ the same file, each will get a
different serial number
- If the same file is closed and re-opened, the serial number will be
different.
It is be possible to fix the second drawback for many VFL drivers, but it
would be a lot of effort and probably isn't worth it until we've got a
good reason to do it. Dunno if we'll ever be able to fix the first
drawback...
Platforms tested:
FreeBSD 4.5 (sleipnir)
VS: ----------------------------------------------------------------------
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Bug Fix
Description:
The H5Gget_objinfo() function was not setting the 'fileno' field in the
H5G_stat_t struct passed in.
Solution:
Added a "file serial number" to each file currently open in the library
and put that in the 'fileno' field. If a file is opened twice (with
H5Fopen) and the VFL driver detects that it is the same file (i.e. the
two file structures have the same "shared file info" in the library's
memory structures), they will have the same serial number.
This serial number has two drawbacks:
- If a VFL driver doesn't/can't detect that two calls to H5Fopen with
the same file actually _are_ the same file, each will get a
different serial number
- If the same file is closed and re-opened, the serial number will be
different.
It is be possible to fix the second drawback for many VFL drivers, but it
would be a lot of effort and probably isn't worth it until we've got a
good reason to do it. Dunno if we'll ever be able to fix the first
drawback...
Platforms tested:
FreeBSD 4.5 (sleipnir)
VS: ----------------------------------------------------------------------
|
|
|
|
|
|
|
|
|
|
|
|
| |
Bug Fix
Description:
I wasn't testing if the Fortran compiler could actually do the MPI
compilation tests.
Solution:
Changed the configure script so that it uses Fortran 90 to test the
MPI compilation stuff instead of the MPI C compiler...
Platforms tested:
AIX and Linux
|
|
|
|
|
|
|
|
| |
Code removal
Description:
Removed the HDF4 source files from the HDF5 tree. The directories
will remain. Use the "-P" option when doing a cvs checkout or update
to "prune" the empty directories from your personal tree.
|
|
|
|
|
|
| |
Update
Description:
Reflect the removal of the HDF4 stuff from the HDF5 library
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Purpose:
Bug Fix
Description:
The new way of detecting LibZ (just specifying the directory where
include/ and lib/ are) wasn't propagated down to the Fortran
directory.
Solution:
Added that code...
Platforms tested:
AIX and Linux
|
|
|
|
| |
Update release notes.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Bug Fix
Description:
Regression test for following bug:
When reading a contiguous hyperslab that spanned the entire dataset and
was larger that the type conversion buffer, the hyperslab routines need
to fill the type conversion buffer and then return to the I/O routines.
When the I/O routines resume the hyperslab operation, it was possible to
have a combination of coordinates which caused the hyperslab iterator
to incorrectly advance in the file, causing some data to be re-read or
re-written.
Platforms tested:
Linux (eirene)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Bug Fix
Description:
When reading a contiguous hyperslab that spanned the entire dataset and
was larger that the type conversion buffer, the hyperslab routines need
to fill the type conversion buffer and then return to the I/O routines.
When the I/O routines resume the hyperslab operation, it was possible to
have a combination of coordinates which caused the hyperslab iterator
to incorrectly advance in the file, causing some data to be re-read or
re-written.
Solution:
Corrected the H5S_hyper_iter_next routine to correctly handle contiguous
hyperslabs that span the entire dataset dimensions.
Platforms tested:
Linux (eirene)
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Purpose:
To clarify where INSTALL files are located.
Description:
The README.txt refers to the INSTALL files as though they
were in the top HDF5 directory. They are not there so this
was confusing to users. Added a line saying they were located in
the release_docs/ directory.
|
| |
|
|
|
|
|
|
|
|
|
| |
Code Motion
Description:
Removal of HDF4 from the configure/Makefiles. This is a precursor to
the actual physical removal of the HDF4 tools from the HDF5 tree.
Platforms tested:
Arabica, Dangermouse
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Bug fix
Description:
Old config assume compiler is the SGI compiler if it is not gcc.
It would apply all SGI cc options to the $CFLAGS. This would cause
problem if a non-cc non-gcc compiler is used.
Solution:
Verify the compiler is indeed the SGI compiler before applying all those
cc specific options to the $CFLAGS.
Platforms tested:
modi4, both parallel serial, gcc or cc, -64 or n32.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Purpose:
1. fix a bug on all_withf90.zip
2. update windows zlib library to 1.14 version
Description:
1. somehow the workspace and project files were not totally updated on all_withf90.zip
update it now.
2. Update windows zlib library to the 1.14 version in responding to the security problem of zlib.
This updating will not affect other platforms.
Solution:
Platforms tested:
windows 2000
|
|
|
|
| |
Updated the help message to include the diff option.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Purpose:
Bug fix
Description:
I borrowed function HDpackFstring from the HDF4 Library and
left name unchanged. It causes linking problems for Fortran users
that use both HDF4 and HDF5 Libraries in their applications.
Solution:
Changed the name to be HD5packFstring
Platforms tested:
Solaris 2.7
|
|
|
|
|
|
|
|
|
| |
Purpose:
test the H5Dset_extend function
Description:
changed the example for more easy debugging
Platforms tested:
w2000, linux
|
|
|
|
|
|
|
|
|
| |
Purpose:
updated the H5D_update_chunk function
Description:
removed some debugging code headers
Platforms tested:
w2000, linux
|
|
|
|
|
|
|
|
|
| |
Purpose:
added a new function H5D_update_chunck that will update the chunk information; for the moment this function
just has debugging of the b-tree
Platforms tested:
w2000 , eirene
|
|
|
|
|
|
|
|
|
|
| |
Purpose:
code clean up
Description:
just some clean up of the functions H5D_set_extend and H5S_set_extend before the big change
(changing chunk info in the b-tree struct of the dataset)
Platforms tested:
w2000, eirene
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Purpose:
Bugfix
Description:
Internally created socket wasn't closed
Solution:
In my last commit I only fixed the case for sending data over a socket.
There was also a resource leak for the receiving side where an internally
created socket wasn't closed. Same wrong logical condition, same fix.
Platforms tested:
Linux, SGI
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Purpose:
Bugfix
Description:
If the socket, used for data streaming by the Stream driver, was created
by the driver itself, it did not close it after the file had been closed.
A resource leak occured.
Solution:
This bug was just introduced due to a logical condition.
Fixing the condition solved the problem.
Platforms tested:
Linux, SGI
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Feature/bug fix
Description:
The 'snapshot diff' command is run in all cases, even after the initial
"snapshot diff" and hosts are polled to run the test. It would not cause
any harm except wasting time repeating diff'ing. Also, the path is
quite right to invoke snapshot by merely "bin/snapshot diff" since it
has not "cd" to the right directory yet.
Solution:
Added a new option of "-nodiff" to skip the special diff request.
Then make "runtest" to call itself again with it to prevent
any further unnecessary diff'ing.
Platforms tested:
eirene
|
|
|
|
|
|
|
|
|
|
|
| |
New feature
Description:
"snapshot diff" will just run the diff and exit 0 is no significant
differences found between current and previous versions.
Runtest will try a "snapshot diff" and will skip test if no significant
differences are found.
Platforms tested:
eirene
|
|
|
|
|
|
|
|
|
|
|
|
| |
Bug-ish Fix
Description:
"make check" would barf in this directory since there's not a
"check:" target.
Solution:
Added a ".PHONY" entry so that "make checks" and the like won't barf
when they enter the pablo directory.
Platforms tested:
Linux
|
|
|
|
|
|
|
|
|
|
| |
Bug Fix
Description:
The Fortran module files weren't being uninstalled.
Solution:
Added them to the 'uninstall:' list...
Platforms tested:
Linux
|
|
|
|
|
|
|
|
|
|
| |
dpss removal
Description:
Removed dpss module since we no longer have that in the source. Also
fixed where the H5Tinit.c file was being looked for and how it was
compiled...
Platforms tested:
Linux
|
|
|
|
|
|
| |
*sigh*
Description:
Needed to point the sed script to the CORRECT pablo directory...
|
|
|
|
|
|
|
|
|
|
|
| |
Bug Fix
Description:
Needed more -I flags to catch some of the include files.
Solution:
Added them. Cleaned up the way include files and -D defines were
specified in the Makefile.
Platforms tested:
Linux
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Bug Fixes
Description:
Fixed some bugs. The CPPFLAGS wasn't being included into the
Makefile. Also, there's a sed script which needed to be pointed to
with the $(top_srcdir) macro.
Solution:
Added @CPPFLAGS@ to the CPPFLAGS line and put $(top_srcdir)/ before
the sed script file's name.
Platforms tested:
Linux
|
|
|
|
|
|
|
|
|
|
|
|
| |
Bug Fix
Description:
Didn't need to test that the Pablo library had a function in it only
that it was there.
Solution:
Removed that check. Just checked if we can actually find the physical
library and include files where the user tells us they're hiding.
Platforms tested:
Linux
|
|
|
|
|
|
|
|
|
|
|
|
| |
Bug Fix
Description:
Fixed wrong test for the HAVE_PABLO flag. Was testing if it was not a
null string when I should have been testing if it was equal to "yes".
Solution:
Changed test so that it checks if it's equal to "yes" instead of
non-null...
Platforms tested:
Linux
|