Intel® Inspector User Guide for Linux* OS

User Guide

  • 2020
  • 05/04/2020
  • Public Content
Contents

Typical Suppressions Usage Models Using Handwritten Suppression Files

There are two typical usage models for handling handwritten suppression files in the
Intel Inspector
 . They differ depending on how you want to confirm the effectiveness of the files:
These usage models also apply to editing suppression files already created using the
Intel Inspector
 GUI or command line interface.

Apply the File to an Existing Result

  1. Create the handwritten file using a text editor. Save the handwritten file to the default suppression directory for the project. Use the default
    .sup
     extension.
  2. In the
    Intel Inspector
     GUI, in the
    Target
     tab of the
    Project Properties
     dialog box, set
    Suppressions
     to
    Apply suppressions
     .
  3. Open an existing result for the project (collected using the
    Intel Inspector
     GUI or command line interface).
    Outcome: In the
    Code Locations
     and
    Problems
     panes, the
    Intel Inspector
     marks (strikes through) all result data
    potentially
     impacted by the rules in the handwritten file. (It may take some time for all marks to appear. The marks remain in the result even if you close and then reopen the result.)
  4. Review the marked data to assess the effectiveness and potential reach of the rules in the handwritten file. If necessary, continue editing the handwritten file in the text editor.
  5. Repeat steps 3 and 4 as necessary.
  6. Run a new analysis using the
    Intel Inspector
     GUI or command line interface.
    Outcome: The
    Intel Inspector
     does not collect result data impacted by suppression rules in the handwritten file and the rules in other files and directories identified in the
    Suppressions
     tab of the
    Project Properties
     dialog box.

Apply the File to a New Result

  1. Create the handwritten file using a text editor. Save the handwritten file to the default suppression directory for the project. Use the default
    .sup
     extension.
  2. In the
    Intel Inspector
     GUI, in the
    Target
     tab of the
    Project Properties
     dialog box, set
    Suppressions
     to
    Apply suppressions
     .
  3. Run a new analysis using the
    Intel Inspector
     GUI or command line interface.
    Outcome: The
    Intel Inspector
     does not collect result data impacted by suppression rules in the handwritten file and the rules in other files and directories identified in the
    Suppressions
     tab of the
    Project Properties
     dialog box).
  4. Review the remaining problems in the result to assess the effectiveness and potential reach of the rules in the handwritten file. If necessary, continue editing the handwritten file in the text editor.
  5. Repeat steps 3 and 4 as necessary.

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