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 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.
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 bytecode 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.
The LLVM test suite cannot be run on the Visual Studio port at this time.
Most of the tools build and work. llvm-db does not build at this time. bugpoint does build, but does not work.
Additional information about the LLVM directory structure and tool chain can be found on the main Getting Started page.
Here's the short story for getting up and running quickly with LLVM:
It is strongly encouraged that you get the latest version from CVS. Much progress has been made since the 1.4 release.
Before you begin to use the LLVM system, review the requirements given below. This may save you some trouble by knowing ahead of time what hardware and software you will need.
Any system that can adequately run Visual Studio .NET 2003 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 also need several open source packages: bison, flex, and sed. These must be installed in llvm/win32/tools. These can be found at http://gnuwin32.sourceforge.net or http://unxutils.sourceforge.net. Bison prefers that m4 be in the path. You must add it to the Visual Studio configuration under the menu Options -> Projects -> VC++ Directories. Alternatively, you can set the environment variable M4 to point to m4 executable.
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.
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:
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.
#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 -o hello
Note that you should have already built the tools and they have to be in your path, at least gccas and gccld.
This will create two result files: hello and hello.bc. The hello.bc is the LLVM bytecode that corresponds the the compiled program and the library facilities that it required. hello is a simple shell script that runs the bytecode file with lli, making the result directly executable. Note that all LLVM optimizations are enabled by default, so there is no need for a "-O3" switch.
Note: while you cannot do this step on Windows, you can do it on a Unix system and transfer hello.bc to Windows.
Run the program. To make sure the program ran, execute the following command:
% lli hello.bc
Use the llvm-dis utility to take a look at the LLVM assembly code:
% llvm-dis < hello.bc | less
Compile the program to native assembly using the LLC code generator:
% llc hello.bc -o hello.s
Assemble the native assembly language file into a program:
Not currently possible, but eventually will use NASMW.
Execute the native code program:
% ./hello.native
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.
This document is just an introduction to how to use LLVM to do some simple things... there are many more interesting and complicated things that you can do that aren't documented here (but we'll gladly accept a patch if you want to write something up!). For more information about LLVM, check out: