blob: d940f0d42910d580971b85fb7a1e6cbc4699d207 [file] [log] [blame]
Brian Gaekeff0c7662004-07-01 20:29:08 +00001=pod
2
3=head1 NAME
4
5bugpoint - automatic test case reduction tool
6
7=head1 SYNOPSIS
8
Misha Brukmanc08937a2004-07-02 16:06:19 +00009B<bugpoint> [I<options>] [I<input LLVM ll/bc files>] [I<LLVM passes>] B<--args>
Misha Brukmana856f5b2004-07-02 15:42:20 +000010I<program arguments>
Brian Gaekeff0c7662004-07-01 20:29:08 +000011
12=head1 DESCRIPTION
13
Misha Brukman595d32e2004-07-02 15:36:29 +000014B<bugpoint> narrows down the source of problems in LLVM tools and passes. It
15can be used to debug three types of failures: optimizer crashes, miscompilations
16by optimizers, or bad native code generation (including problems in the static
17and JIT compilers). It aims to reduce large test cases to small, useful ones.
Misha Brukmanee3b0452004-12-09 20:28:42 +000018For more information on the design and inner workings of B<bugpoint>, as well as
19advice for using bugpoint, see F<llvm/docs/Bugpoint.html> in the LLVM
20distribution.
Brian Gaekeff0c7662004-07-01 20:29:08 +000021
22=head1 OPTIONS
23
24=over
25
26=item B<--additional-so> F<library>
27
28Load the dynamic shared object F<library> into the test program whenever it is
29run. This is useful if you are debugging programs which depend on non-LLVM
30libraries (such as the X or curses libraries) to run.
31
32=item B<--args> I<program args>
33
34Pass all arguments specified after -args to the test program whenever it runs.
35Note that if any of the I<program args> start with a '-', you should use:
36
37 bugpoint [bugpoint args] --args -- [program args]
38
39The "--" right after the B<--args> option tells B<bugpoint> to consider any
40options starting with C<-> to be part of the B<--args> option, not as options to
41B<bugpoint> itself.
42
43=item B<--tool-args> I<tool args>
44
45Pass all arguments specified after --tool-args to the LLVM tool under test
46(B<llc>, B<lli>, etc.) whenever it runs. You should use this option in the
47following way:
48
49 bugpoint [bugpoint args] --tool-args -- [tool args]
50
51The "--" right after the B<--tool-args> option tells B<bugpoint> to consider any
52options starting with C<-> to be part of the B<--tool-args> option, not as
53options to B<bugpoint> itself. (See B<--args>, above.)
54
55=item B<--check-exit-code>=I<{true,false}>
56
57Assume a non-zero exit code or core dump from the test program is a failure.
58Defaults to true.
59
60=item B<--disable-{dce,simplifycfg}>
61
62Do not run the specified passes to clean up and reduce the size of the test
63program. By default, B<bugpoint> uses these passes internally when attempting to
64reduce test programs. If you're trying to find a bug in one of these passes,
65B<bugpoint> may crash.
66
Patrick Jenkins7d686d52006-08-15 17:31:58 +000067=item B<-find-bugs>
68
69Continually randomize the specified passes and run them on the test program
Patrick Jenkins80d92442006-08-15 17:39:40 +000070until a bug is found or the user kills B<bugpoint>.
Patrick Jenkins7d686d52006-08-15 17:31:58 +000071
Brian Gaekeff0c7662004-07-01 20:29:08 +000072=item B<--help>
73
74Print a summary of command line options.
75
76=item B<--input> F<filename>
77
78Open F<filename> and redirect the standard input of the test program, whenever
79it runs, to come from that file.
80
81=item B<--load> F<plugin>
82
83Load the dynamic object F<plugin> into B<bugpoint> itself. This object should
84register new optimization passes. Once loaded, the object will add new command
85line options to enable various optimizations. To see the new complete list of
86optimizations, use the B<--help> and B<--load> options together; for example:
87
88 bugpoint --load myNewPass.so --help
89
90=item B<--output> F<filename>
91
92Whenever the test program produces output on its standard output stream, it
93should match the contents of F<filename> (the "reference output"). If you
94do not use this option, B<bugpoint> will attempt to generate a reference output
95by compiling the program with the C backend and running it.
96
97=item B<--profile-info-file> F<filename>
98
99Profile file loaded by B<--profile-loader>.
100
101=item B<--run-{int,jit,llc,cbe}>
102
103Whenever the test program is compiled, B<bugpoint> should generate code for it
104using the specified code generator. These options allow you to choose the
105interpreter, the JIT compiler, the static native code compiler, or the C
106backend, respectively.
107
Nick Lewyckyd9c294b2006-09-14 04:33:29 +0000108=item B<--enable-valgrind>
109
110Use valgrind to find faults in the optimization phase. This will allow
111bugpoint to find otherwise asymptomatic problems caused by memory
112mis-management.
113
Brian Gaekeff0c7662004-07-01 20:29:08 +0000114=back
115
116=head1 EXIT STATUS
117
118If B<bugpoint> succeeds in finding a problem, it will exit with 0. Otherwise,
119if an error occurs, it will exit with a non-zero value.
120
121=head1 SEE ALSO
122
Reid Spencer84f82f72006-08-28 00:34:19 +0000123L<opt|opt>
Brian Gaekeff0c7662004-07-01 20:29:08 +0000124
125=head1 AUTHOR
126
Reid Spencercd143fc2006-03-14 05:42:07 +0000127Maintained by the LLVM Team (L<http://llvm.org>).
Brian Gaekeff0c7662004-07-01 20:29:08 +0000128
129=cut