llvm.org GIT mirror llvm / b57b066
Documented bugpoint --compile-custom --compile-command. I've used it a few times to reduce unit tests and gotten one request for information on it. It's not easy to use correctly because bugpoint doesn't tell you when you're doing it wrong. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@129507 91177308-0d34-0410-b5e6-96231b3b80d8 Andrew Trick 9 years ago
1 changed file(s) with 16 addition(s) and 2 deletion(s). Raw diff Collapse all Expand all
2020
2121 =head1 OPTIONS
2222
23 =over
23 =over
2424
2525 =item B<--additional-so> F
2626
8686 =item B<-find-bugs>
8787
8888 Continually randomize the specified passes and run them on the test program
89 until a bug is found or the user kills B.
89 until a bug is found or the user kills B.
9090
9191 =item B<-help>
9292
146146 B<--safe-custom> options to execute the bitcode testcase. This can
147147 be useful for cross-compilation.
148148
149 =item B<--compile-command> I
150
151 This option defines the command to use with the B<--compile-custom>
152 option to compile the bitcode testcase. This can be useful for
153 testing compiler output without running any link or execute stages. To
154 generate a reduced unit test, you may add CHECK directives to the
155 testcase and pass the name of a compile-command script in this form:
156
157 llc "$@"
158 not FileCheck [bugpoint input file].ll < bugpoint-test-program.s
159
160 This script will "fail" as long as FileCheck passes. So the result
161 will be the minimum bitcode that passes FileCheck.
162
149163 =item B<--safe-path> I
150164
151165 This option defines the path to the command to execute with the