summaryrefslogtreecommitdiffstats
path: root/llvm/docs/Bugpoint.html
diff options
context:
space:
mode:
authorGabor Greif <ggreif@gmail.com>2007-07-06 22:07:22 +0000
committerGabor Greif <ggreif@gmail.com>2007-07-06 22:07:22 +0000
commita54634adeffe67b31ccf8537c305c5235bf94ca0 (patch)
tree7bb3069907771cfe86b9e33ff443e1e811116d0f /llvm/docs/Bugpoint.html
parent12358b482788c1735fe6bbe2bff63015c6b43696 (diff)
downloadbcm5719-llvm-a54634adeffe67b31ccf8537c305c5235bf94ca0.tar.gz
bcm5719-llvm-a54634adeffe67b31ccf8537c305c5235bf94ca0.zip
first pass of nomenclature changes in .html files
llvm-svn: 37956
Diffstat (limited to 'llvm/docs/Bugpoint.html')
-rw-r--r--llvm/docs/Bugpoint.html4
1 files changed, 2 insertions, 2 deletions
diff --git a/llvm/docs/Bugpoint.html b/llvm/docs/Bugpoint.html
index 43d237d094e..bdfd31379a9 100644
--- a/llvm/docs/Bugpoint.html
+++ b/llvm/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,
<tt>bugpoint</tt> deletes any individual LLVM instructions whose absence does
not eliminate the failure. At the end, <tt>bugpoint</tt> 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 <tt>opt</tt> or <tt>llc</tt>.</p>
</div>
@@ -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
OpenPOWER on IntegriCloud