HP UX Caliper Software manual Example Adding Instructions to an fprof Report

◦A source-code line number for rows showing statements

◦An instruction slot number for rows showing instructions not on a bundle boundary

◦A source-code column number followed by an offset from the beginning address of a function for rows showing instructions on a bundle boundary

•>Statement Instruction: The column contains either a source statement, preceded by “>”, or a disassembled instruction. Statements that are out of order due to optimization are preceded by “*>”.

16“File not found” error: Here, the application called a routine in libc, but the source code for that library routine is not available. This is a common error and you can usually ignore it.

Example: Adding Instructions to an fprof Report

Notice that, by default, only source statements were shown in the Function Details section. If you would also like to see disassembled instructions, then you can re-report the collected data using the -roption. The -roption takes one of the following qualifiers: statement (report source statements), instruction (report disassembled instructions), or all (report both source and instructions).

HP Caliper saves the latest collected data and uses that by default when generating a report. It does not re-run the application and collect new data.

We will also specify an output file using the -ooption:

$ caliper fprof -o out.txt -r all

In the resulting report output file (out.txt), you will find an fprof report that shows IP sample counts down to the instruction level. “fprof Measurement Report for matmul, with IP Sample Counts for One Function” (p. 25) shows a section of the report that contains IP sample counts for one function.

The numbers (which are bold in the PDF version of this guide) are annotations to explain the report—they are not part of the output you receive. See the list at the end of the report for the explanations.

24 Getting Started with the HP Caliper Command-Line Interface