| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
These are based on H5FDsec2, and will have to be re-worked heavily
for sub-filing.
Also added minimal test (based on existing sec2 tests) in test/vfd.c
Since sub-filing is mostly a parallel feature, most testing will have
to be moved to testpar. That said, a serial version of sub-filing will
be neeced eventually, so it makes sense to retain at least a stub in
the serial vfd tests.
Tested serial and parallel on charis and jelly. Encountered errors in
h5diff tests in the parallel builds, but am ignoring them as they also
appear in the version prior to this checkin.
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
in test/vfd.c. Note that this test uses only sec2 and stdio at present.
Since no VFDs support vector I/O at present, the vector I/O VFD calls
are translated to regular read/write calls in the VFD layer.
Tested serial and parallel, debug and production on charis, parallel
debug on jelly. Some seemingly un-related issues, but after consultation
with Richard, I'm proceeding with the checkin.
|
| | |
|
| | |
|
| |\
| |
| |
| |
| |
| |
| | |
~JAKE.SMITH/hdf5:bugfix/splitter_valgrind_patch to develop
* commit '6462c67b6578e48c1ef6d847be59c0b5e3598a50':
Patch a few holes in the Splitter VFD implementation.
|
| | |
| |
| |
| |
| | |
* Missing logfile close on driver-open failure.
* Initialize empty string in test/vfd (logfile path in W/O compat check).
|
| |\ \
| | |
| | |
| | |
| | | |
* commit '0ef32f07fb9e8fb6063f3318425506047454d6f4':
Remember the info for the last ID looked up for a given ID type.
|
| | | | |
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
* commit 'a8a4e9f27b67ae2e22970e42859225adcc2e5cbb':
Eliminate allocating file & memory offset & length arrays when performing I/O on a single element.
|
| | |/ /
| | |
| | |
| | | |
I/O on a single element.
|
| |/ /
| |
| |
| | |
functions. The metadata cache tagging has already been done by routines further up the call stack.
|
| |\ \
| | |
| | |
| | |
| | |
| | |
| | | |
to develop
* commit '87695c999ad7ea348ee6dc03b46b0bd345f7d7df':
Minor normalizations with HDF5 1.10.
|
| | | | |
|
| |/ /
| |
| |
| |
| |
| | |
both selections, but with different selection types (i.e. one selection defined
as an 'all' type and the other as a hyperslab or point type), without falling
into the generic selection iteration case.
|
| | | |
|
| | | |
|
| | | |
|
| |/ |
|
| |
|
|
| |
checking.
|
| |
|
|
| |
in C11 (gets() is not used in our repo).
|
| |
|
|
| |
the dataset is extended.
|
| |\
| |
| |
| |
| |
| |
| | |
to develop
* commit 'c3367e6634d4dee88ff855da08e312f6685c23af':
Moved -Woverlength-strings to the developer flags.
|
| | | |
|
| |/
|
|
| |
and code [-Werror=declaration-after-statement]`.
|
| |\
| |
| |
| |
| |
| |
| |
| |
| | |
* commit '43424a1392b662a29542bb70014c253162ccfe48':
Add missing ')'.
Add C++ warnings treated as error for autotools builds.
Move macro ADD_H5_CFLAGS to cmake_ext_mod/HDFMacros.cmake and remove duplicate versions.
Address PR suggestions and add overlooked GCC compiler version flags.
Don't add general warnings flags for unsupported old versions of gcc and g++ (older than gcc/g++ 4.2). Correct gnu-cxxflags to determine warnings flags to be added based on C++ compiler version instead of C compiler version.
|
| | | |
|
| |/ |
|
| | |
|
| |
|
|
|
|
| |
* Updated info struct parameter to correct info_string
* Fixed Makefile.am where the S3 VFD was listed twice, causing
duplicated symbols errors.
|
| |\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
~JAKE.SMITH/hdf5:feature/vfd_splitter_mirror_a to develop
Add Splitter VFD and Mirror VFD.
* commit '664fc6af47e369152727ff66d68d8532feb0e210':
Add enable-mirror-vfd flag to configure options.
Tidying of Mirror VFD.
Add function header comment for `mirror_writer:run_writer()`.
Add Splitter VFD to library.
|
| | |\
| | |
| | |
| | | |
https://bitbucket.hdfgroup.org/scm/~jake.smith/hdf5 into feature/vfd_splitter_mirror_a
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
* Rename server-stop utility to mirror_server_stop.
* Remove external dependency on bzero().
* Modify test/use_common to use only the public API.
* Rename internal bitswap macro to follow convention.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
* "Simultaneous and equivalent" Read-Write and Write-Only channels for
file I/O.
* Only supports drivers with the H5FD_FEAT_DEFAULT_VFD_COMPATIBLE flag for
now, preventing issues with multi-file drivers.
Add Mirror VFD to library.
* Write-only operations over a network.
* Uses TCP/IP sockets.
* Server and auxiliary server-shutdown programs provided in a new directory,
`utils/mirror_vfd`.
* Automated testing via loopback ("remote" of localhost).
|
| |\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
to develop
* commit '35c0d5cdfcfaa84f59e1c596ba1ccaeb28e3d83d':
Fix for passthrough VOL not passing tools tests due to incorrect optional callback queries.
|
| | | |/
| |/|
| | |
| | | |
optional callback queries.
|
| |\ \ \
| |/ /
|/| |
| | |
| | |
| | |
| | |
| | | |
~VCHOI/my_third_fork:bugfix/dtype_close_on_error to develop
* commit 'db9155c2f34bbf77a1cda01904805fe5c993b6d5':
Fix according to PR feedback.
Fix an error in previous merge: should use NULL instead of FAIL.
|
| | | | |
|
| | | | |
|
| | | | |
|
| |\ \ \
| |/ /
| | |
| | |
| | |
| | |
| | | |
* commit '4830a1796441abbb5a4fbd2cff9a651f2a0d066e':
Updated tools dump output when dataset offset is undefined.
Added checks for native optional call support in some of the tools.
Misc changes for h5dump VOL changes.
|
| | | | |
|
| | |\ \ |
|
| | | | | |
|
| | |/ /
|/| | |
|
| |\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
~VCHOI/my_third_fork:bugfix/dtype_close_on_error to develop
* commit 'afdcac28b85d690eebc80ab568fa5266081baaaa':
A fix in the cleaning up code for datatype when datatype initialization via H5D__init_type() fails. This is triggered by the tests for revised references when the libver bounds setting does not allow version 4 datatype message to be created. The test failure is abort core dumped. This is due to the datatype initialization fails before the datatype ID is registered. The datatype cleanup code should provide for the above situation. The code to fix the problem is the same as what is done in H5D__open_oid().
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
H5D__init_type() fails.
This is triggered by the tests for revised references when the libver bounds setting does not allow version
4 datatype message to be created. The test failure is abort core dumped.
This is due to the datatype initialization fails before the datatype ID is registered.
The datatype cleanup code should provide for the above situation.
The code to fix the problem is the same as what is done in H5D__open_oid().
|
| | | | |
| | | |
| | | |
| | | | |
H5I_INVALID_HID.
|
| |\ \ \ \
| |_|/ /
|/| | |
| | | |
| | | |
| | | | |
* commit '63c95faf49559ea66e3066427961095b69fdb213':
Remove tongue-in-cheek credit for Rusty Shackleford and Dale Alvin Gribble.
Follow HDF5 conventions.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Delete the comment questioning whether pthread_mutex_lock is allowed
in a key destructor, since pthread_key_create(3) provides the answer:
There is no notion of a destructor-safe function. If an application
does not call pthread_exit() from a signal handler, or if it blocks any
signal whose handler may call pthread_exit() while calling async-unsafe
functions, all functions may be safely called from destructors.
Delete redundant comment.
|