Before you Begin Analyzing

Binary program

Launching and analyzing the application's performance, and displaying disassembly code.

More on binary programs:

The binary program is an executable file. To analyze the performance of your program using sampling, or call graph, you need to specify the executable file that you want to analyze, or the executable file that launches other modules you want to analyze.

Symbol information

Instrumentation in call graph, display of symbol names in hotspot, source, and assembly views.

Line number information

Source code display.

More on line number and symbol information:

Line number and symbol information, also referred to as debug information, is generated by your compiler and provided either in a separate file or as part of the binary file.

The VTune analyzer requires the line number and symbol information for various features:

• Call graph. This information is essential for instrumenting the program and generating the call graph information.

• Static module analysis and sampling. This information is used to include symbol names in the function and hotspot views.

• Source view. This information is used to locate and display source code.

See About Symbol and Line Number Information for more details.

Source file

Source code display. In order to see source code, the source files must be available in your system.

Compilation information

Intel(R) Tuning Assistant, source code advice.

More on compilation information:

The Intel Tuning Assistant uses compilation information to display tuning advice for your C, C++, and Java* source code. You need to provide this information in one of these formats:

• C++ project file (.dsp).

• Makefile (makefile or .mak) and the make utility used to build the executable.

• Preprocessor (.i) file or source file with compile options.