blob: 6e3cd7542ba410d97520a0135e40aa6895f94db9 [file] [log] [blame]
Chris Lattnere66e73a2003-11-02 02:10:54 +00001<html>
2<title>LLVM: llvm-prof tool</title>
3
4<body bgcolor=white>
5
6<center><h1>LLVM: <tt>llvm-prof</tt> tool</h1></center>
7<HR>
8
9<h3>NAME</h3>
10<tt>llvm-prof</tt>
11
12<h3>SYNOPSIS</h3>
13<tt>llvm-prof [options] [bytecode file] [LLVM passes]</tt>
14
15<h3>DESCRIPTION</h3>
16
17The <tt>llvm-prof</tt> tool reads in an '<tt>llvmprof.out</tt>' file, a bytecode
18file for the program, and produces a human readable report, suitable for
19determining where the program hotspots are.<p>
20
Chris Lattnerf22d8432003-11-02 05:20:44 +000021This program is often used in conjunction with the <tt>utils/profile.sh</tt>
22script. This script automatically instruments a program, runs it with the JIT,
23then runs <tt>llvm-prof</tt> to format a report. To get more information about
24<tt>utils/profile.sh</tt>, execute it with the <tt>--help</tt> option.<p>
Chris Lattnere66e73a2003-11-02 02:10:54 +000025
26<h3>OPTIONS</h3>
27
28<ul>
29 <li><tt>-annotated-llvm</tt> or <tt>-A</tt><br>
30
31 In addition to the normal report printed, print out the code for the
32 program, annotated we execution frequency information. This can be
33 particularly useful when trying to visualize how frequently basic blocks
34 are executed. This is most useful with basic block profiling
35 information or better.<p>
36</ul>
37
38<h3>EXIT STATUS</h3>
39
40<tt>llvm-prof</tt> returns 1 if it cannot load the bytecode file or the profile
41information, otherwise it exits with zero.
42
43<HR>
44Maintained by the <a href="http://llvm.cs.uiuc.edu">LLVM Team</a>.
45</body>
46</html>