User Guide

Contents

Collecting Trace Files without fgtrun Script

You can choose to collect traces without the
fgtrun
script if you do not want to launch your application from a Visual Studio* command prompt or Linux* terminal. In this case, follow the steps below to collect and convert trace files manually.
These steps do not outline steps required to capture symbol resolution information.
  1. Set paths to the collector libraries.
    Set up or update the environment variables shown below. For Windows* systems, specify also the proper version of the Microsoft Visual Studio* compiler (
    vc12
    ,
    vc14
    , or
    vc14.1
    ).
    Operating System
    Environment Variable
    Default Value
    Description
    Windows*
    INTEL_LIBITTNOTIFY32
    ..\fgt\windows\bin\ia32\<vc version>\fgt.dll
    32-bit collector library
    INTEL_LIBITTNOTIFY64
    ..\fgt\windows\bin\intel64\<vc version>\fgt.dll
    64-bit collector library
    INTEL_ITTNOTIFY_GROUPS
    all;
    Trace events from all groups
    Linux*
    INTEL_LIBITTNOTIFY32
    ../fgt/linux/lib/ia32/cc4.8_libc2.19_kernel3.13.0/libfgt.so
    32-bit collector library
    INTEL_LIBITTNOTIFY64
    ../fgt/linux/lib/intel64/cc4.8_libc2.19_kernel3.13.0/libfgt.so
    64-bit collector library
    INTEL_ITTNOTIFY_GROUPS
    all;
    Trace events from all groups
    macOS*
    INTEL_LIBITTNOTIFY32
    ../fgt/macos/lib/ia32/osx10.12.6_kernel16.7.0/libfgt.dylib
    32-bit collector library
    INTEL_LIBITTNOTIFY64
    ../fgt/macos/lib/intel64/osx10.12.6_kernel16.7.0/libfgt.dylib
    64-bit collector library
    INTEL_ITTNOTIFY_GROUPS
    all;
    Trace events from all groups
    If you want the Microsoft Visual Studio* IDE to use the environment variables set in a Microsoft Visual Studio command prompt, you can launch the Visual Studio* IDE from the command prompt using the following command:
    
    
        
    devenv /useenv
  2. Run the application.
    If your paths are set up correctly, the application generates one or more files that start with
    _fgt
    . There is one file per thread that participates in executing the parallelism in the application. So, for example, if two threads participate in the execution of the flow graph, your run generates two files:
    _fgt.0
    and
    _fgt.1
    , with an autogenerated folder in the format
    _fga_YYYYMMDD_HHMMSS
    according to its creation (for example,
    20191111_1111
    ).
  3. Convert the trace files to GraphML* and TraceML* format.
    Convert the
    _fgt
    binary files to the XML format understood by the Flow Graph Analyzer tool using the
    fgt2xml.exe
    converter in the directory containing the folder with the trace files:
    
    
        
    fgt2xml.exe <desired_name>
    This converter scans the current directory for all
    _fgt
    files within the most recent folder according to its name and generates two output files:
    desired_name.graphml
    and
    desired_name.traceml
    .

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 reserverd 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