compiled into LLVM bytecode, a program can be manipulated with the LLVM tools
from the LLVM suite.</p>
+<p>
+There is a third, optional piece called llvm-test. It is a suite of programs
+with a testing harness that can be used to further test LLVM's functionality
+and performance.
+</p>
+
</div>
<!-- *********************************************************************** -->
<dt>alias llvmgcc <i>LLVMGCCDIR</i><tt>/bin/gcc</tt>
<dt>alias llvmg++ <i>LLVMGCCDIR</i><tt>/bin/g++</tt>
<dd>
- This alias allows you to use the LLVM C and C++ front ends without putting
+ These aliases allow you to use the LLVM C and C++ front ends without putting
them in your <tt>PATH</tt> or typing in their complete pathnames.
</dl>
<dd>This is the source code for the LLVM libraries and tools.<br/></dd>
<dt><tt>llvm-test-1.4.tar.gz</tt></dt>
- <dd>This is the source code for the LLVM test suite</tt></dd>
+ <dd>This is the source code for the LLVM test suite.</tt></dd>
<dt><tt>cfrontend-1.4.source.tar.gz</tt></dt>
<dd>This is the source release of the GCC front end.<br/></dd>
</pre>
<p>Please note that you must follow <a href="CFEBuildInstrs.html">these
-instructions</a> to successfully build the LLVM C front-end.</p>
+instructions</a> to successfully build the LLVM GCC front-end.</p>
</div>
Path to the location where the LLVM GCC front end binaries and
associated libraries were installed. This must be specified as an
absolute pathname.
- <p>
+ <p></p>
</dd>
<dt><i>--with-tclinclude</i></dt>
<dd>Path to the tcl include directory under which the <tt>tclsh</tt> can be
want to use a specific one (8.x) for LLVM. LLVM only uses tcl for running the
dejagnu based test suite in <tt>llvm/test</tt>. If you don't specify this
option, the LLVM configure script will search for tcl 8.4 and 8.3 releases.
+ <p></p>
</dd>
<dt><i>--enable-optimized</i></dt>
<dd>
Enables optimized compilation by default (debugging symbols are removed
and GCC optimization flags are enabled). The default is to use an
unoptimized build (also known as a debug build).
- <p>
+ <p></p>
</dd>
<dt><i>--enable-jit</i></dt>
<dd>
available
on all platforms. The default is dependent on platform, so it is best
to explicitly enable it if you want it.
- <p>
+ <p></p>
</dd>
<dt><i>--enable-doxygen</i></dt>
<dd>Look for the doxygen program and enable construction of doxygen based
<p><tt>gmake</tt></p>
<p>If the build fails, please <a href="#brokengcc">check here</a> to see if you
-are using a known broken version of GCC to compile LLVM with.</p>
+are using a version of GCC that is known not to compile LLVM.</p>
<p>
If you have multiple processors in your machine, you may wish to use some of
<dt><tt>gmake install</tt>
<dd>
- Installs LLVM header files, libraries, tools and documentation in a hierarchy
+ Installs LLVM header files, libraries, tools, and documentation in a
+ hierarchy
under $PREFIX, specified with <tt>./configure --prefix=[dir]</tt>, which
defaults to <tt>/usr/local</tt>.
<p>
<dt><tt>gmake TOOL_VERBOSE=1</tt></dt>
<dd>Ask each tool invoked by the makefiles to print out what it is doing on
- the standard output. This also implies <tt>VERBOSE=1</tt> so the makefile
+ the standard output. This also implies <tt>VERBOSE=1</tt>.
<p></dd>
</dl>
<!-- ======================================================================= -->
<div class="doc_subsection"><a name="llvmtest"><tt>llvm-test</tt></a></div>
<div class="doc_text">
- <p>This is not a directory in the normal llvm module, it is a separate CVS
+ <p>This is not a directory in the normal llvm module; it is a separate CVS
module that must be checked out (usually to <tt>projects/llvm-test</tt>). This
- module contains a comprehensive correctness, performance and benchmarking test
+ module contains a comprehensive correctness, performance, and benchmarking
+ test
suite for LLVM. It is a separate CVS module because not every LLVM user is
interested in downloading or building such a comprehensive test. For further
details on this test suite, please see the
pre-processing, translation, optimization, assembly, and linking of programs
all from one command line. <tt>llvmc</tt> also takes care of processing the
dependent libraries found in bytecode. This reduces the need to get the
- traditional <tt>-l<name></tt> options right on the command line.</dd>
+ traditional <tt>-l<name></tt> options right on the command line. Please
+ note that this tool is new in 1.4 and considered experimental. It will be
+ fully supported in 1.5.</dd>
<dt><tt><b>llvm-ar</b></tt></dt>
<dd>The archiver produces an archive containing
<dd>The disassembler transforms the LLVM bytecode to human readable
LLVM assembly.</dd>
+ <dt><tt><b>llvm-ld</b></tt></dt>
+ <dd><tt>llvm-ld</tt> is very similar to gccld and provides a general purpose
+ and extensible linker for LLVM. This is the linker invoked by <tt>llvmc</tt>.
+ It allows optimization modules to be loaded so that language specific
+ optimizations can be applied at link time. Please note that this tool is new
+ in LLVM 1.4 and still considered experimental. It will be fully supported in
+ LLVM 1.5.</dd>
+
<dt><tt><b>llvm-link</b></tt></dt>
<dd><tt>llvm-link</tt>, not surprisingly, links multiple LLVM modules into
a single program.</dd>
can directly execute LLVM bytecode (although very slowly...). In addition
to a simple interpreter, <tt>lli</tt> also has a tracing mode (entered by
specifying <tt>-trace</tt> on the command line). Finally, for
- architectures that support it (currently only x86 and Sparc), by default,
+ architectures that support it (currently x86, Sparc, and PowerPC), by default,
<tt>lli</tt> will function as a Just-In-Time compiler (if the
functionality was compiled in), and will execute the code <i>much</i>
faster than the interpreter.</dd>
<div class="doc_text">
<p>This directory contains build scripts and project files for use with
Visual C++. This allows developers on Windows to build LLVM without the need
- for cygwin. The contents of this directory should be considered experimental
+ for Cygwin. The contents of this directory should be considered experimental
at this time.
</p>
</div>
projects / oota-llvm.git / blobdiff