| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
Clean up formatting and whitespace.
Tested on:
Mac OSX/64 10.7.3 (amazon) w/debug
(too minor to require h5committest)
|
|
|
|
|
|
| |
Reviewed HDF5-68
Tested: windows
|
|
|
|
|
|
|
| |
the object's
flush class action to ensure that cached data is flushed so that H5Ocopy will get
the correct data. (HDFFV-7853)
|
|
|
|
|
|
|
| |
Cleaned up comments by removing "C" notation comments
Tested: jam (gnu, intel)
koala (intel)
|
|
|
|
|
|
| |
a lack of sparse file support.
Minor change: tested on 64-bit Windows 7
|
|
|
|
|
|
| |
Tested: N/A
|
|
|
|
|
| |
Minor change: tested on jam (test not skipped) and Mac OS-X Lion (test skipped
due to HFS not supporting sparse files).
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
HDFFV-944: Fortran test problem with HDF5 182, intel 11.0, open-mpi-1.2.8
Description:
Moved libtool post-processing 'ed' snippet that replaces wl=""
with wl="-Wl," when intel compilers are used to the end of the
configure script, after libtool is actually generated. (I imagine
that at some point in time during a libtool version upgrade the
libtool script ceased being generated immediately after the libtool
initialization macro and is generated at the end of configure with
all other files).
Additionally, added a leading 'g' to the replacement invocation to
change all instances of wl="" to wl="-Wl," instead of just the
first that it comes across. (There's a separate one for each
compiler used (C, Fortran, C++)).
Tested:
Reproduced the reported make failure and tested resolution on
NCSA's Forge with OpenMPI built with Intel 12.0.4.
Also, h5committested.
|
|
|
|
|
|
| |
Update RELEASE.txt for HDFFV-398
Tested:
None needed, doc only.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
HDFFV-398: h5cc doesn't work with automake
Description:
Fixed compiler wrapper scripts to correctly detect compilation when
-MT preprocessor flag is provided, fixing a bug in which its *.o
argument was added to link_objs but not compile_args.
This previously broke usage of h5cc as the provided compiler in
configure scripts (like with h5edit) as automake may supply the -MT
option to the compiler via the makefiles.
Tested:
Tested using h5edit and h5committested.
|
| |
|
|
|
|
|
|
| |
h5ltget_attribute_string_f
|
|
|
|
|
|
| |
HDFFV-7965
Tested: jam (gnu), koala (gnu)
|
| |
|
|
|
|
|
|
| |
HDFFV-5897.
Tested: jam, durandal (too minor for full h5committest)
|
|
|
|
|
|
|
|
|
|
|
| |
update for HDFFV-7837 - h5diff: incorrect behavior with exclude-path option when unique object exist only in one file
Description:
Add the new test output list to test shell script.
This is based on the previous commit r22114.
Tested:
jam (linux32-LE), koala (linux64-LE), ostrich (linuxppc64-BE)
|
| |
|
|
|
|
|
|
| |
structure in H5D_read as I did in H5D_write.
Tested on jam - simple change.
|
|
|
|
| |
Tested: koala (gnu 4.1)
|
|
|
|
| |
Added check that HLDS fortran function do remove NULL character.
|
|
|
|
|
|
| |
in h5lt_get_attribute_string_f
Fixed size +1 error in HD5f2cstring
|
|
|
|
|
|
|
|
|
|
| |
Description:
Closed various HDF5 objects in DataSet::getInMemDataSize and
Attribute::getInMemDataSize to remove some memory leaks.
Platforms tested:
Linux/32 2.6 (jam)
Linux/64 2.6 (amani)
SunOS 5.10 (linew)
|
| |
|
|
|
|
|
|
|
|
| |
memory and caused seg fault. I added checks in two places to make sure the library returns error stack
when it fails to allocate memory. I didn't add any test to the test suite since there is no good way to test it. But I tested and verified the error stack by hand.
Tested on jam, koala, ostrich.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
core VFD) and HDFFV-7603 (core VFD has trouble with 2GB+ files on Windows).
Propagates the SEC2 driver fixes from HDF5 1.8.8 to the core VFD (mainly concerning the backing store). These fixes also conveniently fixed 7603 as well.
Tested on:
64-bit Windows 7
jam
koala
ostrich
|
|
|
|
|
|
| |
private functions and a macro according to Quincey's suggestion.
Tested on jam - simple change.
|
|
|
|
|
|
|
| |
opened with the MPI-IO VFD
Add test cases for these two routines
Jira issue HDFFV-7961
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Fix for HDFFV-7837 - h5diff: incorrect behavior with exclude-path option when unique object exist only in one file
Description:
If unique objects exists only in one file and try to exclude
the unique objects with --exclude-path option, h5diff missed
excluding some objects.
Fixed to exclude objects correctly in such case.
Test cases were added and tagged with jira#.
Tested:
jam (linux32-LE), koala (linux64-LE), ostrich (linuxppc64-BE), tejeda (mac32-LE), linew (solaris-BE), Windows (32-LE cmake), Cmake (jam)
|
|
|
|
|
|
|
|
| |
Minor code safety issue in test/fheap.c and whitespace in other files.
Tested on:
Mac OSX/64 10.7.3 (amazon) w/debug
(Too minor to require h5committest)
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
HDFFV-7523 JPSS: h5dump fails to open an attribute when using the -a option to specify an attribute with a slash in the name
Description:
Update command line help page and test generating file.
Previous commits: r22052, r22063
Tested:
jam (linux32-LE), koala (linux64-LE), cmake (jam)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
VFD is set).
This occurs due to the istore test creating very large files on systems which
do not have POSIX-like sparse file semantics. The large amount of I/O causes
the test to run for a very long period of time.
The fix was to copy the "big" test's sparse file check and only run the
largest sparse file test when POSIX-like sparse file semantics are found.
Tested on:
jam (nfs)
ostrich (nfs)
loyalty (ufs)
64-bit linux VM (ext4)
64-bit OS-X Lion (hfs, detected as not POSIX sparse)
64-bit Windows 7 (NTFS, detected as not POSIX sparse)
The OS-X failure to pass the sparse check is likely an error and will be
entered as a new bug.
|
|
|
|
| |
Remove "STAR" test as some platforms vary in interpretation.
|
| |
|
|
|
|
| |
Tested: jam (gnu and intel)
|
|
|
|
|
|
| |
(11.8-0) on jam and koala has trouble with the command "*p++ = *p OP tree_val" in the macro definition of H5Z_XFORM_DO_OP1 of H5Ztrans.c. It increments P first before doing the operation. So I break down the command into two lines: "*p = *p OP tree_val; p++;" I also reported the problem to PGI.
Tested on jam, koala, and ostrich.
|
| |
|
| |
|
|
|
|
| |
No test is needed.
|
| |
|
|
|
|
|
|
| |
Changed H5G*() to H5G*2() APIs for compatability.
Tested: (jam intel, --with-default-api-version=v16)
|
|
|
|
|
|
| |
above
tested: none
|
| |
|
|
|
|
|
|
|
|
|
| |
REF: HDFFV-1233
A high-level "H5LTpath_valid" routine for checking if a path is correct
Both Fortran and C version.
Tested: jam (gnu and intel)
|
|
|
|
| |
Tested: local linux
|
|
|
|
|
|
|
|
|
| |
operations like x*-100.
The parser mistaked "-" as substraction. I fixed it and also fixed another problem
with some special cases like 100-x and 2/x.
Tested on jam, koala, and ostrich.
|
|
|
|
| |
Tested: local linux
|
| |
|