diff options
author | Reid Spencer <rspencer@reidspencer.com> | 2007-02-09 15:59:08 +0000 |
---|---|---|
committer | Reid Spencer <rspencer@reidspencer.com> | 2007-02-09 15:59:08 +0000 |
commit | 434262ad518dad47841189b27fb9f3943d8206b8 (patch) | |
tree | 5c5a3ebd2172b71a76f0319e54849e82cea05a47 /docs/GettingStartedVS.html | |
parent | 43eb96c3ef62c69ccec13e7326a5660a74483f04 (diff) | |
download | external_llvm-434262ad518dad47841189b27fb9f3943d8206b8.zip external_llvm-434262ad518dad47841189b27fb9f3943d8206b8.tar.gz external_llvm-434262ad518dad47841189b27fb9f3943d8206b8.tar.bz2 |
Remove references to gccld and gccas, adjusting the documentation to
mention llvm-ld and opt instead (if appropriate).
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@34094 91177308-0d34-0410-b5e6-96231b3b80d8
Diffstat (limited to 'docs/GettingStartedVS.html')
-rw-r--r-- | docs/GettingStartedVS.html | 19 |
1 files changed, 7 insertions, 12 deletions
diff --git a/docs/GettingStartedVS.html b/docs/GettingStartedVS.html index 15b31b0..45e323b 100644 --- a/docs/GettingStartedVS.html +++ b/docs/GettingStartedVS.html @@ -258,18 +258,13 @@ 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 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> |