Overview of the Summary Window, After Running the Survey Tool

After you run the Survey tool, the Survey Report window displays your program target's profiling information. To obtain a dashboard-like summary of your application's top five loops that use the most CPU time, view the Summary window by clicking the Summary button.

Summary report window, after running the Survey tool analysis

A count of the source files found and any annotations detected appears above Top time-consuming loops. This can indicate whether the right source files are found, as defined by the project properties. If your source files already contain annotations (added during a later workflow step), the count of annotations detected appears.

The information under Top time-consuming loops provides a high-level summary of the collected Survey tool data. The Loops listed are the Hot Loops listed in the Survey Report that you should consider for parallelism. Typically, you should include the call to a hot loop as well as the function itself within a parallel site.

To access more profiling details, click one of the links in the Loop column to view the Survey Report window.

After you run the Suitability and Correctness tool, the displayed heading changes and the content includes high-level information collected by other Intel Advisor tools.

The lower part of the window contains collection details for each tool, and platform information (not shown) about the hardware and software environment. Links under Collection Details allow you to display the Application Output, Collection Log output, and Command Line windows for the selected tool. Before you can click the link to view Application Output, select the appropriate Intel Advisor option (see the help topic Choosing Application Output).

After you run the Suitability and Correctness tools, the Summary window displays additional data, including a summary of the collected Suitability and Correctness data with links to their reports below Potential Program Gain.

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