The Visual Studio port at this time is experimental. It is suitable for - use only if you are writing your own compiler front end or otherwise have a +
The Visual Studio port has some limitations. It is suitable for + use if you are writing your own compiler front end or otherwise have a need to dynamically generate machine code. The JIT and interpreter are functional, but it is currently not possible to generate assembly code which - is then assembled into an executable. You can indirectly create executables - by using the C back end.
+ is then assembled into an executable. You can output object files + in COFF format, though. You can also indirectly create executables + by using the C backend. -To emphasize, there is no C/C++ front end currently available. - llvm-gcc is based on GCC, which cannot be bootstrapped using VC++. - Eventually there should be a llvm-gcc based on Cygwin or MinGW that - is usable. There is also the option of generating bitcode files on Unix and - copying them over to Windows. But be aware the odds of linking C++ code - compiled with llvm-gcc with code compiled with VC++ is essentially - zero.
+llvm-gcc is based on GCC, which cannot be bootstrapped + using VC++. There are llvm-gcc binaries based on MinGW + available on the + LLVM download + page. Eventually, Clang + will be able to produce executables on Windows.
-The LLVM test suite cannot be run on the Visual Studio port at this - time.
- -Most of the tools build and work. bugpoint does build, but does - not work. The other tools 'should' work, but have not been fully tested.
+bugpoint does build, but does not work. The other tools + 'should' work, but have not been fully tested.
Additional information about the LLVM directory structure and tool chain can be found on the main Getting Started @@ -74,89 +64,6 @@
Here's the short story for getting up and running quickly with LLVM:
- -It is strongly encouraged that you get the latest version from Subversion as -changes are continually making the VS support better.
- -The remainder of this guide is meant to get you up and running with -LLVM using Visual Studio and to give you some basic information about the LLVM -environment.
+Here's the short story for getting up and running quickly with LLVM:
-Throughout this manual, the following names are used to denote paths -specific to the local system and working environment. These are not -environment variables you need to set but just strings used in the rest -of this document below. In any of the examples below, simply replace -each of these names with the appropriate pathname on your local system. -All these paths are absolute:
+This is the top level directory of the LLVM source tree.
This is the top level directory of the LLVM object tree (i.e. the - tree where object files and compiled programs will be placed. It is - fixed at SRC_ROOT/win32).
The object files are placed under OBJ_ROOT/Debug for debug builds - and OBJ_ROOT/Release for release (optimized) builds. These include - both executables and libararies that your application can link against.
- -The files that configure would create when building on Unix are - created by the Configure project and placed in - OBJ_ROOT/llvm. You application must have OBJ_ROOT in its include - search path just before SRC_ROOT/include.
+Note: while you cannot do this step on Windows, you can do it on a - Unix system and transfer hello.bc to Windows. Important: - transfer as a binary file!
Note: you will need the llvm-gcc binaries from the + LLVM + download page
Run the program using the just-in-time compiler:
@@ -327,6 +257,15 @@ int main() {% llc -march=c hello.bc+ +
Note: you need to add the C backend to the LLVM build, + which amounts to setting the CMake + variable LLVM_TARGETS_TO_BUILD to "X86;CBackend" when + you generate the VS solution files. See + the LLVM CMake guide for more + information about how to configure the LLVM + build.
Compile to binary using Microsoft C:
@@ -360,17 +299,6 @@ int main() {If you are having problems building or using LLVM, or if you have any other general questions about LLVM, please consult the Frequently Asked Questions page.