X-Git-Url: http://plrg.eecs.uci.edu/git/?a=blobdiff_plain;f=docs%2FBugpoint.html;h=0f5a511f71cbbe9217f85c62250569846fe94d11;hb=a3437647dc6996499db4823c31242184c93e6e2e;hp=43d237d094e3fe16bf6742cb5efcfb378959bf0b;hpb=434262ad518dad47841189b27fb9f3943d8206b8;p=oota-llvm.git diff --git a/docs/Bugpoint.html b/docs/Bugpoint.html index 43d237d094e..0f5a511f71c 100644 --- a/docs/Bugpoint.html +++ b/docs/Bugpoint.html @@ -123,7 +123,7 @@ functions has been reduced, it attempts to delete various edges in the control flow graph, to reduce the size of the function as much as possible. Finally, bugpoint deletes any individual LLVM instructions whose absence does not eliminate the failure. At the end, bugpoint should tell you what -passes crash, give you a bytecode file, and give you instructions on how to +passes crash, give you a bitcode file, and give you instructions on how to reproduce the failure with opt or llc.
@@ -141,7 +141,7 @@ test program and partitions it into two pieces: one piece which it compiles with the C backend (into a shared object), and one piece which it runs with either the JIT or the static LLC compiler. It uses several techniques to reduce the amount of code pushed through the LLVM code generator, to reduce the -potential scope of the problem. After it is finished, it emits two bytecode +potential scope of the problem. After it is finished, it emits two bitcode files (called "test" [to be compiled with the code generator] and "safe" [to be compiled with the C backend], respectively), and instructions for reproducing the problem. The code generator debugger assumes that the C backend produces @@ -211,11 +211,6 @@ non-obvious ways. Here are some hints and tips:you might try llvm-link -v on the same set of input files. If that also crashes, you may be experiencing a linker bug. -