Jeff's fix was fine

[oota-llvm.git] / docs / GettingStartedVS.html

diff --git a/docs/GettingStartedVS.html b/docs/GettingStartedVS.html
index 15b31b011fa7c654eec16717955a27140053fa55..9526af57b47f048c82cf5008332e63d00e057dc8 100644 (file)
--- a/docs/GettingStartedVS.html
+++ b/docs/GettingStartedVS.html
@@ -258,26 +258,26 @@ All these paths are absolute:</p>
        </pre></li>
 
   <li><p>Next, compile the C file into a LLVM bytecode file:</p>
-      <p><tt>% llvm-gcc hello.c -o hello</tt></p>
-
-      <p>Note that you should have already built the tools and they have to be
-      in your path, at least <tt>gccas</tt> and <tt>gccld</tt>.</p>
-
-      <p>This will create two result files: <tt>hello</tt> and
-      <tt>hello.bc</tt>. The <tt>hello.bc</tt> is the LLVM bytecode that
-      corresponds the the compiled program and the library facilities that it
-      required.  <tt>hello</tt> is a simple shell script that runs the bytecode
-      file with <tt>lli</tt>, making the result directly executable.  Note that
-      all LLVM optimizations are enabled by default, so there is no need for a 
-      "-O3" switch.</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 
+      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> 
       
       <p><b>Note: while you cannot do this step on Windows, you can do it on a
-        Unix system and transfer <tt>hello.bc</tt> to Windows.</b></p></li>
+        Unix system and transfer <tt>hello.bc</tt> to Windows.  Important:
+        transfer as a binary file!</b></p></li>
 
   <li><p>Run the program using the just-in-time compiler:</p>
       
       <p><tt>% lli hello.bc</tt></p></li>
 
+      <p>Note: this will only work for trivial C programs.  Non-trivial programs
+        (and any C++ program) will have dependencies on the GCC runtime that
+        won't be satisfied by the Microsoft runtime libraries.</p>
+
   <li><p>Use the <tt>llvm-dis</tt> utility to take a look at the LLVM assembly
       code:</p>
 
@@ -291,6 +291,10 @@ All these paths are absolute:</p>
 
       <p><tt>% cl hello.cbe.c</tt></p></li>
 
+      <p>Note: this will only work for trivial C programs.  Non-trivial programs
+        (and any C++ program) will have dependencies on the GCC runtime that
+        won't be satisfied by the Microsoft runtime libraries.</p>
+
   <li><p>Execute the native code program:</p>
 
       <p><tt>% hello.cbe.exe</tt></p></li>