It is strongly encouraged that you get the latest version from CVS. Much -progress has been made since the 1.4 release.
+It is strongly encouraged that you get the latest version from Subversion as +changes are continually making the VS support better.
@@ -154,8 +178,8 @@ progress has been made since the 1.4 release.Any system that can adequately run Visual Studio .NET 2003 is fine. The - LLVM source tree and object files, libraries and executables will consume +
Any system that can adequately run Visual Studio .NET 2005 SP1 is fine. + The LLVM source tree and object files, libraries and executables will consume approximately 3GB.
You will need Visual Studio .NET 2003. Earlier versions cannot open the - solution/project files. The VS 2005 beta can, but will migrate these files - to its own format in the process. While it should work with the VS 2005 - beta, there are no guarantees and there is no support for it at this time. - It has been reported that VC++ Express also works.
+You will need Visual Studio .NET 2005 SP1 or higher. The VS2005 SP1 + beta and the normal VS2005 still have bugs that are not completely + compatible. VS2003 would work except (at last check) it has a bug with + friend classes that you can work-around with some minor code rewriting + (and please submit a patch if you do). Earlier versions of Visual Studio + do not support the C++ standard well enough and will not work.
+ +You will also need the CMake build + system since it generates the project files you will use to build with.
-If you plan to modify any .y or .l files, you will need to have bison - and/or flex installed where Visual Studio can find them. Otherwise, you do - not need them and the pre-generated files that come with the source tree - will be used.
++ Do not install the LLVM directory tree into a path containing spaces (e.g. + C:\Documents and Settings\...) as the configure step will fail.
-
-
- SRC_ROOT -
-
- This is the top level directory of the LLVM source tree.
-
- -
- OBJ_ROOT -
-
- 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).
-
+
- SRC_ROOT +
This is the top level directory of the LLVM source tree.
+
+ - OBJ_ROOT +
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. + 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. + search path just before SRC_ROOT/include.
@@ -248,48 +271,83 @@ All these paths are absolute:-
-
- First, create a simple C file, name it 'hello.c':
-
- #include <stdio.h> - int main() { - printf("hello world\n"); - return 0; - } -
-
- Next, compile the C file into a LLVM bytecode file:
-% llvm-gcc 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 - facilities that it required. You can execute this file directly using - lli tool, compile it to native assembly with the llc, - optimize or analyze it further with the opt tool, etc.
+First, create a simple C file, name it 'hello.c':
+ +++#include <stdio.h> +int main() { + printf("hello world\n"); + return 0; +} +
+
+ Next, compile the C file into a LLVM bitcode file:
+ +++ ++% llvm-gcc -c hello.c -emit-llvm -o hello.bc +
+This will create the result file hello.bc which is the LLVM + bitcode that corresponds the the compiled program and the library + facilities that it required. You can execute this file directly using + lli tool, compile it to native assembly with the llc, + 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
+Use the llvm-dis utility to take a look at the LLVM assembly code:
-% llvm-dis < hello.bc | more
+Compile the program to C using the LLC code generator:
-% llc -march=c hello.bc
+Compile to binary using Microsoft C:
-% cl hello.cbe.c
+Execute the native code program:
-% hello.cbe.exe
-
+
+% 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.
+% llvm-dis < hello.bc | more ++
+% llc -march=c hello.bc ++
+% 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.
+% hello.cbe.exe ++
-
+
- In Visual C++, if you are linking with the x86 target statically, the + linker will remove the x86 target library from your generated executable or + shared library because there are no references to it. You can force the + linker to include these references by using + "/INCLUDE:_X86TargetMachineModule" when linking. In the Visual + Studio IDE, this can be added in +Project Properties->Linker->Input->Force Symbol References. + +
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.
@@ -326,7 +395,7 @@ out:
+ src="http://jigsaw.w3.org/css-validator/images/vcss-blue" alt="Valid CSS">
The LLVM Compiler Infrastructure