Written by Chris Lattner and - Misha Brukman
+ @@ -148,7 +148,7 @@ compilation, compile your test-case to a .s file with the -save-temps option to llvm-gcc. Then run:gccas -debug-pass=Arguments < /dev/null -o - > /dev/null+
gccas -debug-pass=Arguments < /dev/null -o - > /dev/null
... which will print a list of arguments, indicating the list of passes that @@ -171,9 +171,9 @@ being linked together (the "llvm-gcc -v" output should include the full list of objects linked). Then run:
-llvm-as < /dev/null > null.bc -gccld -debug-pass=Arguments null.bc +llvm-as < /dev/null > null.bc
+gccld -debug-pass=Arguments null.bc +
... which will print a list of arguments, indicating the list of passes that @@ -196,19 +196,19 @@ order to reduce the list of passes (which is probably large) and the input to something tractable, use the bugpoint tool as follows:
bugpoint <input files> <list of passes>+
bugpoint <input files> <list of passes>
bugpoint will print a bunch of output as it reduces the test-case, but it should eventually print something like this:
-... -Emitted bytecode to 'bugpoint-reduced-simplified.bc' - -*** You can reproduce the problem with: opt bugpoint-reduced-simplified.bc -licm -+
+...
+Emitted bytecode to 'bugpoint-reduced-simplified.bc'
+
+*** You can reproduce the problem with: opt bugpoint-reduced-simplified.bc -licm
+
Once you complete this, please send the LLVM bytecode file and the command @@ -242,8 +242,8 @@ which code generator you wish to compile the program with (e.g. C backend, the JIT, or LLC) and optionally a series of LLVM passes to run. For example:
-bugpoint -run-cbe [... optimization passes ...] file-to-test.bc --args -- [program arguments]+
+bugpoint -run-cbe [... optzn passes ...] file-to-test.bc --args -- [program arguments]
bugpoint will try to narrow down your list of passes to the one pass @@ -295,10 +295,10 @@ debug the JIT, LLC, and CBE, using the pre-written Makefile targets, which will pass the program options specified in the Makefiles:
-cd llvm/test/../../program +++cd llvm/test/../../program
make bugpoint-jit -
At the end of a successful bugpoint run, you will be presented @@ -314,28 +314,28 @@ the following:
Regenerate the shared object from the safe bytecode file:
-llc -march=c safe.bc -o safe.c +++llc -march=c safe.bc -o safe.c
gcc -shared safe.c -o safe.so -
If debugging LLC, compile test bytecode native and link with the shared object:
-llc test.bc -o test.s -f -gcc test.s safe.so -o test.llc +++llc test.bc -o test.s -f
+gcc test.s safe.so -o test.llc
./test.llc [program options] -
If debugging the JIT, load the shared object and supply the test bytecode:
lli -load=safe.so test.bc [program options]+
lli -load=safe.so test.bc [program options]