79a065290c
- general: - incremented version number to 1.11.2openmpi - lib OTFAUX: - speed-up messages matching, if no snapshots should be generated Changes to VT: - general: - incremented version number to 5.13.1openmpi - compiler wrappers: - vtnvcc: - add path to cuda.h to the PDT parser command - exclude *.cu source files from instrumenting with PDT/TAU; the PDT parser is not (yet) able to handle CUDA statements and kernels - vtunify: - fixed timestamp boundary check for merging asynchronous plugin counters (i.e. async. timestamp must >= process' start timestamp) - fixed timestamp conversion from local to global - print percentage of message matching bumps (unmatched or reversed messages) - inlined key-value list "record handler" - minor optimizations in hook for merging async. events: - search async. source manager only once per stream - don't call writeRecHook_Event() if no async. source key is defined This commit was SVN r26925. |
||
|---|---|---|
| .. | ||
| 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).