Typical Suppressions Usage Models Using Third-party Suppression Files

There are two typical usage models for handling third-party suppression files depending on how you want to confirm the effectiveness of the converted files:

Apply the Converted File to an Existing Result

  1. In the Intel Inspector command line interface, use the convert-suppression-file action to convert an IBM Rational Purify* or Valgrind* suppression file to the Intel Inspector suppression file format. Save the converted 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 converted 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 converted file. If necessary, edit the converted file in a 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 converted file and the rules in other files and directories identified in the Suppressions tab of the Project Properties dialog box.

Apply the Converted File to a New Result

  1. In the Intel Inspector command line interface, use the convert-suppression-file action to convert an IBM Rational Purify* or Valgrind* suppression file to the Intel Inspector suppression file format. Save the converted 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 converted 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 converted file. If necessary, edit the converted file in a text editor.

  5. Repeat steps 3 and 4 as necessary.

See Also


Supplemental documentation specific to a particular Intel Studio may be available at <install-dir>/<studio>/documentation/.

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