report

Generate a report from result data collected during a previous analysis.

Syntax

-report <value>

-R <value>

Note

Both short names and long names are case-sensitive. For example, -R is the short name of the report action, and -r is the short name of the result-dir action-option.

Arguments

summary

Brief statement of the total number of new problems found and a breakdown by problem type. After each collect or collect-with action, a Summary report is generated by default, written to a text file in the current working directory, and sent to stdout.

problems

Detailed report of detected problem sets in the result, including their location in the source code.

observations

Detailed report of all code locations used to form new problem sets.

status

Brief statement of the total number of detected problems, the number that are Not investigated, and the breakdown by category.

Default

By default, a Summary report is automatically generated after running a collect or collect-with action, and then sent to stdout and to a file named inspxe.xml.

Description

Use the report action to generate the specified type of report from an analysis result.

By default, a report is written to standard output in text format, but the inspxe-cl tool provides a number of options you can use when generating a report.

  • To save a report to a file, use the report-output option.

  • Use the format option to choose a report format: Text, CSV, or XML. If you choose the CSV format and want to use a delimiter other than the default comma, use the csv-delimiter option to specify the delimiter.

  • To sort and filter report content, use the sort-asc, sort-desc and filter options.

Example

Generate a problems report of all detected problems in the specified result r001ti and display it to stdout.

$ inspxe-cl -report problems -result-dir r001ti

Generate a status report for the most recent result and save it as myThreadingStatus.txt text format in the current working directory.

$ inspxe-cl -R status -report-output myThreadingStatus.txt

Status report output:

181 problem(s) found
15 Investigated
166 Not investigated
Breakdown by state:
13 Confirmed
2 Fixed
166 New

Compare two t1 Detect Deadlocks results and generate a summary report that shows the differences.

$ inspxe-cl -R summary -r myRes000ti -r myRes001t1
For more complete information about compiler optimizations, see our Optimization Notice.