| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Feature
Description:
Most tests are done inside a for-loop. Whenever a test exits
with error, the for-loop does a "exit 1" to exit the make.
"make -i" could not catch and ignore the error status.
Solution:
Replaced "exit 1" with break. At the end of the for-loop,
test if all tests have been run. If not, the for-loop is
ended by the break command, thus raise an error. Now,
'make -i' can catch and ignor it.
Also added the test of variable HDF5_Make_Ignore inside the
for-loop to indicate the desire to ignore errors when the
HDF5_Make_Ignore is set to a non-null/blank string.
Platforms:
Tested on modi4 and eirene.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I introduced a small bug when trying to fix the zlib stuff.
Description:
-lz wouldn't be specified with the compile flags if it was found
while checking for the HDF4 library.
Solution:
Removed my bad check and replaced with a better one.
Platforms:
Linux, Solaris
|
|
|
|
| |
Mention the hypeslab speedups
|
|
|
|
| |
Added Stream VFD modules to the MANIFEST
|
|
|
|
|
|
|
|
| |
Stupid error in one of the tests.
Description:
The string tested needed to be in quotes.
Platforms:
Linux, Solaris
|
|
|
|
|
|
|
| |
Regenerated after changes to the configure.in file made by Thomas
Radke <tradke@aei-potsdam.mpg.de>
Platforms:
Linux
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Added the Stream Virtual File Driver to the list of drivers
used for trying to open a file via h5dump_fopen().
Description:
The Stream VFD was added at bottom of the driver list for h5dump_fopen().
If no driver succeeded to open a file given by its filename
the Stream VFD would try to do so by parsing the filename as an
'hostname:port' argument, open a socket to that address and read
read the file.
This feature can be used to h5ls/h5dump streamed files.
Platforms:
All platforms (also between heterogenous).
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Added test program to verify the Stream Virtual File Driver.
Description:
This program tests the functionality of the Stream Virtual File Driver.
1. It spawns two new processes, a sender and a receiver.
2. The sender opens an HDF5 file for writing and writes
a sample dataset to it.
On closing the file the Stream VFD would send the file
contents to any connected client.
3. The receiver serves as a client attempting to open an
HDF5 file for reading. On opening the file the Stream VFD
would establish a socket connection to the sender process,
identified by its hostname (which is localhost in this example)
and a port number, and read the file contents via this socket.
Aftwerwards the dataset is read from the file into memory
and verified.
4. The main program waits for termination of its two child
processes and returns their exit code.
Platforms:
Tested so far under Linux, Irix 32/64bit, OSF1, Solaris, Cray Unicos,
Hitachi SR8000, IBM AIX.
Not tested under Windows yet.
|
|
|
|
|
|
|
| |
Add the Stream VFD test program to the 'make check' targets.
Description:
Added stream_test to the TEST_PROGS variable and a rule to build it.
|
|
|
|
|
|
|
| |
Include the Stream VFD's header file H5FDstream.h.
Description:
All the VFD's header files are included by hdf5.h itself for convenience.
|
|
|
|
|
|
|
|
| |
Add the Stream VFD sources to the appropriate makefile variables.
Description:
Added H5FDstream.c to the LIB_SRC variable and H5FDstream.h
to the PUB_HDR variable for building the Stream VFD.
|
|
|
|
|
|
|
|
|
|
| |
Define HAVE_STREAM.
Description:
If the Stream VFD was configured the configured script
will expand this into
'#define HAVE_STREAM 1' in H5config.h and
'#define H5_STREAM 1' in H5pubconf.h.
|
|
|
|
|
|
|
| |
Added registration of the Stream Virtual File Driver.
Description:
The Stream VFD is registered here if it was configured.
|
|
|
|
|
|
|
|
|
|
|
| |
Added the H5FD_stream_fapl_t type to the TypeString mapping table.
Description:
This servers for proper substitution of the H5TRACE macros in the
Stream VFD sources.
Platforms:
All platforms.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Added source files for the Stream Virtual File Driver.
Description:
The Stream VFD allows users to stream complete HDF5 files
via socket connections between different applications.
Files which were created anew are flushed to any connected client
on each H5Fflush() or H5Fclose() operation.
Files which are opened as read-only will be read from a socket
on a H5Fopen() call.
The driver's H5FDset_fapl_stream() routine allows to pass in
several parameters such as an external socket descriptor,
some socket options, and flags for broadcasting a received file.
If an external socket is provided the Stream VFD would use that
for the socket calls. Otherwise it parses the filename argument
in H5Fcreate()/H5Fopen() for a 'hostname::port' parameter.
All files processed by the Stream VFD are kept in memory
(same way as the core VFD does).
Platforms:
Tested so far under Linux, Irix 32/64bit, OSF1, Solaris, Cray Unicos,
Hitachi SR8000, IBM AIX.
Not tested under Windows yet.
|
|
|
|
|
|
|
|
|
|
| |
Add the socket library to make's LIBS variable.
Description:
The socket library is needed to build HDF5 with the Stream VFD.
Platforms:
Solaris
|
|
|
|
|
|
|
|
|
|
|
|
| |
Added new option --with-Stream-VFD.
Description:
The configure option --with-Stream-VFD[={yes}|{no}] is used
to configure HDF5 to build the Stream Virtual File Driver.
The default is not to build it.
Platforms:
all platforms
|
|
|
|
|
|
|
|
|
|
| |
Upgrade of GNU tools.
Description:
Upgraded the aclocal.m4 to the newest version of libtool.m4.
Platforms:
Linux.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Fix last couple of errors from introducing "regular" hyperslab feature
into the library.
Description:
Code was blindly dereferencing data structures which aren't defined when
operating on regular hyperslabs.
Solution:
Check for regular hyperslab defined and retrieve information from regular
hyperslab info instead of mucking about in other hyperslab information.
Platforms:
Solaris 2.6
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Cleaned up the configure file a bit.
Description:
There were a few small bugs having to do with checking if strings
were empty. Also needed to force paths to be absolute instead of
relative.
Solution:
I standardized string checking (test -z for an empty string and
test -n for a non-empty string). Also, if the user specifies a
relative path for any of the options, the configure now makes it
into an absolute path for both CPPFLAGS and LDFLAGS macros.
Platforms:
Solaris, Linux
|
|
|
|
| |
command line arguments are given).
|
|
|
|
|
|
|
| |
declaration.
Przemek Klosowski, Ph.D. <przemek@nist.gov> reported this problem on
Linux RH 6.1 systems.
|
|
|
|
|
|
| |
instead of 36 1x1
hyperslabs.
|
|
|
|
|
|
| |
tests are
passing, but not all of them yet...
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
On my benchmarks,
they are about 4-5 times faster than before. We no longer generate "general"
hyperslab data structures for regular hyperslabs, the general data structures
are only generated when needed for irregular hyperslabs.
Still fixing a couple of nook-and-cranny functions to understand the new
information for the regular hyperslabs, so the tests aren't completely passing,
but I wanted to get this checked in for Elena's benchmarks. I should have
more/all tests passing later today.
|
| |
|
|
|
|
|
|
| |
care of much
more nicely in the config/commence file...
|
|
|
|
|
|
|
|
| |
created
in the configure script, basically replacing all -L/<path> constructs
with -R/<path> ones so that libtools will pass it along to the compiler
correctly.
|
|
|
|
|
|
|
|
| |
add the
equivalent -R/<path> to the LT_LINK_EXE command. Therefore, any
executables created will know where we got the different libraries from
automagically.
|
|
|
|
|
|
| |
problem with
FILENAME being extern global...
|
|
|
|
| |
h5test.o, which requires the definition to work...
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The "FILENAME" declared extern in h5test.h is not always used.
It was used in h5_cleanup to remove temporary files created
during tests. Not all tests codes have used this routine.
Indeed, quite a few of test programs do "#define FILENAME ".
Also, h5_cleanup needs to work in tandem with h5_fixname.
h5_fixname accepts an explicite base_name argument instead
of using the global variable FILENAME. That is cleaner.
Solution:
Added char *base_name[] as a new argument to h5_cleanup, in
the same style as h5_fixname. Removed "extern char *FILENAME..."
from use. Also, undo some unnecessary declaration of "char *FILENAME"
from some tests which don't use it at all (yet).
Platforms tested:
modi4-64(irix64), arabica(solari2.7), eirene(linux)
(arabica could not launch tests automatically. I had to hack
in LD_LIBRARY_PATH to make them run.)
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
with
zlib, and zlib isn't in our LD_LIBRARY_PATH or in a standard system
library place (/usr/lib or /lib), then the tests can't run. This fixes it
if the person configures the source with the flag:
--with-zlib=/usr/fnord/include,/usr/fnord/lib
This only works if you're pointing to the shared library version in the
above flag...
|
|
|
|
|
|
|
| |
libh5test, but
libh5test wants FILENAME to be defined. I have no clue why this was
working before...
|
| |
|
|
|
|
|
|
| |
static.
Also I'm keeping the place the user indicated the zlib would be...
|
|
|
|
|
| |
RM_H5Z.html
Corrected compression cross-reference.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
__cplusplus
macro didn't work on all systems. This fixes it.
This also introduces the ability to configure for fortran and c++. This
is not to be implemented yet, though!
|
| |
|
| |
|
| |
|
|
|
|
| |
autoheader, it was useless to add them in here...
|
|
|
|
|
|
|
| |
src/H5{pub}config.h
files. I append to them an #undef of the inline macro. Then, if it's a
C++ compiler, the inline keyword isn't redefined incorrectly...
|
|
|
|
|
|
| |
in C++
and, when adding the header to a C++ program, breaks it.
|
| |
|
|
|
|
|
|
| |
and dynamicly
allocated memory.
|
|
|
|
|
|
|
|
| |
variable instead of
multi-dereferenced pointer chains. This buys us another ~20% improvement in
the hyperslab I/O speed. (From ~30 seconds to ~25 seconds on the h5hypers
benchmark)
|