6502/llvm-6502
1
0
Fork 0
mirror of https://github.com/c64scene-ar/llvm-6502.git synced 2025-05-16 07:38:43 +00:00
Code Issues Projects Releases Wiki Activity

Remove C Backend from the bugpoint docs

Browse Source 
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@156333 91177308-0d34-0410-b5e6-96231b3b80d8
This commit is contained in:
Pete Cooper 2012-05-07 22:42:40 +00:00
parent 397fc4874e
commit 7e56e92a33
1 changed files with 8 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
docs/CommandGuide/bugpoint.pod
View File

@ -123,23 +123,23 @@ by compiling the program with the "safe" backend and running it.
Profile file loaded by B<--profile-loader>. Profile file loaded by B<--profile-loader>.
=item B<--run-{int,jit,llc,cbe,custom}> =item B<--run-{int,jit,llc,custom}>
Whenever the test program is compiled, B<bugpoint> should generate code for it Whenever the test program is compiled, B<bugpoint> should generate code for it
using the specified code generator. These options allow you to choose the using the specified code generator. These options allow you to choose the
interpreter, the JIT compiler, the static native code compiler, the C interpreter, the JIT compiler, the static native code compiler, or a
backend, or a custom command (see B<--exec-command>) respectively. custom command (see B<--exec-command>) respectively.
=item B<--safe-{llc,cbe,custom}> =item B<--safe-{llc,custom}>
When debugging a code generator, B<bugpoint> should use the specified code When debugging a code generator, B<bugpoint> should use the specified code
generator as the "safe" code generator. This is a known-good code generator generator as the "safe" code generator. This is a known-good code generator
used to generate the "reference output" if it has not been provided, and to used to generate the "reference output" if it has not been provided, and to
compile portions of the program that as they are excluded from the testcase. compile portions of the program that as they are excluded from the testcase.
These options allow you to choose the These options allow you to choose the
static native code compiler, the C backend, or a custom command, static native code compiler, or a custom command, (see B<--exec-command>)
(see B<--exec-command>) respectively. The interpreter and the JIT backends respectively. The interpreter and the JIT backends cannot currently
cannot currently be used as the "safe" backends. be used as the "safe" backends.
=item B<--exec-command> I<command> =item B<--exec-command> I<command>
@ -165,7 +165,7 @@ will be the minimum bitcode that passes FileCheck.
=item B<--safe-path> I<path> =item B<--safe-path> I<path>
This option defines the path to the command to execute with the This option defines the path to the command to execute with the
B<--safe-{int,jit,llc,cbe,custom}> B<--safe-{int,jit,llc,custom}>
option. option.
=back =back