From: Jeff Cohen Date: Wed, 28 Mar 2007 20:27:51 +0000 (+0000) Subject: Update to current situation. X-Git-Url: http://demsky.eecs.uci.edu/git/?a=commitdiff_plain;h=3c8dfcd53dc7e4b9f82e9e099d27d9d3ee70e6e3;p=oota-llvm.git Update to current situation. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@35440 91177308-0d34-0410-b5e6-96231b3b80d8 --- diff --git a/docs/GettingStartedVS.html b/docs/GettingStartedVS.html index 45e323b6ff4..7934f1ea689 100644 --- a/docs/GettingStartedVS.html +++ b/docs/GettingStartedVS.html @@ -258,7 +258,7 @@ All these paths are absolute:

  • Next, compile the C file into a LLVM bytecode file:

    -

    % llvm-gcc hello.c -emit-llvm -o hello.bc

    +

    % llvm-gcc -c hello.c -emit-llvm -o hello.bc

    This will create the result file hello.bc which is the LLVM bytecode that corresponds the the compiled program and the library @@ -267,12 +267,17 @@ All these paths are absolute:

    optimize or analyze it further with the opt tool, etc.

    Note: while you cannot do this step on Windows, you can do it on a - Unix system and transfer hello.bc to Windows.

  • + Unix system and transfer hello.bc to Windows. Important: + transfer as a binary file!

  • Run the program using the just-in-time compiler:

    % lli hello.bc

  • +

    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.

    +
  • Use the llvm-dis utility to take a look at the LLVM assembly code:

    @@ -286,6 +291,11 @@ All these paths are absolute:

    % cl hello.cbe.c

  • +

    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. Currently, it + doesn't even work for trivial C programs such as the one above.

    +
  • Execute the native code program:

    % hello.cbe.exe