9a0432632a
- general: - incremented version number to 5.14.4 - fixed Coverity CIDs: 72002, 72099, 72273, 710580, 710664, 710665, 710666 - VT libs: - fixed "incompatible declaration" errors when building against an MPI-3 implementation Since MPI-3 the C keyword "const" is added to all relevant MPI API parameters (e.g. MPI_Send(void* sendbuf, ...) -> MPI_Send(const void* sendbuf, ...)). Prepending the macro CONST to these parameters which is defined either to "const" (if MPI-3) or to nothing (if MPI-1/2). - fixed potential buffer overflow when reading the filter file - CUDA tracing: - enabled access to CUPTI counters for CUDA tracing via CUPTI - enabled GPU memory usage tracing independent of the CUDA API - enabled recording of CUDA synchronization and implicit synchronization in blocking CUDA memory copies for CUDA tracing via CUPTI - enabled recording of synchronous peer-to-peer CUDA memory copies for CUDA tracing via CUPTI - consider CUDA data transfers as not idle for option 'pure_idle' - fixed identification of the CUDA device ID for CUDA tracing via CUPTI - fixed region filtering for applications using the CUDA runtime API wrapper - compiler wrappers: add path to mpi.h to the PDT parser command and preprocessor flags This commit was SVN r28494.
This is the OMPI contrib system. It is (far) less functional and flexible than the OMPI MCA framework/component system. Each contrib package must have a configure.m4. It may optionally also have an autogen.subdirs file. If it has a configure.m4 file, it must specify its own relevant files to AC_CONFIG_FILES to create during AC_OUTPUT -- just like MCA components (at a minimum, usually its own Makefile). The configure.m4 file will be slurped up into the main configure script, just like other MCA components. Note that there is currently no "no configure" option for contrib packages -- you *must* have a configure.m4 (even if all it does it call $1). Feel free to fix this situation if you want -- it probably won't not be too difficult to extend autogen.pl to support this scenario, similar to how it is done for MCA components. :-) If it has an autogen.subdirs file, then it needs to be a subdirectory that is autogen-able (see the vt project for an example).