STF Components

A structured tracefile actually consists of a number of files, which can be interpreted as one conceptual data set. See the approximate structure in the Figure 7.1. Depending on the organization of actual files, the following component files will be written, with <trace> being the tracefile name that can be automatically determined or set by the LOGFILE-NAME directive:

  • one index file with the name <trace>.stf

  • one record declaration file with the name <trace>.stf.dcl

  • one statistics file with the name <trace>.stf.sts

  • one message file with the name <trace>.stf.msg

  • one collective operation file with the name <trace>.stf.cop

  • one or more process files with the name <trace>.stf.*.<index> (where * is one of the symbols, f, i, s, c, r, or x)

  • for the above three kinds of files, one anchor file each with the added extension .anc

Additionally, five data files might be created for the given trace. These files are Summary Data files. They have common name <trace>.stf.sum.<suffix> (where suffix is one of fnc, cop, msg, cnt, or rep) and formally aren't a part of the trace. You can use these files as additional input for Intel® Trace Analyzer. For details of Summary Data usage, see Intel® Trace Analyzer Reference Manual.

The records for routine entry/exit and counters are contained in the process files. The anchor files are used by Intel® Trace Analyzer to fast-forward within the record files; they can be deleted, but that may result in slower operation of Intel® Trace Analyzer.

Make sure that you use different names for traces from different runs; otherwise you will experience difficulties in identifying which process files belong to an index file, and which ones are left over from a previous run. To catch all component files, use the stftool with the --remove option to delete a STF file, or put the files into single-file STF format for transmission or archival with the stftool -convert option.

The number of actual process files will depend on the setting of the STF-USE-HW-STRUCTURE and STF-PROCS-PER-FILE configuration options described below.

See Also

--sumdata
Structured Trace File Manipulation

For more complete information about compiler optimizations, see our Optimization Notice.