summaryrefslogtreecommitdiff
path: root/docs/GettingStartedVS.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/GettingStartedVS.html
parent05c1dc64936c196d7242567e85710b26e8696336 (diff)
downloadllvm-04367bfc20c021c4105abf0c33b86d55f782d1e8.tar.gz
llvm-04367bfc20c021c4105abf0c33b86d55f782d1e8.tar.bz2
llvm-04367bfc20c021c4105abf0c33b86d55f782d1e8.tar.xz
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/GettingStartedVS.html')
-rw-r--r--docs/GettingStartedVS.html6
1 files changed, 3 insertions, 3 deletions
diff --git a/docs/GettingStartedVS.html b/docs/GettingStartedVS.html
index 9526af57b4..90a30bb040 100644
--- a/docs/GettingStartedVS.html
+++ b/docs/GettingStartedVS.html
@@ -57,7 +57,7 @@
<p>To emphasize, there is no C/C++ front end currently available.
<tt>llvm-gcc</tt> is based on GCC, which cannot be bootstrapped using VC++.
Eventually there should be a <tt>llvm-gcc</tt> based on Cygwin or MinGW that
- is usable. There is also the option of generating bytecode files on Unix and
+ is usable. There is also the option of generating bitcode files on Unix and
copying them over to Windows. But be aware the odds of linking C++ code
compiled with <tt>llvm-gcc</tt> with code compiled with VC++ is essentially
zero.</p>
@@ -257,11 +257,11 @@ All these paths are absolute:</p>
}
</pre></li>
- <li><p>Next, compile the C file into a LLVM bytecode file:</p>
+ <li><p>Next, compile the C file into a LLVM bitcode file:</p>
<p><tt>% llvm-gcc -c hello.c -emit-llvm -o hello.bc</tt></p>
<p>This will create the result file <tt>hello.bc</tt> which is the LLVM
- bytecode that corresponds the the compiled program and the library
+ bitcode that corresponds the the compiled program and the library
facilities that it required. You can execute this file directly using
<tt>lli</tt> tool, compile it to native assembly with the <tt>llc</tt>,
optimize or analyze it further with the <tt>opt</tt> tool, etc.</p>