diff --git a/llvm/docs/CommandGuide/llvmgcc.pod b/llvm/docs/CommandGuide/llvmgcc.pod
index 0b2b1566824b..9892ca71861e 100644
--- a/llvm/docs/CommandGuide/llvmgcc.pod
+++ b/llvm/docs/CommandGuide/llvmgcc.pod
@@ -15,12 +15,14 @@ version of gcc that compiles C/ObjC programs into native objects, LLVM
 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 bitcode files instead.
-If B<-S> (assembly) is also given, then it will generate LLVM assembly. 
+B<-emit-llvm> and B<-c> options are given then it will generate LLVM bitcode files
+instead. If B<-emit-llvm> and B<-S> are given, then it will generate LLVM
+assembly.
 
 Being derived from the GNU Compiler Collection, B<llvm-gcc> has many
 of gcc's features and accepts most of gcc's options.  It handles a
-number of gcc's extensions to the C programming language.
+number of gcc's extensions to the C programming language.  See the gcc
+documentation for details.
 
 =head1 OPTIONS
 
@@ -30,18 +32,6 @@ number of gcc's extensions to the C programming language.
 
 Print a summary of command line options.
 
-=item B<-S>
-
-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 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>
 
 Specify the output file to be I<filename>.
@@ -63,8 +53,9 @@ be a bitcode library.
 
 =item B<-emit-llvm>
 
-Make the output be LLVM bitcode (or assembly) instead of native object (or
-assembly).
+Make the output be LLVM bitcode (with B<-c>) or assembly (with B<-s>) instead
+of native object (or assembly).  If B<-emit-llvm> is given without either B<-c>
+or B<-S> it has no effect.
 
 =back