Remove bizarre use of /dev/null in a makefile include line that

[oota-llvm.git] / docs / CommandGuide / llvmc.pod

diff --git a/docs/CommandGuide/llvmc.pod b/docs/CommandGuide/llvmc.pod
index e398a4eba802e503de604506515878cc44c74fa1..5e6cc9513ef53282bd34e050efad444bea12fa5c 100644 (file)
--- a/docs/CommandGuide/llvmc.pod
+++ b/docs/CommandGuide/llvmc.pod
@@ -69,13 +69,13 @@ into a set of basic actions to be done:
 
 =item * Pre-processing: gathering/filtering compiler input (optional).
 
-=item * Translation: source language to bytecode conversion.
+=item * Translation: source language to bitcode conversion.
 
-=item * Assembly: bytecode to native code conversion.
+=item * Assembly: bitcode to native code conversion.
 
-=item * Optimization: conversion of bytecode to something that runs faster.
+=item * Optimization: conversion of bitcode to something that runs faster.
 
-=item * Linking: combining multiple bytecodes to produce executable program.
+=item * Linking: combining multiple bitcode files to produce executable program.
 
 =back
 
@@ -99,7 +99,7 @@ following control options are defined:
 
 This option specifies that the linking phase is not to be run. All
 previous phases, if applicable will run. This is generally how a given
-bytecode file is compiled and optimized for a source language module.
+bitcode file is compiled and optimized for a source language module.
 
 =item B<-k> or B<--link> or default
 
@@ -145,7 +145,7 @@ this is the default level of optimization.
 This level of optimization specifies a balance between generating good code 
 that will execute reasonably quickly and not spending too much time optimizing
 the code to get there. For example, this level of optimization may include 
-things like global common subexpression elimination, aggressive dead code 
+things like global common sub-expression elimination, aggressive dead code 
 elimination, and scalar replication.
 
 =item B<-O3> (aggressive optimization)
@@ -173,7 +173,7 @@ aggressive inter-procedural optimization.
 
 This is the same as B<-O5> except that it employs profile-guided
 re-optimization of the program after it has executed. Note that this implies
-a single level of re-optimization based on runtime profile analysis. Once
+a single level of re-optimization based on run time profile analysis. Once
 the re-optimization has completed, the profiling instrumentation is
 removed and final optimizations are employed.
 
@@ -220,7 +220,7 @@ of the option names the back end to use.
 
 =item B<--native>
 
-Normally, B<llvmc> produces bytecode files at most stages of compilation.
+Normally, B<llvmc> produces bitcode files at most stages of compilation.
 With this option, B<llvmc> will arrange for native object files to be
 generated with the B<-c> option, native assembly files to be generated
 with the B<-S> option, and native executables to be generated with the