Source files without calls to the Intel® Trace Collector API can be compiled with the usual methods and without any special precautions.
Source files containing calls to the Intel® Trace Collector API need to include the appropriate header files: VT.h for C and C++ and VT.inc for Fortran.
Use this option to disable the usage of debugging information for building the function names in the trace file. By default debugging information finds the source file of each function and groups those functions together in the same class.
Which errors are checked for at runtime is configurable: all errors have a unique name and are categorized in a hierarchy similar to functions. For example, LOCAL:MEMORY:OVERLAP is a local check which ensures that memory is not used twice in concurrent MPI operations. The CHECK configuration option matches against these full names of each supported error and turns it on or off, like this:
When the program terminates Intel® Trace Collector prints a list of all unfreed MPI requests together with their status. Unfreed requests are usually currently active and application should have checked their status before terminating. Persistent requests can also be passive and need to be freed explicitly with MPI_Request_free().
This timer is provided by the MPI implementation. In general this is simply a wrapper around gettimeofday() and then using it instead of gettimeofday() only has disadvantages: with gettimeofday() Intel® Trace Collector knows that processes running on the same node share the same clock and thus does not synchronize between them.
As a new option in Intel® Trace Collector, the trace data can be saved in the single-file STF format. This format is selected by specifying the LOGFILE-FORMAT STFSINGLE configuration directive, and it causes all the component files of an STF trace to be combined into one file with the extension .single.stf. The logical structure is preserved. The drawback of the single-file STF format is that no I/O parallelism can be exploited when writing the tracefile.
Prints the Message Checker reports of the input file to stdout.
The following routines take a state handle defined with either the new or old interface. Handles defined with the old interface incur a higher overhead in these functions, because they need to be mapped to the real internal handles. Therefore it is better to use the new interface, so that support for the old interface may eventually be removed.