<p>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 directly generate an
- executable file. You can do so indirectly by using the C back end.</p>
+ 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.</p>
<p>To emphasize, there is no C/C++ front end currently available.
<tt>llvm-gcc</tt> is based on GCC, which cannot be bootstrapped using VC++.
<li><tt>cd llvm</tt></li>
</ol></li>
- <li>With anonymous CVS access (or use a <a href="#mirror">mirror</a>):
+ <li>With anonymous CVS access:
<ol>
<li><tt>cd <i>where-you-want-llvm-to-live</i></tt></li>
<li><tt>cvs -d
<p>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.</p>
+ beta, there are no guarantees and there is no support for it at this time.
+ It has been reported that VC++ Express also works.</p>
- <p>You will also need several open source packages: bison, flex, and sed.
- These must be installed in <tt>llvm/win32/tools</tt>. These can be found at
- <a href="http://gnuwin32.sourceforge.net/">http://gnuwin32.sourceforge.net/
- </a>. 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 <tt>M4</tt>
- to point to <tt>m4</tt> executable.</p>
+ <p>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.</p>
</div>
<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>
- <li><p>Run the program. To make sure the program ran, execute the
- following command:</p>
+ <li><p>Run the program using the just-in-time compiler:</p>
<p><tt>% lli hello.bc</tt></p></li>
<li><p>Use the <tt>llvm-dis</tt> utility to take a look at the LLVM assembly
code:</p>
- <p><tt>% llvm-dis < hello.bc | less</tt><p></li>
+ <p><tt>% llvm-dis < hello.bc | more</tt><p></li>
- <li><p>Compile the program to native assembly using the LLC code
- generator:</p>
+ <li><p>Compile the program to C using the LLC code generator:</p>
- <p><tt>% llc hello.bc -o hello.s</tt></p>
+ <p><tt>% llc -march=c hello.bc</tt></p></li>
- <li><p>Assemble the native assembly language file into a program:</p>
+ <li><p>Compile to binary using Microsoft C:</p>
- <p><b>Not currently possible, but eventually will use <tt>NASMW</tt>.</b></p>
+ <p><tt>% cl hello.cbe.c</tt></p></li>
<li><p>Execute the native code program:</p>
- <p><tt>% ./hello.native</tt></p></li>
+ <p><tt>% hello.cbe.exe</tt></p></li>
</ol>
out:</p>
<ul>
- <li><a href="http://llvm.cs.uiuc.edu/">LLVM homepage</a></li>
- <li><a href="http://llvm.cs.uiuc.edu/doxygen/">LLVM doxygen tree</a></li>
- <li><a href="http://llvm.cs.uiuc.edu/docs/Projects.html">Starting a Project
+ <li><a href="http://llvm.org/">LLVM homepage</a></li>
+ <li><a href="http://llvm.org/doxygen/">LLVM doxygen tree</a></li>
+ <li><a href="http://llvm.org/docs/Projects.html">Starting a Project
that Uses LLVM</a></li>
</ul>
src="http://www.w3.org/Icons/valid-html401" alt="Valid HTML 4.01!" /></a>
<a href="mailto:jeffc@jolt-lang.org">Jeff Cohen</a><br>
- <a href="http://llvm.cs.uiuc.edu">The LLVM Compiler Infrastructure</a><br>
+ <a href="http://llvm.org">The LLVM Compiler Infrastructure</a><br>
Last modified: $Date$
</address>
</body>