164ee92f22
Changes to OTF: - general: - updated copyright information (2011->2012) - otfmerge-mpi: - use the MPI-2 versions of MPI_Address and MPI_Type_struct - otfdump: - don't abort when reading events fails - the input tracefile might only have statistics Changes to VT: - general: - updated version number to 5.12.2openmpi - updated copyright information (2011->2012) - configure: - added configure switches to enable/disable CUPTI and CUDA wrapping - fixed detection of C++ runtime libraries for Cray and PGI v11.x compilers - fixed detection of Cray compiler's OpenMP flag - fixed detection of MPI_IN_PLACE - disable support for RTLD_DEFAULT on CrayX? platforms; it's provided by dlfcn.h but not working - added '-force_flat_namespace' to linker flags of compiler wrappers on MacOS (causes that OpenMPI's libmpi_f77 calls the VT MPI wrapper functions - not the original ones) - default configure options on Cray platforms: use compiler option '--target=$XTPE_COMPILE_TARGET' only if the environment variable is set - VT libs: - added support for CUDA tracing via CUPTI callbacks and activities (runtime and driver API, kernels, memory copies, GPU idle time and GPU memory usage) - added support for cudaMemcpyDefault and synchronous peer-to-peer memory copies in CUDA library wrapper - fixed a bug in CUDA runtime wrapper initialization and thread creation - fixed a build bug occurred if CUDA and CUPTI found, but support for library tracing is disabled - use stack-allocated char-array when composing vtunify command; on some platforms system() results in exit code 127 when using a dynamically allocated char-array - fixed bug in async. counter plugin - fixed handling of empty MPI groups (MPI_GROUP_EMPTY) - fixed handling of MPI groups implicitly generated by MPI_Win_create - fixed conversion from MPI_Fint-arrays to MPI_Aint-arrays in Fortran MPI wrappers - fixed order of OpenMP threads based on its id (omp_get_thread_num) - fixed parsing of filter file to consider non-rank-specific filter rules appearing after a rank selection for disabling - fixed handling of 'errno' in LIBC[-I/O] wrappers for statically linked applications (set application's errno to the errno defined in the external LIBC which is used for calling the real functions) - suppress warnings about usage of deprecated MPI functions (OMPI_WANT_MPI_INTERFACE_WARNING=0) - vtunify[-mpi]: - fixed potential memory corruption during enqueuing recv. messages for p2p message matching - vtunify-mpi: - use the MPI-2 versions of MPI_Address and MPI_Type_struct - removed unused MPI wrappers - fixed assertion in p2p message matching which occurred when processing local traces with disabled ranks - vtdyn: - load user-specified shared libraries (-s SHLIB) into the mutatee before starting the instrumentation; adds support for instrumenting shared libraries which are loaded during runtime - compiler wrappers: - fixed detection of MPI library linked in the path form (e.g. libmpi.a instead of -lmpi) - fixed corrupt library order when using vtnvcc for linking MPI/CUDA mixed program - OPARI: - fixed Fortran parsing for detecting end of block DO loops This commit was SVN r26114. |
||
---|---|---|
.. | ||
libompitrace | ||
vt | ||
README.txt |
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).