summaryrefslogtreecommitdiffstats
path: root/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
commit04367bfc20c021c4105abf0c33b86d55f782d1e8 (patch)
tree4cb65ce2b61535ce8b294cabbbfa0e80d30c5dfc /docs/Bugpoint.html
parent05c1dc64936c196d7242567e85710b26e8696336 (diff)
downloadexternal_llvm-04367bfc20c021c4105abf0c33b86d55f782d1e8.zip
external_llvm-04367bfc20c021c4105abf0c33b86d55f782d1e8.tar.gz
external_llvm-04367bfc20c021c4105abf0c33b86d55f782d1e8.tar.bz2
first pass of nomenclature changes in .html files
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@37956 91177308-0d34-0410-b5e6-96231b3b80d8
Diffstat (limited to 'docs/Bugpoint.html')
-rw-r--r--docs/Bugpoint.html4
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/Bugpoint.html b/docs/Bugpoint.html
index 43d237d..bdfd313 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,
<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