2 .\" Man page generated from reStructuredText.
4 .TH "OPT" "1" "2015-05-30" "3.7" "LLVM"
8 .nr rst2man-indent-level 0
12 level \\n[rst2man-indent-level]
13 level margin: \\n[rst2man-indent\\n[rst2man-indent-level]]
20 .\" .rstReportMargin pre:
22 . nr rst2man-indent\\n[rst2man-indent-level] \\n[an-margin]
23 . nr rst2man-indent-level +1
24 .\" .rstReportMargin post:
28 .\" indent \\n[an-margin]
29 .\" old: \\n[rst2man-indent\\n[rst2man-indent-level]]
30 .nr rst2man-indent-level -1
31 .\" new: \\n[rst2man-indent\\n[rst2man-indent-level]]
32 .in \\n[rst2man-indent\\n[rst2man-indent-level]]u
36 \fBopt\fP [\fIoptions\fP] [\fIfilename\fP]
39 The \fBopt\fP command is the modular LLVM optimizer and analyzer. It
40 takes LLVM source files as input, runs the specified optimizations or analyses
41 on it, and then outputs the optimized file or the analysis results. The
42 function of \fBopt\fP depends on whether the \fI\-analyze\fP option is
45 When \fI\-analyze\fP is specified, \fBopt\fP performs various analyses
46 of the input source. It will usually print the results on standard output, but
47 in a few cases, it will print output to standard error or generate a file with
48 the analysis output, which is usually done when the output is meant for another
51 While \fI\-analyze\fP is \fInot\fP given, \fBopt\fP attempts to produce an
52 optimized output file. The optimizations available via \fBopt\fP depend
53 upon what libraries were linked into it as well as any additional libraries
54 that have been loaded with the \fI\%\-load\fP option. Use the \fI\%\-help\fP
55 option to determine what optimizations you can use.
57 If \fBfilename\fP is omitted from the command line or is "\fB\-\fP", \fBopt\fP
58 reads its input from standard input. Inputs can be in either the LLVM assembly
59 language format (\fB\&.ll\fP) or the LLVM bitcode format (\fB\&.bc\fP).
61 If an output filename is not specified with the \fI\%\-o\fP option,
62 \fBopt\fP writes its output to the standard output.
67 Enable binary output on terminals. Normally, \fBopt\fP will refuse to
68 write raw bitcode output if the output stream is a terminal. With this option,
69 \fBopt\fP will write raw bitcode regardless of the output device.
74 Print a summary of command line options.
79 Specify the output filename.
84 Write output in LLVM intermediate language (instead of bitcode).
89 \fBopt\fP provides the ability to run any of LLVM\(aqs optimization or
90 analysis passes in any order. The \fI\%\-help\fP option lists all the passes
91 available. The order in which the options occur on the command line are the
92 order in which they are executed (within pass constraints).
96 .B \-disable\-inlining
97 This option simply removes the inlining pass from the standard list.
102 This option is only meaningful when \fI\-std\-link\-opts\fP is given. It
103 disables most passes.
108 This option causes opt to strip debug information from the module before
109 applying other optimizations. It is essentially the same as \fI\-strip\fP
110 but it ensures that stripping of debug information is done first.
115 This option causes opt to add a verify pass after every pass otherwise
116 specified on the command line (including \fI\-verify\fP). This is useful
117 for cases where it is suspected that a pass is creating an invalid module but
118 it is not clear which pass is doing it.
128 Record the amount of time needed for each pass and print it to standard
134 If this is a debug build, this option will enable debug printouts from passes
135 which use the \fBDEBUG()\fP macro. See the \fI\%LLVM Programmer\(aqs Manual\fP, section \fB#DEBUG\fP for more information.
140 Load the dynamic object \fBplugin\fP\&. This object should register new
141 optimization or analysis passes. Once loaded, the object will add new command
142 line options to enable various optimizations or analyses. To see the new
143 complete list of optimizations, use the \fI\%\-help\fP and \fI\%\-load\fP
144 options together. For example:
150 opt \-load=plugin.so \-help
159 Print module after each transformation.
163 If \fBopt\fP succeeds, it will exit with 0. Otherwise, if an error
164 occurs, it will exit with a non\-zero value.
166 Maintained by The LLVM Team (http://llvm.org/).
168 2003-2014, LLVM Project
169 .\" Generated by docutils manpage writer.