eliminated all references to 'bytecode' from .pod files
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@38452 91177308-0d34-0410-b5e6-96231b3b80d8
diff --git a/docs/CommandGuide/llvmgcc.pod b/docs/CommandGuide/llvmgcc.pod
index 3accd03..0b2b156 100644
--- a/docs/CommandGuide/llvmgcc.pod
+++ b/docs/CommandGuide/llvmgcc.pod
@@ -12,10 +12,10 @@
The B<llvm-gcc> command is the LLVM C front end. It is a modified
version of gcc that compiles C/ObjC programs into native objects, LLVM
-bytecode or LLVM assembly language, depending upon the options.
+bitcode or LLVM assembly language, depending upon the options.
By default, B<llvm-gcc> compiles to native objects just like GCC does. If the
-B<-emit-llvm> option is given then it will generate LLVM bytecode files instead.
+B<-emit-llvm> option is given then it will generate LLVM bitcode files instead.
If B<-S> (assembly) is also given, then it will generate LLVM assembly.
Being derived from the GNU Compiler Collection, B<llvm-gcc> has many
@@ -32,14 +32,14 @@
=item B<-S>
-Do not generate an LLVM bytecode file. Rather, compile the source
+Do not generate an LLVM bitcode file. Rather, compile the source
file into an LLVM assembly language file.
=item B<-c>
Do not generate a linked executable. Rather, compile the source
-file into an LLVM bytecode file. This bytecode file can then be
-linked with other bytecode files later on to generate a full LLVM
+file into an LLVM bitcode file. This bitcode file can then be
+linked with other bitcode files later on to generate a full LLVM
executable.
=item B<-o> I<filename>
@@ -59,11 +59,11 @@
=item B<-l>I<name>
Link in the library libI<name>.[bc | a | so]. This library should
-be a bytecode library.
+be a bitcode library.
=item B<-emit-llvm>
-Make the output be LLVM bytecode (or assembly) instead of native object (or
+Make the output be LLVM bitcode (or assembly) instead of native object (or
assembly).
=back