| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
| |
remove benchpar and mpi-perf tests
add new prunTest.cmake that will be modified for parallel tests
|
| |
|
|
|
|
| |
Tested: cygwin
|
| |
|
| |
|
|
|
|
|
|
| |
Change reference of generated executables in src and fortran/src to use $<TARGETFILE:xxx> format.
Tested: local linux
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Purpose:
Remove H5_MPI_SPECIAL_COLLECTIVE_IO_WORKS and
H5_MPI_COMPLEX_DERIVED_DATATYPE_WORKS #defines from source.
Description:
Two advanced parallel functionalities, special collective IO and
complex derived datatypes, are not supported by older
implementations of mpi, and thus our code limits the use of these
features with #ifdefs and has checks in configure to set them (or
not). Unfortunately, configure can't actually run a parallel check
to see if these features are working (nor not) so it resorts to
looking in the config files where they are explicity enabled or
disabled based on versions of mpi, sytems being built on, or for
no documented reason at all (i.e. just set to on or off as some
'default'). Overriding these settings is easy if need be, provided
it is known that it needs to be done to get improved performance,
and oftentimes it is not.
Most new MPI implementations successfully handle the functionality
requested when these #defines are set, and many of the "turn these
features off" cases in the config files are for old (> 5 years)
versions of MPI and retired systems (such as NCSA's tungsten).
Therefore, the decision has been made to remove the support for
these old versions of MPI and systems that cannot handle these
behaviors. The #ifdefs and supporting setup in the config/ files
and configure script has been removed, and the code executed when
these options were not set removed from the source.
In passing, this commit also cleans up some whitespace issues in
both t_mpi.c and H5Dmpio.c. Furthermore, in t_mpi.c, the special
collective IO test was not getting regularly run due to it being
written to work only with four processes (we regularly test with
six, previously with three), and thus it failed when actually run
due to an out of bounds data buffer assignment. It has been
modified to run at any number of processes greater than four, and
the memory problem has been fixed so the test passes.
Tested:
jam, h5committest, ember
|
| |
|
|
|
|
| |
Tested: windows
|
| |
|
|
|
|
|
|
| |
status of check
Tested: heiwa
|
| |
|
| |
|
|
|
|
| |
Bring r20895 from 1.8
|
| |
|
|
|
|
|
|
| |
corrected test dependencies so that memcheck would process tests in correct order.
Tested: local linux - confirmed with valgrind
|
|
|
|
| |
extension in folder name. Add install configuration commands if ext libs are packaged with project.
|
|
|
|
| |
EXTERNAL_PROJECT for extlibs.
|
| |
|
|
|
|
| |
Add SOVERSION for linux
|
|
|
|
|
|
| |
Change case of tools subtests to not conflict with tools tests.
Tested: windows, local linux
|
|
|
|
|
|
|
|
|
| |
removed option defines and #ifdef/#endif
refactored all printf to HDfprintf in h5dump.c
formatted and indention improvements
synched with 1.8 branch
Tested: local linux
|
|
|
|
|
|
| |
Tested:
NCSA BP AIX system. No need of h5committest because the changes affect AIX
systems only.
|
|
|
|
|
|
| |
Autotools merge to come.
Tested: local Linux
|
| |
|
|
|
|
|
|
| |
products are: HDF Group/Product/Version
Tested: windows , local linux
|
| |
|
|
|
|
| |
ext lib handling to get the correct path. Needs more work to remove the the pre-install copying.
|
|
|
|
|
|
| |
InitOnceExecuteOnce for use by threads.
merge from 1.8 r20568
|
|
|
|
|
|
|
| |
Remove C++ specific flag from C compilation flags, for gcc 4.5 & 4.6
Tested on:
FreebSD/64 8.2 (freedom) w/gcc 4.6
|
|
|
|
| |
lib fails if permission to install location is denied. Does not affect build otherwise.
|
|
|
|
|
|
|
|
| |
Update with new warning flags for gcc 4.6.x
Tested on:
FreeBSD/32 8.2 (loyalty) w/gcc 4.6
FreeBSD/64 8.2 (freedom) w/gcc 4.6
|
|
|
|
|
|
|
|
|
|
| |
Removed code in
configure.in that tried to distinguish different versions of AIX. This is no
longer needed.
Tested:
NCSA Blue-print. No h5committest since this affected AIX system only.
|
|
|
|
|
|
|
|
|
|
|
|
| |
Remove old, uneeded configuration customizations for FreeBSD systems.
(config/freebsd)
Also, convert a large stack variable into a dynamic memory allocation
and clean up a few compiler warnings (tools/h5dump/h5dumpgentest.c)
Tested on:
FreeBSD/32 8.2 (loyalty) w/debug & production
FreeBSD/64 8.2 (freedom) w/debug & production
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
General shared library improvements for CYGWIN / AIX
Description:
Shared libraries are disabled on both CYGWIN and AIX due
to inability to build them correctly. Part of the problem
in both of these situations is the lack of the libtool
flag -no-undefined, which tells libtool that all needed
symbols are defined at link time (a requirement on these
systems) and that it's okay to build shared libraries.
Another problem are lack of dependencies between wrapper
libraries and core C HDF5 library.
This patch addresses both of these by fixing configure to
add in -no-undefined flag for libtool during linking and
adds automake dependencies in the Makefile.am files.
After testing, both CYGWIN and AIX now generate shared
libraries, but there are still some test failures in each.
(cache_api, dt_arith, and testerror.sh on CYGWIN, and
fortran tests on AIX).
Even though the shared libraries are not quite perfect,
this is a general improvement to what we had before, so
I'm applying the patch anyways. Note that default behavior
of shared libraries on these systems being disabled has
NOT been changed and requires the use of the
--enable-unsupported to attempt to build them.
We will need to address the test failures in each
architecture prior to formally supporting shared
libraries on each.
Tested:
h5committested & CYGWIN tested (on bangan)
(AIX tested by Albert on bp-login2)
|
|
|
|
|
|
|
|
| |
HDFFV-5931). Previously, H5_HAVE_GETTIMEOFDAY was never properly defined. The timezone struct and Wgettimeofday() timezone output was also added.
This is a merge of several changesets from the log_vfd branch where this work took place: 20355, 20359, 20411, 20413, 20431, 20460
Tested on: Windows
|
|
|
|
| |
builds of "Debug" builds.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Revise shared Fortran library disabling scenarios in configure
- Improve configure output summary
Description:
Shared Fortran libraries are not supported on Mac, but were being
disabled by configure in a way that also forced the C libraries
to be static-only. This has been fixed, so now only shared Fortran
is disabled while shared C can remain.
This prompted two additional changes:
1. While working on the check that addresses whether or not
shared Fortran libraries are allowed, removed old and no
longer needed check(s) that disable shared Fortran
libraries with HP, Intel 8, PGI, and Absoft compilers.
(Essentially, Mac is the only situation in which Fortran
shared are disabled by configure.)
2. Having two different states of libraries (i.e. shared C
library with static-only Fortran library) was not apparent
in the configure summary, which labeled all libraries as
either shared and/or static. I've added lines to both the
C++ and Fortran output sections to list shared/static-ness
of these libraries specifically.
Additionally, I've made sure that the new --enable-unsupported
configure option correctly overrides configure if it tries to
disable a shared library.
Tested:
jam, fred, & h5committest
|
|
|
|
| |
(VISTA or WIN7)
|
| |
|
|
|
|
| |
Tested: local linux
|
|
|
|
| |
H5_HAVE_GETCONSOLESCREENBUFFERINFO always gets set on windows (this is from the pubconf.h in the windows folder)
|
|
|
|
|
|
| |
h5jam tests, and correct h5jam tests
Tested: local linux
|
|
|
|
| |
Tested: local linux
|
| |
|