-<ul>
- <li><tt>-additional-so <library></tt><br>
- Load <tt><library></tt> 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.<p>
-
- <li><tt>-args <program args></tt><br>
- Pass all arguments specified after <tt>-args</tt> to the
- test program whenever it runs. Note that if any of
- the <tt><program args></tt> start with a '-', you should use:
- <p>
- <tt>bugpoint <bugpoint args> -args -- <program args></tt>
- <p>
- The "<tt>--</tt>" right after the <tt>-args</tt> option tells
- <tt>bugpoint</tt> to consider any options starting with <tt>-</tt> to be
- part of the <tt>-args</tt> option, not as options to <tt>bugpoint</tt>
- itself.<p>
-
- <li><tt>-tool-args <tool args></tt><br>
- Pass all arguments specified after <tt>-tool-args</tt> to the
- LLVM tool under test (llc, lli, etc.) whenever it runs.
- You should use this option in the following way:
- <p>
- <tt>bugpoint <bugpoint args> -tool-args -- <tool args></tt>
- <p>
- The "<tt>--</tt>" right after the <tt>-tool-args</tt> option tells
- <tt>bugpoint</tt> to consider any options starting with <tt>-</tt> to be
- part of the <tt>-tool-args</tt> option, not as options to
- <tt>bugpoint</tt> itself. (See <tt>-args</tt>, above.)<p>
-
- <li><tt>-check-exit-code={true,false}</tt><br>
- Assume a non-zero exit code or core dump from the test program is
- a failure. Defaults to true.<p>
-
- <li><tt>-disable-{dce,simplifycfg}</tt><br>
- Do not run the specified passes to clean up and reduce the size of the
- test program. By default, <tt>bugpoint</tt> uses these passes internally
- when attempting to reduce test programs. If you're trying to find
- a bug in one of these passes, <tt>bugpoint</tt> may crash.<p>
-
- <li> <tt>-help</tt><br>
- Print a summary of command line options.<p>
-
- <a name="opt_input"><li><tt>-input <filename></tt><br>
- Open <tt><filename></tt> and redirect the standard input of the
- test program, whenever it runs, to come from that file.
- <p>
-
- <a name="opt_load"><li> <tt>-load <plugin></tt><br>
- Load the dynamic object <tt><plugin></tt> into <tt>bugpoint</tt>
- 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:
- <p>
- <tt>bugpoint -load <plugin> -help</tt>
- <p>
-
- <a name="opt_output"><li><tt>-output <filename></tt><br>
- Whenever the test program produces output on its standard output
- stream, it should match the contents of <tt><filename></tt>
- (the "reference output"). If you do not use this option,
- <tt>bugpoint</tt> will attempt to generate a reference output by
- compiling the program with the C backend and running it.<p>
-
- <li><tt>-profile-info-file <filename></tt><br>
- Profile file loaded by -profile-loader.<p>
-
- <a name="opt_run-"><li><tt>-run-{int,jit,llc,cbe}</tt><br>
- Whenever the test program is compiled, <tt>bugpoint</tt> should generate
- code for it using the specified code generator. These options allow
- you to choose the interpreter, the JIT compiler, the static native
- code compiler, or the C backend, respectively.<p>
-</ul>