Lines Matching +full:- +full:- +full:exit +full:- +full:code
1 bugpoint - automatic test case reduction tool
5 --------
7 **bugpoint** [*options*] [*input LLVM ll/bc files*] [*LLVM passes*] **--args**
11 -----------
15 by optimizers, or bad native code generation (including problems in the static
22 -------
24 **--additional-so** *library*
27 run. This is useful if you are debugging programs which depend on non-LLVM
30 **--append-exit-code**\ =\ *{true,false}*
32 Append the test programs exit code to the output file so that a change in exit
33 code is considered a test failure. Defaults to false.
35 **--args** *program args*
37 Pass all arguments specified after **--args** to the test program whenever it runs.
38 Note that if any of the *program args* start with a "``-``", you should use:
40 .. code-block:: bash
42 bugpoint [bugpoint args] --args -- [program args]
44 The "``--``" right after the **--args** option tells **bugpoint** to consider
45 any options starting with "``-``" to be part of the **--args** option, not as
48 **--tool-args** *tool args*
50 Pass all arguments specified after **--tool-args** to the LLVM tool under test
54 .. code-block:: bash
56 bugpoint [bugpoint args] --tool-args -- [tool args]
58 The "``--``" right after the **--tool-args** option tells **bugpoint** to
59 consider any options starting with "``-``" to be part of the **--tool-args**
60 option, not as options to **bugpoint** itself. (See **--args**, above.)
62 **--safe-tool-args** *tool args*
64 Pass all arguments specified after **--safe-tool-args** to the "safe" execution
67 **--gcc-tool-args** *gcc tool args*
69 Pass all arguments specified after **--gcc-tool-args** to the invocation of
72 **--opt-args** *opt args*
74 Pass all arguments specified after **--opt-args** to the invocation of **opt**.
76 **--disable-{dce,simplifycfg}**
83 **--enable-valgrind**
87 mis-management.
89 **-find-bugs**
94 **-help**
98 **--input** *filename*
103 **--load** *plugin*
108 optimizations, use the **-help** and **--load** options together; for example:
111 .. code-block:: bash
113 bugpoint --load myNewPass.so -help
115 **--mlimit** *megabytes*
120 **--output** *filename*
127 **--run-{int,jit,llc,custom}**
129 Whenever the test program is compiled, **bugpoint** should generate code for it
130 using the specified code generator. These options allow you to choose the
131 interpreter, the JIT compiler, the static native code compiler, or a
132 custom command (see **--exec-command**) respectively.
134 **--safe-{llc,custom}**
136 When debugging a code generator, **bugpoint** should use the specified code
137 generator as the "safe" code generator. This is a known-good code generator
141 static native code compiler, or a custom command, (see **--exec-command**)
145 **--exec-command** *command*
147 This option defines the command to use with the **--run-custom** and
148 **--safe-custom** options to execute the bitcode testcase. This can
149 be useful for cross-compilation.
151 **--compile-command** *command*
153 This option defines the command to use with the **--compile-custom**
154 option to compile the bitcode testcase. The command should exit with a
155 failure exit code if the file is "interesting" and should exit with a
156 success exit code (i.e. 0) otherwise (this is the same as if it crashed on
162 testcase and pass the name of an executable compile-command script in this form:
164 .. code-block:: sh
168 not FileCheck [bugpoint input file].ll < bugpoint-test-program.s
173 **--safe-path** *path*
176 **--safe-{int,jit,llc,custom}**
179 EXIT STATUS
180 -----------
182 If **bugpoint** succeeds in finding a problem, it will exit with 0. Otherwise,
183 if an error occurs, it will exit with a non-zero value.
186 --------