• 2019 Update 3
  • 03/07/2019
  • Public Content
  • Download as PDF
Contents

A structured tracefile consists of a number of files, which can be interpreted as one conceptual data set. See the approximate structure in the figure below. Depending on the organization of actual files, the following component files will be written:
  • Index file
    <trace>
    .stf
  • Record declaration file
    <trace>
    .stf.dcl
  • Statistics file
    <trace>
    .stf.sts
  • Message file
    <trace>
    .stf.msg
  • Collective operation file
    <trace>.stf.cop
  • Process file(s)
    <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 extension
    .anc
<trace>
is the tracefile name, which is determined automatically or set in the
LOGFILE-NAME
configuration option.
STF Components
Additionally, five data files may 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 are not 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 User and Reference Guide
.
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

Product and Performance Information

1

Intel's compilers may or may not optimize to the same degree for non-Intel microprocessors for optimizations that are not unique to Intel microprocessors. These optimizations include SSE2, SSE3, and SSSE3 instruction sets and other optimizations. Intel does not guarantee the availability, functionality, or effectiveness of any optimization on microprocessors not manufactured by Intel. Microprocessor-dependent optimizations in this product are intended for use with Intel microprocessors. Certain optimizations not specific to Intel microarchitecture are reserved for Intel microprocessors. Please refer to the applicable product User and Reference Guides for more information regarding the specific instruction sets covered by this notice.

Notice revision #20110804