45dfa0d0b1
- added CUDA stream reuse for both, CUDA tracing with CUPTI and CUDART wrapper - removed CUDA stream number from thread name, when CUDA stream reuse is enabled - disable tracking of MPI communicators, requests, windows, etc. if MPI is initialized with MPI_THREAD_SERIALIZED or MPI_THREAD_MULTIPLE (only MPI function enter/leave events will be recorded) - configure: - fixed detection of compiler instrumentation type on Cray platforms using the cc compiler wrapper - compiler wrappers: - fixed preprocessing source files to be parsed by OPARI (add path to empty omp.h to the preprocessor flags to avoid multiple declarations of OpenMP functions, types, etc.) - vtnvcc: Remove 'compinst' instrumentation type, if VT is configured with a non-GNU compiler instrumentation support (Fixed "unrecognized option" error) - vtdyn: - added support for instrumenting outer- and inner loops and its iterations (outer=loops within a function, inner=loops within outer loops) - try to get the full prototype of functions to be instrumented - consider default filter rules also if no filter file is given - fixed potential segfault if adding a filter rule w/o stack bounds - print verbose messages on stdout if vtdyn is started from the Dyninst attach library (libvt-dynatt) - vtunify: - print verbose messages on stderr if vtunify is started automatically from the VT library This commit was SVN r26836.
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).