$FreeBSD$
Automatically generated by Pod::Man 2.23 (Pod::Simple 3.14)

Standard preamble:
========================================================================
..

..

.. Set up some character translations and predefined strings. \*(-- will
give an unbreakable dash, \*(PI will give pi, \*(L" will give a left
double quote, and \*(R" will give a right double quote. \*(C+ will
give a nicer C++. Capital omega is used to do unbreakable dashes and
therefore won't be available. \*(C` and \*(C' expand to `' in nroff,
nothing in troff, for use with C<>.
.tr \(*W- . ds -- \(*W- . ds PI pi . if (\n(.H=4u)&(1m=24u) .ds -- \(*W\h'-12u'\(*W\h'-12u'-\" diablo 10 pitch . if (\n(.H=4u)&(1m=20u) .ds -- \(*W\h'-12u'\(*W\h'-8u'-\" diablo 12 pitch . ds L" "" . ds R" "" . ds C` "" . ds C' "" 'br\} . ds -- \|\(em\| . ds PI \(*p . ds L" `` . ds R" '' 'br\}
Escape single quotes in literal strings from groff's Unicode transform.

If the F register is turned on, we'll generate index entries on stderr for
titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index
entries marked with X<> in POD. Of course, you'll have to process the
output yourself in some meaningful fashion.
. de IX . tm Index:\\$1\t\\n%\t"\\$2" .. . nr % 0 . rr F .\} . de IX .. .\}
Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2).
Fear. Run. Save yourself. No user-serviceable parts.
. \" fudge factors for nroff and troff . ds #H 0 . ds #V .8m . ds #F .3m . ds #[ \f1 . ds #] .\} . ds #H ((1u-(\\\\n(.fu%2u))*.13m) . ds #V .6m . ds #F 0 . ds #[ \& . ds #] \& .\} . \" simple accents for nroff and troff . ds ' \& . ds ` \& . ds ^ \& . ds , \& . ds ~ ~ . ds / .\} . ds ' \\k:\h'-(\\n(.wu*8/10-\*(#H)'\'\h"|\\n:u" . ds ` \\k:\h'-(\\n(.wu*8/10-\*(#H)'\`\h'|\\n:u' . ds ^ \\k:\h'-(\\n(.wu*10/11-\*(#H)'^\h'|\\n:u' . ds , \\k:\h'-(\\n(.wu*8/10)',\h'|\\n:u' . ds ~ \\k:\h'-(\\n(.wu-\*(#H-.1m)'~\h'|\\n:u' . ds / \\k:\h'-(\\n(.wu*8/10-\*(#H)'\z\(sl\h'|\\n:u' .\} . \" troff and (daisy-wheel) nroff accents . \" corrections for vroff . \" for low resolution devices (crt and lpr) \{\ . ds : e . ds 8 ss . ds o a . ds d- d\h'-1'\(ga . ds D- D\h'-1'\(hy . ds th \o'bp' . ds Th \o'LP' . ds ae ae . ds Ae AE .\} ========================================================================

Title "BUGPOINT 1" For nroff, turn off justification. Always turn off hyphenation; it makes
way too many mistakes in technical documents.
bugpoint - automatic test case reduction tool Header "SYNOPSIS" \fBbugpoint [options] [input \s-1LLVM\s0 ll/bc files] [\s-1LLVM\s0 passes] --args \fIprogram arguments Header "DESCRIPTION" \fBbugpoint narrows down the source of problems in \s-1LLVM\s0 tools and passes. It can be used to debug three types of failures: optimizer crashes, miscompilations by optimizers, or bad native code generation (including problems in the static and \s-1JIT\s0 compilers). It aims to reduce large test cases to small, useful ones. For more information on the design and inner workings of bugpoint, as well as advice for using bugpoint, see llvm/docs/Bugpoint.html in the \s-1LLVM\s0 distribution. Header "OPTIONS" Item "--additional-so library" Load the dynamic shared object library into the test program whenever it is run. This is useful if you are debugging programs which depend on non-LLVM libraries (such as the X or curses libraries) to run. Item "--append-exit-code={true,false}" Append the test programs exit code to the output file so that a change in exit code is considered a test failure. Defaults to false. Item "--args program args" Pass all arguments specified after -args to the test program whenever it runs. Note that if any of the program args start with a '-', you should use: .Sp .Vb 1 bugpoint [bugpoint args] --args -- [program args] .Ve .Sp The \*(L"--\*(R" right after the --args option tells bugpoint to consider any options starting with \*(C`-\*(C' to be part of the --args option, not as options to \fBbugpoint itself. Item "--tool-args tool args" Pass all arguments specified after --tool-args to the \s-1LLVM\s0 tool under test (llc, lli, etc.) whenever it runs. You should use this option in the following way: .Sp .Vb 1 bugpoint [bugpoint args] --tool-args -- [tool args] .Ve .Sp The \*(L"--\*(R" right after the --tool-args option tells bugpoint to consider any options starting with \*(C`-\*(C' to be part of the --tool-args option, not as options to bugpoint itself. (See --args, above.) Item "--safe-tool-args tool args" Pass all arguments specified after --safe-tool-args to the \*(L"safe\*(R" execution tool. Item "--gcc-tool-args gcc tool args" Pass all arguments specified after --gcc-tool-args to the invocation of \fBgcc. Item "--opt-args opt args" Pass all arguments specified after --opt-args to the invocation of opt. Item "--disable-{dce,simplifycfg}" Do not run the specified passes to clean up and reduce the size of the test program. By default, bugpoint uses these passes internally when attempting to reduce test programs. If you're trying to find a bug in one of these passes, \fBbugpoint may crash. Item "--enable-valgrind" Use valgrind to find faults in the optimization phase. This will allow bugpoint to find otherwise asymptomatic problems caused by memory mis-management. Item "-find-bugs" Continually randomize the specified passes and run them on the test program until a bug is found or the user kills bugpoint. Item "-help" Print a summary of command line options. Item "--input filename" Open filename and redirect the standard input of the test program, whenever it runs, to come from that file. Item "--load plugin" Load the dynamic object plugin into bugpoint itself. This object should register new optimization passes. Once loaded, the object will add new command line options to enable various optimizations. To see the new complete list of optimizations, use the -help and --load options together; for example: .Sp .Vb 1 bugpoint --load myNewPass.so -help .Ve Item "--mlimit megabytes" Specifies an upper limit on memory usage of the optimization and codegen. Set to zero to disable the limit. Item "--output filename" Whenever the test program produces output on its standard output stream, it should match the contents of filename (the \*(L"reference output\*(R"). If you do not use this option, bugpoint will attempt to generate a reference output by compiling the program with the \*(L"safe\*(R" backend and running it. Item "--profile-info-file filename" Profile file loaded by --profile-loader. Item "--run-{int,jit,llc,cbe,custom}" Whenever the test program is compiled, bugpoint should generate code for it using the specified code generator. These options allow you to choose the interpreter, the \s-1JIT\s0 compiler, the static native code compiler, the C backend, or a custom command (see --exec-command) respectively. Item "--safe-{llc,cbe,custom}" When debugging a code generator, bugpoint should use the specified code generator as the \*(L"safe\*(R" code generator. This is a known-good code generator used to generate the \*(L"reference output\*(R" if it has not been provided, and to compile portions of the program that as they are excluded from the testcase. These options allow you to choose the static native code compiler, the C backend, or a custom command, (see --exec-command) respectively. The interpreter and the \s-1JIT\s0 backends cannot currently be used as the \*(L"safe\*(R" backends. Item "--exec-command command" This option defines the command to use with the --run-custom and \fB--safe-custom options to execute the bitcode testcase. This can be useful for cross-compilation. Item "--compile-command command" This option defines the command to use with the --compile-custom option to compile the bitcode testcase. This can be useful for testing compiler output without running any link or execute stages. To generate a reduced unit test, you may add \s-1CHECK\s0 directives to the testcase and pass the name of an executable compile-command script in this form: .Sp .Vb 3 #!/bin/sh llc "$@" not FileCheck [bugpoint input file].ll < bugpoint-test-program.s .Ve .Sp This script will \*(L"fail\*(R" as long as FileCheck passes. So the result will be the minimum bitcode that passes FileCheck. Item "--safe-path path" This option defines the path to the command to execute with the \fB--safe-{int,jit,llc,cbe,custom} option. Header "EXIT STATUS" If bugpoint succeeds in finding a problem, it will exit with 0. Otherwise, if an error occurs, it will exit with a non-zero value. Header "SEE ALSO" opt Header "AUTHOR" Maintained by the \s-1LLVM\s0 Team (<http://llvm.org/>).