[llvm-commits] [www-releases] r145591 - in /www-releases/trunk/3.0/docs/CommandGuide/html: FileCheck.html bugpoint.html lit.html llc.html lli.html llvm-ar.html llvm-as.html llvm-bcanalyzer.html llvm-config.html llvm-diff.html llvm-dis.html llvm-extract.html llvm-ld.html llvm-link.html llvm-nm.html llvm-prof.html llvm-ranlib.html opt.html tblgen.html
Tanya Lattner
tonic at nondot.org
Thu Dec 1 09:44:59 PST 2011
Author: tbrethou
Date: Thu Dec 1 11:44:59 2011
New Revision: 145591
URL: http://llvm.org/viewvc/llvm-project?rev=145591&view=rev
Log:
Add html versions of command guide
Added:
www-releases/trunk/3.0/docs/CommandGuide/html/FileCheck.html
www-releases/trunk/3.0/docs/CommandGuide/html/bugpoint.html
www-releases/trunk/3.0/docs/CommandGuide/html/lit.html
www-releases/trunk/3.0/docs/CommandGuide/html/llc.html
www-releases/trunk/3.0/docs/CommandGuide/html/lli.html
www-releases/trunk/3.0/docs/CommandGuide/html/llvm-ar.html
www-releases/trunk/3.0/docs/CommandGuide/html/llvm-as.html
www-releases/trunk/3.0/docs/CommandGuide/html/llvm-bcanalyzer.html
www-releases/trunk/3.0/docs/CommandGuide/html/llvm-config.html
www-releases/trunk/3.0/docs/CommandGuide/html/llvm-diff.html
www-releases/trunk/3.0/docs/CommandGuide/html/llvm-dis.html
www-releases/trunk/3.0/docs/CommandGuide/html/llvm-extract.html
www-releases/trunk/3.0/docs/CommandGuide/html/llvm-ld.html
www-releases/trunk/3.0/docs/CommandGuide/html/llvm-link.html
www-releases/trunk/3.0/docs/CommandGuide/html/llvm-nm.html
www-releases/trunk/3.0/docs/CommandGuide/html/llvm-prof.html
www-releases/trunk/3.0/docs/CommandGuide/html/llvm-ranlib.html
www-releases/trunk/3.0/docs/CommandGuide/html/opt.html
www-releases/trunk/3.0/docs/CommandGuide/html/tblgen.html
Added: www-releases/trunk/3.0/docs/CommandGuide/html/FileCheck.html
URL: http://llvm.org/viewvc/llvm-project/www-releases/trunk/3.0/docs/CommandGuide/html/FileCheck.html?rev=145591&view=auto
==============================================================================
--- www-releases/trunk/3.0/docs/CommandGuide/html/FileCheck.html (added)
+++ www-releases/trunk/3.0/docs/CommandGuide/html/FileCheck.html Thu Dec 1 11:44:59 2011
@@ -0,0 +1,276 @@
+<?xml version="1.0" ?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+<title>FileCheck</title>
+<link rel="stylesheet" href="manpage.css" type="text/css" />
+<meta http-equiv="content-type" content="text/html; charset=utf-8" />
+<link rev="made" href="mailto:root at localhost" />
+</head>
+
+<body>
+
+
+<!-- INDEX BEGIN -->
+<div name="index">
+<p><a name="__index__"></a></p>
+<!--
+
+<ul>
+
+ <li><a href="#name">NAME</a></li>
+ <li><a href="#synopsis">SYNOPSIS</a></li>
+ <li><a href="#description">DESCRIPTION</a></li>
+ <li><a href="#options">OPTIONS</a></li>
+ <li><a href="#exit_status">EXIT STATUS</a></li>
+ <li><a href="#tutorial">TUTORIAL</a></li>
+ <ul>
+
+ <li><a href="#the_filecheck__check_prefix_option">The FileCheck -check-prefix option</a></li>
+ <li><a href="#the_check_next__directive">The "CHECK-NEXT:" directive</a></li>
+ <li><a href="#the_check_not__directive">The "CHECK-NOT:" directive</a></li>
+ <li><a href="#filecheck_pattern_matching_syntax">FileCheck Pattern Matching Syntax</a></li>
+ <li><a href="#filecheck_variables">FileCheck Variables</a></li>
+ </ul>
+
+ <li><a href="#authors">AUTHORS</a></li>
+</ul>
+
+-->
+
+
+</div>
+<!-- INDEX END -->
+
+<p>
+</p>
+<hr />
+<h1><a name="name">NAME</a></h1>
+<p>FileCheck - Flexible pattern matching file verifier</p>
+<p>
+</p>
+<hr />
+<h1><a name="synopsis">SYNOPSIS</a></h1>
+<p><strong>FileCheck</strong> <em>match-filename</em> [<em>--check-prefix=XXX</em>] [<em>--strict-whitespace</em>]</p>
+<p>
+</p>
+<hr />
+<h1><a name="description">DESCRIPTION</a></h1>
+<p><strong>FileCheck</strong> reads two files (one from standard input, and one specified on the
+command line) and uses one to verify the other. This behavior is particularly
+useful for the testsuite, which wants to verify that the output of some tool
+(e.g. llc) contains the expected information (for example, a movsd from esp or
+whatever is interesting). This is similar to using grep, but it is optimized
+for matching multiple different inputs in one file in a specific order.</p>
+<p>The <em>match-filename</em> file specifies the file that contains the patterns to
+match. The file to verify is always read from standard input.</p>
+<p>
+</p>
+<hr />
+<h1><a name="options">OPTIONS</a></h1>
+<dl>
+<dt><strong><a name="help" class="item"><strong>-help</strong></a></strong></dt>
+
+<dd>
+<p>Print a summary of command line options.</p>
+</dd>
+<dt><strong><a name="check_prefix_prefix" class="item"><strong>--check-prefix</strong> <em>prefix</em></a></strong></dt>
+
+<dd>
+<p>FileCheck searches the contents of <em>match-filename</em> for patterns to match. By
+default, these patterns are prefixed with "CHECK:". If you'd like to use a
+different prefix (e.g. because the same input file is checking multiple
+different tool or options), the <strong>--check-prefix</strong> argument allows you to specify
+a specific prefix to match.</p>
+</dd>
+<dt><strong><a name="strict_whitespace" class="item"><strong>--strict-whitespace</strong></a></strong></dt>
+
+<dd>
+<p>By default, FileCheck canonicalizes input horizontal whitespace (spaces and
+tabs) which causes it to ignore these differences (a space will match a tab).
+The --strict-whitespace argument disables this behavior.</p>
+</dd>
+<dt><strong><a name="version" class="item"><strong>-version</strong></a></strong></dt>
+
+<dd>
+<p>Show the version number of this program.</p>
+</dd>
+</dl>
+<p>
+</p>
+<hr />
+<h1><a name="exit_status">EXIT STATUS</a></h1>
+<p>If <strong>FileCheck</strong> verifies that the file matches the expected contents, it exits
+with 0. Otherwise, if not, or if an error occurs, it will exit with a non-zero
+value.</p>
+<p>
+</p>
+<hr />
+<h1><a name="tutorial">TUTORIAL</a></h1>
+<p>FileCheck is typically used from LLVM regression tests, being invoked on the RUN
+line of the test. A simple example of using FileCheck from a RUN line looks
+like this:</p>
+<pre>
+ ; RUN: llvm-as < %s | llc -march=x86-64 | FileCheck %s</pre>
+<p>This syntax says to pipe the current file ("%s") into llvm-as, pipe that into
+llc, then pipe the output of llc into FileCheck. This means that FileCheck will
+be verifying its standard input (the llc output) against the filename argument
+specified (the original .ll file specified by "%s"). To see how this works,
+lets look at the rest of the .ll file (after the RUN line):</p>
+<pre>
+ define void @sub1(i32* %p, i32 %v) {
+ entry:
+ ; <b>CHECK: sub1:</b>
+ ; <b>CHECK: subl</b>
+ %0 = tail call i32 @llvm.atomic.load.sub.i32.p0i32(i32* %p, i32 %v)
+ ret void
+ }
+
+ define void @inc4(i64* %p) {
+ entry:
+ ; <b>CHECK: inc4:</b>
+ ; <b>CHECK: incq</b>
+ %0 = tail call i64 @llvm.atomic.load.add.i64.p0i64(i64* %p, i64 1)
+ ret void
+ }</pre>
+<p>Here you can see some "CHECK:" lines specified in comments. Now you can see
+how the file is piped into llvm-as, then llc, and the machine code output is
+what we are verifying. FileCheck checks the machine code output to verify that
+it matches what the "CHECK:" lines specify.</p>
+<p>The syntax of the CHECK: lines is very simple: they are fixed strings that
+must occur in order. FileCheck defaults to ignoring horizontal whitespace
+differences (e.g. a space is allowed to match a tab) but otherwise, the contents
+of the CHECK: line is required to match some thing in the test file exactly.</p>
+<p>One nice thing about FileCheck (compared to grep) is that it allows merging
+test cases together into logical groups. For example, because the test above
+is checking for the "sub1:" and "inc4:" labels, it will not match unless there
+is a "subl" in between those labels. If it existed somewhere else in the file,
+that would not count: "grep subl" matches if subl exists anywhere in the
+file.</p>
+<p>
+</p>
+<h2><a name="the_filecheck__check_prefix_option">The FileCheck -check-prefix option</a></h2>
+<p>The FileCheck -check-prefix option allows multiple test configurations to be
+driven from one .ll file. This is useful in many circumstances, for example,
+testing different architectural variants with llc. Here's a simple example:</p>
+<pre>
+ ; RUN: llvm-as < %s | llc -mtriple=i686-apple-darwin9 -mattr=sse41 \
+ ; RUN: | <b>FileCheck %s -check-prefix=X32</b>
+ ; RUN: llvm-as < %s | llc -mtriple=x86_64-apple-darwin9 -mattr=sse41 \
+ ; RUN: | <b>FileCheck %s -check-prefix=X64</b></pre>
+<pre>
+ define <4 x i32> @pinsrd_1(i32 %s, <4 x i32> %tmp) nounwind {
+ %tmp1 = insertelement <4 x i32>; %tmp, i32 %s, i32 1
+ ret <4 x i32> %tmp1
+ ; <b>X32:</b> pinsrd_1:
+ ; <b>X32:</b> pinsrd $1, 4(%esp), %xmm0
+
+ ; <b>X64:</b> pinsrd_1:
+ ; <b>X64:</b> pinsrd $1, %edi, %xmm0
+ }</pre>
+<p>In this case, we're testing that we get the expected code generation with
+both 32-bit and 64-bit code generation.</p>
+<p>
+</p>
+<h2><a name="the_check_next__directive">The "CHECK-NEXT:" directive</a></h2>
+<p>Sometimes you want to match lines and would like to verify that matches
+happen on exactly consecutive lines with no other lines in between them. In
+this case, you can use CHECK: and CHECK-NEXT: directives to specify this. If
+you specified a custom check prefix, just use "<PREFIX>-NEXT:". For
+example, something like this works as you'd expect:</p>
+<pre>
+ define void @t2(<2 x double>* %r, <2 x double>* %A, double %B) {
+ %tmp3 = load <2 x double>* %A, align 16
+ %tmp7 = insertelement <2 x double> undef, double %B, i32 0
+ %tmp9 = shufflevector <2 x double> %tmp3,
+ <2 x double> %tmp7,
+ <2 x i32> < i32 0, i32 2 >
+ store <2 x double> %tmp9, <2 x double>* %r, align 16
+ ret void
+
+ ; <b>CHECK:</b> t2:
+ ; <b>CHECK:</b> movl 8(%esp), %eax
+ ; <b>CHECK-NEXT:</b> movapd (%eax), %xmm0
+ ; <b>CHECK-NEXT:</b> movhpd 12(%esp), %xmm0
+ ; <b>CHECK-NEXT:</b> movl 4(%esp), %eax
+ ; <b>CHECK-NEXT:</b> movapd %xmm0, (%eax)
+ ; <b>CHECK-NEXT:</b> ret
+ }</pre>
+<p>CHECK-NEXT: directives reject the input unless there is exactly one newline
+between it an the previous directive. A CHECK-NEXT cannot be the first
+directive in a file.</p>
+<p>
+</p>
+<h2><a name="the_check_not__directive">The "CHECK-NOT:" directive</a></h2>
+<p>The CHECK-NOT: directive is used to verify that a string doesn't occur
+between two matches (or before the first match, or after the last match). For
+example, to verify that a load is removed by a transformation, a test like this
+can be used:</p>
+<pre>
+ define i8 @coerce_offset0(i32 %V, i32* %P) {
+ store i32 %V, i32* %P
+
+ %P2 = bitcast i32* %P to i8*
+ %P3 = getelementptr i8* %P2, i32 2</pre>
+<pre>
+ %A = load i8* %P3
+ ret i8 %A
+ ; <b>CHECK:</b> @coerce_offset0
+ ; <b>CHECK-NOT:</b> load
+ ; <b>CHECK:</b> ret i8
+ }</pre>
+<p>
+</p>
+<h2><a name="filecheck_pattern_matching_syntax">FileCheck Pattern Matching Syntax</a></h2>
+<p>The CHECK: and CHECK-NOT: directives both take a pattern to match. For most
+uses of FileCheck, fixed string matching is perfectly sufficient. For some
+things, a more flexible form of matching is desired. To support this, FileCheck
+allows you to specify regular expressions in matching strings, surrounded by
+double braces: <strong>{{yourregex}}</strong>. Because we want to use fixed string
+matching for a majority of what we do, FileCheck has been designed to support
+mixing and matching fixed string matching with regular expressions. This allows
+you to write things like this:</p>
+<pre>
+ ; CHECK: movhpd <b>{{[0-9]+}}</b>(%esp), <b>{{%xmm[0-7]}}</b></pre>
+<p>In this case, any offset from the ESP register will be allowed, and any xmm
+register will be allowed.</p>
+<p>Because regular expressions are enclosed with double braces, they are
+visually distinct, and you don't need to use escape characters within the double
+braces like you would in C. In the rare case that you want to match double
+braces explicitly from the input, you can use something ugly like
+<strong>{{[{][{]}}</strong> as your pattern.</p>
+<p>
+</p>
+<h2><a name="filecheck_variables">FileCheck Variables</a></h2>
+<p>It is often useful to match a pattern and then verify that it occurs again
+later in the file. For codegen tests, this can be useful to allow any register,
+but verify that that register is used consistently later. To do this, FileCheck
+allows named variables to be defined and substituted into patterns. Here is a
+simple example:</p>
+<pre>
+ ; CHECK: test5:
+ ; CHECK: notw <b>[[REGISTER:%[a-z]+]]</b>
+ ; CHECK: andw {{.*}}<b>[[REGISTER]]</b></pre>
+<p>The first check line matches a regex (<tt>%[a-z]+</tt>) and captures it into
+the variables "REGISTER". The second line verifies that whatever is in REGISTER
+occurs later in the file after an "andw". FileCheck variable references are
+always contained in <tt>[[ ]]</tt> pairs, are named, and their names can be
+formed with the regex "<tt>[a-zA-Z_][a-zA-Z0-9_]*</tt>". If a colon follows the
+name, then it is a definition of the variable, if not, it is a use.</p>
+<p>FileCheck variables can be defined multiple times, and uses always get the
+latest value. Note that variables are all read at the start of a "CHECK" line
+and are all defined at the end. This means that if you have something like
+"<tt>CHECK: [[XYZ:.*]]x[[XYZ]]<tt>" that the check line will read the previous
+value of the XYZ variable and define a new one after the match is performed. If
+you need to do something like this you can probably take advantage of the fact
+that FileCheck is not actually line-oriented when it matches, this allows you to
+define two separate CHECK lines that match on the same line.</p>
+<p>
+</p>
+<hr />
+<h1><a name="authors">AUTHORS</a></h1>
+<p>Maintained by The LLVM Team (<a href="http://llvm.org/">http://llvm.org/</a>).</p>
+
+</body>
+
+</html>
Added: www-releases/trunk/3.0/docs/CommandGuide/html/bugpoint.html
URL: http://llvm.org/viewvc/llvm-project/www-releases/trunk/3.0/docs/CommandGuide/html/bugpoint.html?rev=145591&view=auto
==============================================================================
--- www-releases/trunk/3.0/docs/CommandGuide/html/bugpoint.html (added)
+++ www-releases/trunk/3.0/docs/CommandGuide/html/bugpoint.html Thu Dec 1 11:44:59 2011
@@ -0,0 +1,246 @@
+<?xml version="1.0" ?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+<title>bugpoint</title>
+<link rel="stylesheet" href="manpage.css" type="text/css" />
+<meta http-equiv="content-type" content="text/html; charset=utf-8" />
+<link rev="made" href="mailto:root at localhost" />
+</head>
+
+<body>
+
+
+<!-- INDEX BEGIN -->
+<div name="index">
+<p><a name="__index__"></a></p>
+<!--
+
+<ul>
+
+ <li><a href="#name">NAME</a></li>
+ <li><a href="#synopsis">SYNOPSIS</a></li>
+ <li><a href="#description">DESCRIPTION</a></li>
+ <li><a href="#options">OPTIONS</a></li>
+ <li><a href="#exit_status">EXIT STATUS</a></li>
+ <li><a href="#see_also">SEE ALSO</a></li>
+ <li><a href="#author">AUTHOR</a></li>
+</ul>
+
+-->
+
+
+</div>
+<!-- INDEX END -->
+
+<p>
+</p>
+<hr />
+<h1><a name="name">NAME</a></h1>
+<p>bugpoint - automatic test case reduction tool</p>
+<p>
+</p>
+<hr />
+<h1><a name="synopsis">SYNOPSIS</a></h1>
+<p><strong>bugpoint</strong> [<em>options</em>] [<em>input LLVM ll/bc files</em>] [<em>LLVM passes</em>] <strong>--args</strong>
+<em>program arguments</em></p>
+<p>
+</p>
+<hr />
+<h1><a name="description">DESCRIPTION</a></h1>
+<p><strong>bugpoint</strong> narrows down the source of problems in LLVM tools and passes. It
+can be used to debug three types of failures: optimizer crashes, miscompilations
+by optimizers, or bad native code generation (including problems in the static
+and JIT compilers). It aims to reduce large test cases to small, useful ones.
+For more information on the design and inner workings of <strong>bugpoint</strong>, as well as
+advice for using bugpoint, see <em class="file">llvm/docs/Bugpoint.html</em> in the LLVM
+distribution.</p>
+<p>
+</p>
+<hr />
+<h1><a name="options">OPTIONS</a></h1>
+<dl>
+<dt><strong><a name="additional_so_library" class="item"><strong>--additional-so</strong> <em class="file">library</em></a></strong></dt>
+
+<dd>
+<p>Load the dynamic shared object <em class="file">library</em> into the test program whenever it is
+run. This is useful if you are debugging programs which depend on non-LLVM
+libraries (such as the X or curses libraries) to run.</p>
+</dd>
+<dt><strong><a name="append_exit_code_true_false" class="item"><strong>--append-exit-code</strong>=<em>{true,false}</em></a></strong></dt>
+
+<dd>
+<p>Append the test programs exit code to the output file so that a change in exit
+code is considered a test failure. Defaults to false.</p>
+</dd>
+<dt><strong><a name="args_program_args" class="item"><strong>--args</strong> <em>program args</em></a></strong></dt>
+
+<dd>
+<p>Pass all arguments specified after -args to the test program whenever it runs.
+Note that if any of the <em>program args</em> start with a '-', you should use:</p>
+<pre>
+ bugpoint [bugpoint args] --args -- [program args]</pre>
+<p>The "--" right after the <strong>--args</strong> option tells <strong>bugpoint</strong> to consider any
+options starting with <code>-</code> to be part of the <strong>--args</strong> option, not as options to
+<strong>bugpoint</strong> itself.</p>
+</dd>
+<dt><strong><a name="tool_args_tool_args" class="item"><strong>--tool-args</strong> <em>tool args</em></a></strong></dt>
+
+<dd>
+<p>Pass all arguments specified after --tool-args to the LLVM tool under test
+(<strong>llc</strong>, <strong>lli</strong>, etc.) whenever it runs. You should use this option in the
+following way:</p>
+<pre>
+ bugpoint [bugpoint args] --tool-args -- [tool args]</pre>
+<p>The "--" right after the <strong>--tool-args</strong> option tells <strong>bugpoint</strong> to consider any
+options starting with <code>-</code> to be part of the <strong>--tool-args</strong> option, not as
+options to <strong>bugpoint</strong> itself. (See <strong>--args</strong>, above.)</p>
+</dd>
+<dt><strong><a name="safe_tool_args_tool_args" class="item"><strong>--safe-tool-args</strong> <em>tool args</em></a></strong></dt>
+
+<dd>
+<p>Pass all arguments specified after <strong>--safe-tool-args</strong> to the "safe" execution
+tool.</p>
+</dd>
+<dt><strong><a name="gcc_tool_args_gcc_tool_args" class="item"><strong>--gcc-tool-args</strong> <em>gcc tool args</em></a></strong></dt>
+
+<dd>
+<p>Pass all arguments specified after <strong>--gcc-tool-args</strong> to the invocation of
+<strong>gcc</strong>.</p>
+</dd>
+<dt><strong><a name="opt_args_opt_args" class="item"><strong>--opt-args</strong> <em>opt args</em></a></strong></dt>
+
+<dd>
+<p>Pass all arguments specified after <strong>--opt-args</strong> to the invocation of <strong>opt</strong>.</p>
+</dd>
+<dt><strong><a name="disable_dce_simplifycfg" class="item"><strong>--disable-{dce,simplifycfg}</strong></a></strong></dt>
+
+<dd>
+<p>Do not run the specified passes to clean up and reduce the size of the test
+program. By default, <strong>bugpoint</strong> uses these passes internally when attempting to
+reduce test programs. If you're trying to find a bug in one of these passes,
+<strong>bugpoint</strong> may crash.</p>
+</dd>
+<dt><strong><a name="enable_valgrind" class="item"><strong>--enable-valgrind</strong></a></strong></dt>
+
+<dd>
+<p>Use valgrind to find faults in the optimization phase. This will allow
+bugpoint to find otherwise asymptomatic problems caused by memory
+mis-management.</p>
+</dd>
+<dt><strong><a name="find_bugs" class="item"><strong>-find-bugs</strong></a></strong></dt>
+
+<dd>
+<p>Continually randomize the specified passes and run them on the test program
+until a bug is found or the user kills <strong>bugpoint</strong>.</p>
+</dd>
+<dt><strong><a name="help" class="item"><strong>-help</strong></a></strong></dt>
+
+<dd>
+<p>Print a summary of command line options.</p>
+</dd>
+<dt><strong><a name="input_filename" class="item"><strong>--input</strong> <em class="file">filename</em></a></strong></dt>
+
+<dd>
+<p>Open <em class="file">filename</em> and redirect the standard input of the test program, whenever
+it runs, to come from that file.</p>
+</dd>
+<dt><strong><a name="load_plugin" class="item"><strong>--load</strong> <em class="file">plugin</em></a></strong></dt>
+
+<dd>
+<p>Load the dynamic object <em class="file">plugin</em> into <strong>bugpoint</strong> itself. This object should
+register new optimization passes. Once loaded, the object will add new command
+line options to enable various optimizations. To see the new complete list of
+optimizations, use the <strong>-help</strong> and <strong>--load</strong> options together; for example:</p>
+<pre>
+ bugpoint --load myNewPass.so -help</pre>
+</dd>
+<dt><strong><a name="mlimit_megabytes" class="item"><strong>--mlimit</strong> <em class="file">megabytes</em></a></strong></dt>
+
+<dd>
+<p>Specifies an upper limit on memory usage of the optimization and codegen. Set
+to zero to disable the limit.</p>
+</dd>
+<dt><strong><a name="output_filename" class="item"><strong>--output</strong> <em class="file">filename</em></a></strong></dt>
+
+<dd>
+<p>Whenever the test program produces output on its standard output stream, it
+should match the contents of <em class="file">filename</em> (the "reference output"). If you
+do not use this option, <strong>bugpoint</strong> will attempt to generate a reference output
+by compiling the program with the "safe" backend and running it.</p>
+</dd>
+<dt><strong><a name="profile_info_file_filename" class="item"><strong>--profile-info-file</strong> <em class="file">filename</em></a></strong></dt>
+
+<dd>
+<p>Profile file loaded by <strong>--profile-loader</strong>.</p>
+</dd>
+<dt><strong><a name="run_int_jit_llc_cbe_custom" class="item"><strong>--run-{int,jit,llc,cbe,custom}</strong></a></strong></dt>
+
+<dd>
+<p>Whenever the test program is compiled, <strong>bugpoint</strong> should generate code for it
+using the specified code generator. These options allow you to choose the
+interpreter, the JIT compiler, the static native code compiler, the C
+backend, or a custom command (see <strong>--exec-command</strong>) respectively.</p>
+</dd>
+<dt><strong><a name="safe_llc_cbe_custom" class="item"><strong>--safe-{llc,cbe,custom}</strong></a></strong></dt>
+
+<dd>
+<p>When debugging a code generator, <strong>bugpoint</strong> should use the specified code
+generator as the "safe" code generator. This is a known-good code generator
+used to generate the "reference output" if it has not been provided, and to
+compile portions of the program that as they are excluded from the testcase.
+These options allow you to choose the
+static native code compiler, the C backend, or a custom command,
+(see <strong>--exec-command</strong>) respectively. The interpreter and the JIT backends
+cannot currently be used as the "safe" backends.</p>
+</dd>
+<dt><strong><a name="exec_command_command" class="item"><strong>--exec-command</strong> <em>command</em></a></strong></dt>
+
+<dd>
+<p>This option defines the command to use with the <strong>--run-custom</strong> and
+<strong>--safe-custom</strong> options to execute the bitcode testcase. This can
+be useful for cross-compilation.</p>
+</dd>
+<dt><strong><a name="compile_command_command" class="item"><strong>--compile-command</strong> <em>command</em></a></strong></dt>
+
+<dd>
+<p>This option defines the command to use with the <strong>--compile-custom</strong>
+option to compile the bitcode testcase. This can be useful for
+testing compiler output without running any link or execute stages. To
+generate a reduced unit test, you may add CHECK directives to the
+testcase and pass the name of an executable compile-command script in this form:</p>
+<pre>
+ #!/bin/sh
+ llc "$@"
+ not FileCheck [bugpoint input file].ll < bugpoint-test-program.s</pre>
+<p>This script will "fail" as long as FileCheck passes. So the result
+will be the minimum bitcode that passes FileCheck.</p>
+</dd>
+<dt><strong><a name="safe_path_path" class="item"><strong>--safe-path</strong> <em>path</em></a></strong></dt>
+
+<dd>
+<p>This option defines the path to the command to execute with the
+<strong>--safe-{int,jit,llc,cbe,custom}</strong>
+option.</p>
+</dd>
+</dl>
+<p>
+</p>
+<hr />
+<h1><a name="exit_status">EXIT STATUS</a></h1>
+<p>If <strong>bugpoint</strong> succeeds in finding a problem, it will exit with 0. Otherwise,
+if an error occurs, it will exit with a non-zero value.</p>
+<p>
+</p>
+<hr />
+<h1><a name="see_also">SEE ALSO</a></h1>
+<p><a href="././opt.html">opt</a></p>
+<p>
+</p>
+<hr />
+<h1><a name="author">AUTHOR</a></h1>
+<p>Maintained by the LLVM Team (<a href="http://llvm.org/">http://llvm.org/</a>).</p>
+
+</body>
+
+</html>
Added: www-releases/trunk/3.0/docs/CommandGuide/html/lit.html
URL: http://llvm.org/viewvc/llvm-project/www-releases/trunk/3.0/docs/CommandGuide/html/lit.html?rev=145591&view=auto
==============================================================================
--- www-releases/trunk/3.0/docs/CommandGuide/html/lit.html (added)
+++ www-releases/trunk/3.0/docs/CommandGuide/html/lit.html Thu Dec 1 11:44:59 2011
@@ -0,0 +1,411 @@
+<?xml version="1.0" ?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+<title>lit</title>
+<link rel="stylesheet" href="manpage.css" type="text/css" />
+<meta http-equiv="content-type" content="text/html; charset=utf-8" />
+<link rev="made" href="mailto:root at localhost" />
+</head>
+
+<body>
+
+
+<!-- INDEX BEGIN -->
+<div name="index">
+<p><a name="__index__"></a></p>
+<!--
+
+<ul>
+
+ <li><a href="#name">NAME</a></li>
+ <li><a href="#synopsis">SYNOPSIS</a></li>
+ <li><a href="#description">DESCRIPTION</a></li>
+ <li><a href="#general_options">GENERAL OPTIONS</a></li>
+ <li><a href="#output_options">OUTPUT OPTIONS</a></li>
+ <li><a href="#execution_options">EXECUTION OPTIONS</a></li>
+ <li><a href="#selection_options">SELECTION OPTIONS</a></li>
+ <li><a href="#additional_options">ADDITIONAL OPTIONS</a></li>
+ <li><a href="#exit_status">EXIT STATUS</a></li>
+ <li><a href="#test_discovery">TEST DISCOVERY</a></li>
+ <li><a href="#test_status_results">TEST STATUS RESULTS</a></li>
+ <li><a href="#lit_infrastructure">LIT INFRASTRUCTURE</a></li>
+ <ul>
+
+ <li><a href="#test_suites">TEST SUITES</a></li>
+ <li><a href="#test_discovery">TEST DISCOVERY</a></li>
+ <li><a href="#local_configuration_files">LOCAL CONFIGURATION FILES</a></li>
+ <li><a href="#lit_example_tests">LIT EXAMPLE TESTS</a></li>
+ </ul>
+
+ <li><a href="#see_also">SEE ALSO</a></li>
+ <li><a href="#author">AUTHOR</a></li>
+</ul>
+
+-->
+
+
+</div>
+<!-- INDEX END -->
+
+<p>
+</p>
+<hr />
+<h1><a name="name">NAME</a></h1>
+<p>lit - LLVM Integrated Tester</p>
+<p>
+</p>
+<hr />
+<h1><a name="synopsis">SYNOPSIS</a></h1>
+<p><strong>lit</strong> [<em>options</em>] [<em>tests</em>]</p>
+<p>
+</p>
+<hr />
+<h1><a name="description">DESCRIPTION</a></h1>
+<p><strong>lit</strong> is a portable tool for executing LLVM and Clang style test suites,
+summarizing their results, and providing indication of failures. <strong>lit</strong> is
+designed to be a lightweight testing tool with as simple a user interface as
+possible.</p>
+<p><strong>lit</strong> should be run with one or more <em>tests</em> to run specified on the command
+line. Tests can be either individual test files or directories to search for
+tests (see <a href="#test_discovery">TEST DISCOVERY</a>).</p>
+<p>Each specified test will be executed (potentially in parallel) and once all
+tests have been run <strong>lit</strong> will print summary information on the number of tests
+which passed or failed (see <a href="#test_status_results">TEST STATUS RESULTS</a>). The <strong>lit</strong> program will
+execute with a non-zero exit code if any tests fail.</p>
+<p>By default <strong>lit</strong> will use a succinct progress display and will only print
+summary information for test failures. See <a href="#output_options">OUTPUT OPTIONS</a> for options
+controlling the <strong>lit</strong> progress display and output.</p>
+<p><strong>lit</strong> also includes a number of options for controlling how tests are exected
+(specific features may depend on the particular test format). See <a href="#execution_options">EXECUTION OPTIONS</a> for more information.</p>
+<p>Finally, <strong>lit</strong> also supports additional options for only running a subset of
+the options specified on the command line, see <a href="#selection_options">SELECTION OPTIONS</a> for
+more information.</p>
+<p>Users interested in the <strong>lit</strong> architecture or designing a <strong>lit</strong> testing
+implementation should see <a href="#lit_architecture">LIT ARCHITECTURE</a></p>
+<p>
+</p>
+<hr />
+<h1><a name="general_options">GENERAL OPTIONS</a></h1>
+<dl>
+<dt><strong><a name="h_help" class="item"><strong>-h</strong>, <strong>--help</strong></a></strong></dt>
+
+<dd>
+<p>Show the <strong>lit</strong> help message.</p>
+</dd>
+<dt><strong><a name="j_n_threads_n" class="item"><strong>-j</strong> <em>N</em>, <strong>--threads</strong>=<em>N</em></a></strong></dt>
+
+<dd>
+<p>Run <em>N</em> tests in parallel. By default, this is automatically chosen to match
+the number of detected available CPUs.</p>
+</dd>
+<dt><strong><a name="config_prefix_name" class="item"><strong>--config-prefix</strong>=<em>NAME</em></a></strong></dt>
+
+<dd>
+<p>Search for <em>NAME.cfg</em> and <em>NAME.site.cfg</em> when searching for test suites,
+instead of <em>lit.cfg</em> and <em>lit.site.cfg</em>.</p>
+</dd>
+<dt><strong><a name="param_name_param_name_value" class="item"><strong>--param</strong> <em>NAME</em>, <strong>--param</strong> <em>NAME</em>=<em>VALUE</em></a></strong></dt>
+
+<dd>
+<p>Add a user defined parameter <em>NAME</em> with the given <em>VALUE</em> (or the empty
+string if not given). The meaning and use of these parameters is test suite
+dependent.</p>
+</dd>
+</dl>
+<p>
+</p>
+<hr />
+<h1><a name="output_options">OUTPUT OPTIONS</a></h1>
+<dl>
+<dt><strong><a name="q_quiet" class="item"><strong>-q</strong>, <strong>--quiet</strong></a></strong></dt>
+
+<dd>
+<p>Suppress any output except for test failures.</p>
+</dd>
+<dt><strong><a name="s_succinct" class="item"><strong>-s</strong>, <strong>--succinct</strong></a></strong></dt>
+
+<dd>
+<p>Show less output, for example don't show information on tests that pass.</p>
+</dd>
+<dt><strong><a name="v_verbose" class="item"><strong>-v</strong>, <strong>--verbose</strong></a></strong></dt>
+
+<dd>
+<p>Show more information on test failures, for example the entire test output
+instead of just the test result.</p>
+</dd>
+<dt><strong><a name="no_progress_bar" class="item"><strong>--no-progress-bar</strong></a></strong></dt>
+
+<dd>
+<p>Do not use curses based progress bar.</p>
+</dd>
+</dl>
+<p>
+</p>
+<hr />
+<h1><a name="execution_options">EXECUTION OPTIONS</a></h1>
+<dl>
+<dt><strong><a name="path_path" class="item"><strong>--path</strong>=<em>PATH</em></a></strong></dt>
+
+<dd>
+<p>Specify an addition <em>PATH</em> to use when searching for executables in tests.</p>
+</dd>
+<dt><strong><a name="vg" class="item"><strong>--vg</strong></a></strong></dt>
+
+<dd>
+<p>Run individual tests under valgrind (using the memcheck tool). The
+<em>--error-exitcode</em> argument for valgrind is used so that valgrind failures will
+cause the program to exit with a non-zero status.</p>
+</dd>
+<dt><strong><a name="vg_arg_arg" class="item"><strong>--vg-arg</strong>=<em>ARG</em></a></strong></dt>
+
+<dd>
+<p>When <em>--vg</em> is used, specify an additional argument to pass to valgrind itself.</p>
+</dd>
+<dt><strong><a name="time_tests" class="item"><strong>--time-tests</strong></a></strong></dt>
+
+<dd>
+<p>Track the wall time individual tests take to execute and includes the results in
+the summary output. This is useful for determining which tests in a test suite
+take the most time to execute. Note that this option is most useful with <em>-j
+1</em>.</p>
+</dd>
+</dl>
+<p>
+</p>
+<hr />
+<h1><a name="selection_options">SELECTION OPTIONS</a></h1>
+<dl>
+<dt><strong><a name="max_tests_n" class="item"><strong>--max-tests</strong>=<em>N</em></a></strong></dt>
+
+<dd>
+<p>Run at most <em>N</em> tests and then terminate.</p>
+</dd>
+<dt><strong><a name="max_time_n" class="item"><strong>--max-time</strong>=<em>N</em></a></strong></dt>
+
+<dd>
+<p>Spend at most <em>N</em> seconds (approximately) running tests and then terminate.</p>
+</dd>
+<dt><strong><a name="shuffle" class="item"><strong>--shuffle</strong></a></strong></dt>
+
+<dd>
+<p>Run the tests in a random order.</p>
+</dd>
+</dl>
+<p>
+</p>
+<hr />
+<h1><a name="additional_options">ADDITIONAL OPTIONS</a></h1>
+<dl>
+<dt><strong><a name="debug" class="item"><strong>--debug</strong></a></strong></dt>
+
+<dd>
+<p>Run <strong>lit</strong> in debug mode, for debugging configuration issues and <strong>lit</strong> itself.</p>
+</dd>
+<dt><strong><a name="show_suites" class="item"><strong>--show-suites</strong></a></strong></dt>
+
+<dd>
+<p>List the discovered test suites as part of the standard output.</p>
+</dd>
+<dt><strong><a name="no_tcl_as_sh" class="item"><strong>--no-tcl-as-sh</strong></a></strong></dt>
+
+<dd>
+<p>Run Tcl scripts internally (instead of converting to shell scripts).</p>
+</dd>
+<dt><strong><a name="repeat_n" class="item"><strong>--repeat</strong>=<em>N</em></a></strong></dt>
+
+<dd>
+<p>Run each test <em>N</em> times. Currently this is primarily useful for timing tests,
+other results are not collated in any reasonable fashion.</p>
+</dd>
+</dl>
+<p>
+</p>
+<hr />
+<h1><a name="exit_status">EXIT STATUS</a></h1>
+<p><strong>lit</strong> will exit with an exit code of 1 if there are any FAIL or XPASS
+results. Otherwise, it will exit with the status 0. Other exit codes used for
+non-test related failures (for example a user error or an internal program
+error).</p>
+<p>
+</p>
+<hr />
+<h1><a name="test_discovery">TEST DISCOVERY</a></h1>
+<p>The inputs passed to <strong>lit</strong> can be either individual tests, or entire
+directories or hierarchies of tests to run. When <strong>lit</strong> starts up, the first
+thing it does is convert the inputs into a complete list of tests to run as part
+of <em>test discovery</em>.</p>
+<p>In the <strong>lit</strong> model, every test must exist inside some <em>test suite</em>. <strong>lit</strong>
+resolves the inputs specified on the command line to test suites by searching
+upwards from the input path until it finds a <em>lit.cfg</em> or <em>lit.site.cfg</em>
+file. These files serve as both a marker of test suites and as configuration
+files which <strong>lit</strong> loads in order to understand how to find and run the tests
+inside the test suite.</p>
+<p>Once <strong>lit</strong> has mapped the inputs into test suites it traverses the list of
+inputs adding tests for individual files and recursively searching for tests in
+directories.</p>
+<p>This behavior makes it easy to specify a subset of tests to run, while still
+allowing the test suite configuration to control exactly how tests are
+interpreted. In addition, <strong>lit</strong> always identifies tests by the test suite they
+are in, and their relative path inside the test suite. For appropriately
+configured projects, this allows <strong>lit</strong> to provide convenient and flexible
+support for out-of-tree builds.</p>
+<p>
+</p>
+<hr />
+<h1><a name="test_status_results">TEST STATUS RESULTS</a></h1>
+<p>Each test ultimately produces one of the following six results:</p>
+<dl>
+<dt><strong><a name="pass" class="item"><strong>PASS</strong></a></strong></dt>
+
+<dd>
+<p>The test succeeded.</p>
+</dd>
+<dt><strong><a name="xfail" class="item"><strong>XFAIL</strong></a></strong></dt>
+
+<dd>
+<p>The test failed, but that is expected. This is used for test formats which allow
+specifying that a test does not currently work, but wish to leave it in the test
+suite.</p>
+</dd>
+<dt><strong><a name="xpass" class="item"><strong>XPASS</strong></a></strong></dt>
+
+<dd>
+<p>The test succeeded, but it was expected to fail. This is used for tests which
+were specified as expected to fail, but are now succeeding (generally because
+the feautre they test was broken and has been fixed).</p>
+</dd>
+<dt><strong><a name="fail" class="item"><strong>FAIL</strong></a></strong></dt>
+
+<dd>
+<p>The test failed.</p>
+</dd>
+<dt><strong><a name="unresolved" class="item"><strong>UNRESOLVED</strong></a></strong></dt>
+
+<dd>
+<p>The test result could not be determined. For example, this occurs when the test
+could not be run, the test itself is invalid, or the test was interrupted.</p>
+</dd>
+<dt><strong><a name="unsupported" class="item"><strong>UNSUPPORTED</strong></a></strong></dt>
+
+<dd>
+<p>The test is not supported in this environment. This is used by test formats
+which can report unsupported tests.</p>
+</dd>
+</dl>
+<p>Depending on the test format tests may produce additional information about
+their status (generally only for failures). See the <a href="#lit_output">Output</a>
+section for more information.</p>
+<p>
+</p>
+<hr />
+<h1><a name="lit_infrastructure">LIT INFRASTRUCTURE</a></h1>
+<p>This section describes the <strong>lit</strong> testing architecture for users interested in
+creating a new <strong>lit</strong> testing implementation, or extending an existing one.</p>
+<p><strong>lit</strong> proper is primarily an infrastructure for discovering and running
+arbitrary tests, and to expose a single convenient interface to these
+tests. <strong>lit</strong> itself doesn't know how to run tests, rather this logic is
+defined by <em>test suites</em>.</p>
+<p>
+</p>
+<h2><a name="test_suites">TEST SUITES</a></h2>
+<p>As described in <a href="#test_discovery">TEST DISCOVERY</a>, tests are always located inside a <em>test
+suite</em>. Test suites serve to define the format of the tests they contain, the
+logic for finding those tests, and any additional information to run the tests.</p>
+<p><strong>lit</strong> identifies test suites as directories containing <em>lit.cfg</em> or
+<em>lit.site.cfg</em> files (see also <strong>--config-prefix</strong>. Test suites are initially
+discovered by recursively searching up the directory hierarchy for all the input
+files passed on the command line. You can use <strong>--show-suites</strong> to display the
+discovered test suites at startup.</p>
+<p>Once a test suite is discovered, its config file is loaded. Config files
+themselves are Python modules which will be executed. When the config file is
+executed, two important global variables are predefined:</p>
+<dl>
+<dt><strong><a name="lit" class="item"><strong>lit</strong></a></strong></dt>
+
+<dd>
+<p>The global <strong>lit</strong> configuration object (a <em>LitConfig</em> instance), which defines
+the builtin test formats, global configuration parameters, and other helper
+routines for implementing test configurations.</p>
+</dd>
+<dt><strong><a name="config" class="item"><strong>config</strong></a></strong></dt>
+
+<dd>
+<p>This is the config object (a <em>TestingConfig</em> instance) for the test suite,
+which the config file is expected to populate. The following variables are also
+available on the <em>config</em> object, some of which must be set by the config and
+others are optional or predefined:</p>
+<p><strong>name</strong> <em>[required]</em> The name of the test suite, for use in reports and
+diagnostics.</p>
+<p><strong>test_format</strong> <em>[required]</em> The test format object which will be used to
+discover and run tests in the test suite. Generally this will be a builtin test
+format available from the <em>lit.formats</em> module.</p>
+<p><strong>test_src_root</strong> The filesystem path to the test suite root. For out-of-dir
+builds this is the directory that will be scanned for tests.</p>
+<p><strong>test_exec_root</strong> For out-of-dir builds, the path to the test suite root inside
+the object directory. This is where tests will be run and temporary output files
+places.</p>
+<p><strong>environment</strong> A dictionary representing the environment to use when executing
+tests in the suite.</p>
+<p><strong>suffixes</strong> For <strong>lit</strong> test formats which scan directories for tests, this
+variable as a list of suffixes to identify test files. Used by: <em>ShTest</em>,
+<em>TclTest</em>.</p>
+<p><strong>substitutions</strong> For <strong>lit</strong> test formats which substitute variables into a test
+script, the list of substitutions to perform. Used by: <em>ShTest</em>, <em>TclTest</em>.</p>
+<p><strong>unsupported</strong> Mark an unsupported directory, all tests within it will be
+reported as unsupported. Used by: <em>ShTest</em>, <em>TclTest</em>.</p>
+<p><strong>parent</strong> The parent configuration, this is the config object for the directory
+containing the test suite, or None.</p>
+<p><strong>on_clone</strong> The config is actually cloned for every subdirectory inside a test
+suite, to allow local configuration on a per-directory basis. The <em>on_clone</em>
+variable can be set to a Python function which will be called whenever a
+configuration is cloned (for a subdirectory). The function should takes three
+arguments: (1) the parent configuration, (2) the new configuration (which the
+<em>on_clone</em> function will generally modify), and (3) the test path to the new
+directory being scanned.</p>
+</dd>
+</dl>
+<p>
+</p>
+<h2><a name="test_discovery">TEST DISCOVERY</a></h2>
+<p>Once test suites are located, <strong>lit</strong> recursively traverses the source directory
+(following <em>test_src_root</em>) looking for tests. When <strong>lit</strong> enters a
+sub-directory, it first checks to see if a nest test suite is defined in that
+directory. If so, it loads that test suite recursively, otherwise it
+instantiates a local test config for the directory (see <a href="#local_configuration_files">LOCAL CONFIGURATION FILES</a>).</p>
+<p>Tests are identified by the test suite they are contained within, and the
+relative path inside that suite. Note that the relative path may not refer to an
+actual file on disk; some test formats (such as <em>GoogleTest</em>) define "virtual
+tests" which have a path that contains both the path to the actual test file and
+a subpath to identify the virtual test.</p>
+<p>
+</p>
+<h2><a name="local_configuration_files">LOCAL CONFIGURATION FILES</a></h2>
+<p>When <strong>lit</strong> loads a subdirectory in a test suite, it instantiates a local test
+configuration by cloning the configuration for the parent direction -- the root
+of this configuration chain will always be a test suite. Once the test
+configuration is cloned <strong>lit</strong> checks for a <em>lit.local.cfg</em> file in the
+subdirectory. If present, this file will be loaded and can be used to specialize
+the configuration for each individual directory. This facility can be used to
+define subdirectories of optional tests, or to change other configuration
+parameters -- for example, to change the test format, or the suffixes which
+identify test files.</p>
+<p>
+</p>
+<h2><a name="lit_example_tests">LIT EXAMPLE TESTS</a></h2>
+<p>The <strong>lit</strong> distribution contains several example implementations of test suites
+in the <em>ExampleTests</em> directory.</p>
+<p>
+</p>
+<hr />
+<h1><a name="see_also">SEE ALSO</a></h1>
+<p><em>valgrind(1)</em></p>
+<p>
+</p>
+<hr />
+<h1><a name="author">AUTHOR</a></h1>
+<p>Written by Daniel Dunbar and maintained by the LLVM Team (<a href="http://llvm.org/">http://llvm.org/</a>).</p>
+
+</body>
+
+</html>
Added: www-releases/trunk/3.0/docs/CommandGuide/html/llc.html
URL: http://llvm.org/viewvc/llvm-project/www-releases/trunk/3.0/docs/CommandGuide/html/llc.html?rev=145591&view=auto
==============================================================================
--- www-releases/trunk/3.0/docs/CommandGuide/html/llc.html (added)
+++ www-releases/trunk/3.0/docs/CommandGuide/html/llc.html Thu Dec 1 11:44:59 2011
@@ -0,0 +1,265 @@
+<?xml version="1.0" ?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+<title>llc</title>
+<link rel="stylesheet" href="manpage.css" type="text/css" />
+<meta http-equiv="content-type" content="text/html; charset=utf-8" />
+<link rev="made" href="mailto:root at localhost" />
+</head>
+
+<body>
+
+
+<!-- INDEX BEGIN -->
+<div name="index">
+<p><a name="__index__"></a></p>
+<!--
+
+<ul>
+
+ <li><a href="#name">NAME</a></li>
+ <li><a href="#synopsis">SYNOPSIS</a></li>
+ <li><a href="#description">DESCRIPTION</a></li>
+ <li><a href="#options">OPTIONS</a></li>
+ <ul>
+
+ <li><a href="#end_user_options">End-user Options</a></li>
+ <li><a href="#tuning_configuration_options">Tuning/Configuration Options</a></li>
+ <li><a href="#intel_ia_32_specific_options">Intel IA-32-specific Options</a></li>
+ </ul>
+
+ <li><a href="#exit_status">EXIT STATUS</a></li>
+ <li><a href="#see_also">SEE ALSO</a></li>
+ <li><a href="#authors">AUTHORS</a></li>
+</ul>
+
+-->
+
+
+</div>
+<!-- INDEX END -->
+
+<p>
+</p>
+<hr />
+<h1><a name="name">NAME</a></h1>
+<p>llc - LLVM static compiler</p>
+<p>
+</p>
+<hr />
+<h1><a name="synopsis">SYNOPSIS</a></h1>
+<p><strong>llc</strong> [<em>options</em>] [<em>filename</em>]</p>
+<p>
+</p>
+<hr />
+<h1><a name="description">DESCRIPTION</a></h1>
+<p>The <strong>llc</strong> command compiles LLVM source inputs into assembly language for a
+specified architecture. The assembly language output can then be passed through
+a native assembler and linker to generate a native executable.</p>
+<p>The choice of architecture for the output assembly code is automatically
+determined from the input file, unless the <strong>-march</strong> option is used to override
+the default.</p>
+<p>
+</p>
+<hr />
+<h1><a name="options">OPTIONS</a></h1>
+<p>If <em>filename</em> is - or omitted, <strong>llc</strong> reads from standard input. Otherwise, it
+will from <em>filename</em>. Inputs can be in either the LLVM assembly language
+format (.ll) or the LLVM bitcode format (.bc).</p>
+<p>If the <strong>-o</strong> option is omitted, then <strong>llc</strong> will send its output to standard
+output if the input is from standard input. If the <strong>-o</strong> option specifies -,
+then the output will also be sent to standard output.</p>
+<p>If no <strong>-o</strong> option is specified and an input file other than - is specified,
+then <strong>llc</strong> creates the output filename by taking the input filename,
+removing any existing <em class="file">.bc</em> extension, and adding a <em class="file">.s</em> suffix.</p>
+<p>Other <strong>llc</strong> options are as follows:</p>
+<p>
+</p>
+<h2><a name="end_user_options">End-user Options</a></h2>
+<dl>
+<dt><strong><a name="help" class="item"><strong>-help</strong></a></strong></dt>
+
+<dd>
+<p>Print a summary of command line options.</p>
+</dd>
+<dt><strong><a name="o_uint" class="item"><strong>-O</strong>=<em>uint</em></a></strong></dt>
+
+<dd>
+<p>Generate code at different optimization levels. These correspond to the <em>-O0</em>,
+<em>-O1</em>, <em>-O2</em>, <em>-O3</em>, and <em>-O4</em> optimization levels used by <strong>llvm-gcc</strong> and
+<strong>clang</strong>.</p>
+</dd>
+<dt><strong><a name="mtriple_target_triple" class="item"><strong>-mtriple</strong>=<em>target triple</em></a></strong></dt>
+
+<dd>
+<p>Override the target triple specified in the input file with the specified
+string.</p>
+</dd>
+<dt><strong><a name="march_arch" class="item"><strong>-march</strong>=<em>arch</em></a></strong></dt>
+
+<dd>
+<p>Specify the architecture for which to generate assembly, overriding the target
+encoded in the input file. See the output of <strong>llc -help</strong> for a list of
+valid architectures. By default this is inferred from the target triple or
+autodetected to the current architecture.</p>
+</dd>
+<dt><strong><a name="mcpu_cpuname" class="item"><strong>-mcpu</strong>=<em>cpuname</em></a></strong></dt>
+
+<dd>
+<p>Specify a specific chip in the current architecture to generate code for.
+By default this is inferred from the target triple and autodetected to
+the current architecture. For a list of available CPUs, use:
+<strong>llvm-as < /dev/null | llc -march=xyz -mcpu=help</strong></p>
+</dd>
+<dt><strong><a name="mattr_a1_a2_a3" class="item"><strong>-mattr</strong>=<em>a1,+a2,-a3,...</em></a></strong></dt>
+
+<dd>
+<p>Override or control specific attributes of the target, such as whether SIMD
+operations are enabled or not. The default set of attributes is set by the
+current CPU. For a list of available attributes, use:
+<strong>llvm-as < /dev/null | llc -march=xyz -mattr=help</strong></p>
+</dd>
+<dt><strong><a name="disable_fp_elim" class="item"><strong>--disable-fp-elim</strong></a></strong></dt>
+
+<dd>
+<p>Disable frame pointer elimination optimization.</p>
+</dd>
+<dt><strong><a name="disable_excess_fp_precision" class="item"><strong>--disable-excess-fp-precision</strong></a></strong></dt>
+
+<dd>
+<p>Disable optimizations that may produce excess precision for floating point.
+Note that this option can dramatically slow down code on some systems
+(e.g. X86).</p>
+</dd>
+<dt><strong><a name="enable_no_infs_fp_math" class="item"><strong>--enable-no-infs-fp-math</strong></a></strong></dt>
+
+<dd>
+<p>Enable optimizations that assume no Inf values.</p>
+</dd>
+<dt><strong><a name="enable_no_nans_fp_math" class="item"><strong>--enable-no-nans-fp-math</strong></a></strong></dt>
+
+<dd>
+<p>Enable optimizations that assume no NAN values.</p>
+</dd>
+<dt><strong><a name="enable_unsafe_fp_math" class="item"><strong>--enable-unsafe-fp-math</strong></a></strong></dt>
+
+<dd>
+<p>Enable optimizations that make unsafe assumptions about IEEE math (e.g. that
+addition is associative) or may not work for all input ranges. These
+optimizations allow the code generator to make use of some instructions which
+would otherwise not be usable (such as fsin on X86).</p>
+</dd>
+<dt><strong><a name="enable_correct_eh_support" class="item"><strong>--enable-correct-eh-support</strong></a></strong></dt>
+
+<dd>
+<p>Instruct the <strong>lowerinvoke</strong> pass to insert code for correct exception handling
+support. This is expensive and is by default omitted for efficiency.</p>
+</dd>
+<dt><strong><a name="stats" class="item"><strong>--stats</strong></a></strong></dt>
+
+<dd>
+<p>Print statistics recorded by code-generation passes.</p>
+</dd>
+<dt><strong><a name="time_passes" class="item"><strong>--time-passes</strong></a></strong></dt>
+
+<dd>
+<p>Record the amount of time needed for each pass and print a report to standard
+error.</p>
+</dd>
+<dt><strong><a name="load_dso_path" class="item"><strong>--load</strong>=<em class="file">dso_path</em></a></strong></dt>
+
+<dd>
+<p>Dynamically load <em class="file">dso_path</em> (a path to a dynamically shared object) that
+implements an LLVM target. This will permit the target name to be used with the
+<strong>-march</strong> option so that code can be generated for that target.</p>
+</dd>
+</dl>
+<p>
+</p>
+<h2><a name="tuning_configuration_options">Tuning/Configuration Options</a></h2>
+<dl>
+<dt><strong><a name="print_machineinstrs" class="item"><strong>--print-machineinstrs</strong></a></strong></dt>
+
+<dd>
+<p>Print generated machine code between compilation phases (useful for debugging).</p>
+</dd>
+<dt><strong><a name="regalloc_allocator" class="item"><strong>--regalloc</strong>=<em>allocator</em></a></strong></dt>
+
+<dd>
+<p>Specify the register allocator to use. The default <em>allocator</em> is <em>local</em>.
+Valid register allocators are:</p>
+<dl>
+<dt><strong><a name="simple" class="item"><em>simple</em></a></strong></dt>
+
+<dd>
+<p>Very simple "always spill" register allocator</p>
+</dd>
+<dt><strong><a name="local" class="item"><em>local</em></a></strong></dt>
+
+<dd>
+<p>Local register allocator</p>
+</dd>
+<dt><strong><a name="linearscan" class="item"><em>linearscan</em></a></strong></dt>
+
+<dd>
+<p>Linear scan global register allocator</p>
+</dd>
+<dt><strong><a name="iterativescan" class="item"><em>iterativescan</em></a></strong></dt>
+
+<dd>
+<p>Iterative scan global register allocator</p>
+</dd>
+</dl>
+</dd>
+<dt><strong><a name="spiller_spiller" class="item"><strong>--spiller</strong>=<em>spiller</em></a></strong></dt>
+
+<dd>
+<p>Specify the spiller to use for register allocators that support it. Currently
+this option is used only by the linear scan register allocator. The default
+<em>spiller</em> is <em>local</em>. Valid spillers are:</p>
+<dl>
+<dt><strong><em>simple</em></strong></dt>
+
+<dd>
+<p>Simple spiller</p>
+</dd>
+<dt><strong><em>local</em></strong></dt>
+
+<dd>
+<p>Local spiller</p>
+</dd>
+</dl>
+</dd>
+</dl>
+<p>
+</p>
+<h2><a name="intel_ia_32_specific_options">Intel IA-32-specific Options</a></h2>
+<dl>
+<dt><strong><a name="x86_asm_syntax_att_intel" class="item"><strong>--x86-asm-syntax=att|intel</strong></a></strong></dt>
+
+<dd>
+<p>Specify whether to emit assembly code in AT&T syntax (the default) or intel
+syntax.</p>
+</dd>
+</dl>
+<p>
+</p>
+<hr />
+<h1><a name="exit_status">EXIT STATUS</a></h1>
+<p>If <strong>llc</strong> succeeds, it will exit with 0. Otherwise, if an error occurs,
+it will exit with a non-zero value.</p>
+<p>
+</p>
+<hr />
+<h1><a name="see_also">SEE ALSO</a></h1>
+<p><a href="././lli.html">lli</a></p>
+<p>
+</p>
+<hr />
+<h1><a name="authors">AUTHORS</a></h1>
+<p>Maintained by the LLVM Team (<a href="http://llvm.org/">http://llvm.org/</a>).</p>
+
+</body>
+
+</html>
Added: www-releases/trunk/3.0/docs/CommandGuide/html/lli.html
URL: http://llvm.org/viewvc/llvm-project/www-releases/trunk/3.0/docs/CommandGuide/html/lli.html?rev=145591&view=auto
==============================================================================
--- www-releases/trunk/3.0/docs/CommandGuide/html/lli.html (added)
+++ www-releases/trunk/3.0/docs/CommandGuide/html/lli.html Thu Dec 1 11:44:59 2011
@@ -0,0 +1,288 @@
+<?xml version="1.0" ?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+<title>lli</title>
+<link rel="stylesheet" href="manpage.css" type="text/css" />
+<meta http-equiv="content-type" content="text/html; charset=utf-8" />
+<link rev="made" href="mailto:root at localhost" />
+</head>
+
+<body>
+
+
+<!-- INDEX BEGIN -->
+<div name="index">
+<p><a name="__index__"></a></p>
+<!--
+
+<ul>
+
+ <li><a href="#name">NAME</a></li>
+ <li><a href="#synopsis">SYNOPSIS</a></li>
+ <li><a href="#description">DESCRIPTION</a></li>
+ <li><a href="#general_options">GENERAL OPTIONS</a></li>
+ <li><a href="#target_options">TARGET OPTIONS</a></li>
+ <li><a href="#floating_point_options">FLOATING POINT OPTIONS</a></li>
+ <li><a href="#code_generation_options">CODE GENERATION OPTIONS</a></li>
+ <li><a href="#exit_status">EXIT STATUS</a></li>
+ <li><a href="#see_also">SEE ALSO</a></li>
+ <li><a href="#author">AUTHOR</a></li>
+</ul>
+
+-->
+
+
+</div>
+<!-- INDEX END -->
+
+<p>
+</p>
+<hr />
+<h1><a name="name">NAME</a></h1>
+<p>lli - directly execute programs from LLVM bitcode</p>
+<p>
+</p>
+<hr />
+<h1><a name="synopsis">SYNOPSIS</a></h1>
+<p><strong>lli</strong> [<em>options</em>] [<em>filename</em>] [<em>program args</em>]</p>
+<p>
+</p>
+<hr />
+<h1><a name="description">DESCRIPTION</a></h1>
+<p><strong>lli</strong> directly executes programs in LLVM bitcode format. It takes a program
+in LLVM bitcode format and executes it using a just-in-time compiler, if one is
+available for the current architecture, or an interpreter. <strong>lli</strong> takes all of
+the same code generator options as <a href="././llc.html">llc</a>, but they are only effective when
+<strong>lli</strong> is using the just-in-time compiler.</p>
+<p>If <em>filename</em> is not specified, then <strong>lli</strong> reads the LLVM bitcode for the
+program from standard input.</p>
+<p>The optional <em>args</em> specified on the command line are passed to the program as
+arguments.</p>
+<p>
+</p>
+<hr />
+<h1><a name="general_options">GENERAL OPTIONS</a></h1>
+<dl>
+<dt><strong><a name="fake_argv0_executable" class="item"><strong>-fake-argv0</strong>=<em>executable</em></a></strong></dt>
+
+<dd>
+<p>Override the <code>argv[0]</code> value passed into the executing program.</p>
+</dd>
+<dt><strong><a name="force_interpreter_false_true" class="item"><strong>-force-interpreter</strong>=<em>{false,true}</em></a></strong></dt>
+
+<dd>
+<p>If set to true, use the interpreter even if a just-in-time compiler is available
+for this architecture. Defaults to false.</p>
+</dd>
+<dt><strong><a name="help" class="item"><strong>-help</strong></a></strong></dt>
+
+<dd>
+<p>Print a summary of command line options.</p>
+</dd>
+<dt><strong><a name="load_puginfilename" class="item"><strong>-load</strong>=<em>puginfilename</em></a></strong></dt>
+
+<dd>
+<p>Causes <strong>lli</strong> to load the plugin (shared object) named <em>pluginfilename</em> and use
+it for optimization.</p>
+</dd>
+<dt><strong><a name="stats" class="item"><strong>-stats</strong></a></strong></dt>
+
+<dd>
+<p>Print statistics from the code-generation passes. This is only meaningful for
+the just-in-time compiler, at present.</p>
+</dd>
+<dt><strong><a name="time_passes" class="item"><strong>-time-passes</strong></a></strong></dt>
+
+<dd>
+<p>Record the amount of time needed for each code-generation pass and print it to
+standard error.</p>
+</dd>
+<dt><strong><a name="version" class="item"><strong>-version</strong></a></strong></dt>
+
+<dd>
+<p>Print out the version of <strong>lli</strong> and exit without doing anything else.</p>
+</dd>
+</dl>
+<p>
+</p>
+<hr />
+<h1><a name="target_options">TARGET OPTIONS</a></h1>
+<dl>
+<dt><strong><a name="mtriple_target_triple" class="item"><strong>-mtriple</strong>=<em>target triple</em></a></strong></dt>
+
+<dd>
+<p>Override the target triple specified in the input bitcode file with the
+specified string. This may result in a crash if you pick an
+architecture which is not compatible with the current system.</p>
+</dd>
+<dt><strong><a name="march_arch" class="item"><strong>-march</strong>=<em>arch</em></a></strong></dt>
+
+<dd>
+<p>Specify the architecture for which to generate assembly, overriding the target
+encoded in the bitcode file. See the output of <strong>llc -help</strong> for a list of
+valid architectures. By default this is inferred from the target triple or
+autodetected to the current architecture.</p>
+</dd>
+<dt><strong><a name="mcpu_cpuname" class="item"><strong>-mcpu</strong>=<em>cpuname</em></a></strong></dt>
+
+<dd>
+<p>Specify a specific chip in the current architecture to generate code for.
+By default this is inferred from the target triple and autodetected to
+the current architecture. For a list of available CPUs, use:
+<strong>llvm-as < /dev/null | llc -march=xyz -mcpu=help</strong></p>
+</dd>
+<dt><strong><a name="mattr_a1_a2_a3" class="item"><strong>-mattr</strong>=<em>a1,+a2,-a3,...</em></a></strong></dt>
+
+<dd>
+<p>Override or control specific attributes of the target, such as whether SIMD
+operations are enabled or not. The default set of attributes is set by the
+current CPU. For a list of available attributes, use:
+<strong>llvm-as < /dev/null | llc -march=xyz -mattr=help</strong></p>
+</dd>
+</dl>
+<p>
+</p>
+<hr />
+<h1><a name="floating_point_options">FLOATING POINT OPTIONS</a></h1>
+<dl>
+<dt><strong><a name="disable_excess_fp_precision" class="item"><strong>-disable-excess-fp-precision</strong></a></strong></dt>
+
+<dd>
+<p>Disable optimizations that may increase floating point precision.</p>
+</dd>
+<dt><strong><a name="enable_no_infs_fp_math" class="item"><strong>-enable-no-infs-fp-math</strong></a></strong></dt>
+
+<dd>
+<p>Enable optimizations that assume no Inf values.</p>
+</dd>
+<dt><strong><a name="enable_no_nans_fp_math" class="item"><strong>-enable-no-nans-fp-math</strong></a></strong></dt>
+
+<dd>
+<p>Enable optimizations that assume no NAN values.</p>
+</dd>
+<dt><strong><a name="enable_unsafe_fp_math" class="item"><strong>-enable-unsafe-fp-math</strong></a></strong></dt>
+
+<dd>
+<p>Causes <strong>lli</strong> to enable optimizations that may decrease floating point
+precision.</p>
+</dd>
+<dt><strong><a name="soft_float" class="item"><strong>-soft-float</strong></a></strong></dt>
+
+<dd>
+<p>Causes <strong>lli</strong> to generate software floating point library calls instead of
+equivalent hardware instructions.</p>
+</dd>
+</dl>
+<p>
+</p>
+<hr />
+<h1><a name="code_generation_options">CODE GENERATION OPTIONS</a></h1>
+<dl>
+<dt><strong><a name="code_model_model" class="item"><strong>-code-model</strong>=<em>model</em></a></strong></dt>
+
+<dd>
+<p>Choose the code model from:</p>
+<pre>
+ default: Target default code model
+ small: Small code model
+ kernel: Kernel code model
+ medium: Medium code model
+ large: Large code model</pre>
+</dd>
+<dt><strong><a name="disable_post_ra_scheduler" class="item"><strong>-disable-post-RA-scheduler</strong></a></strong></dt>
+
+<dd>
+<p>Disable scheduling after register allocation.</p>
+</dd>
+<dt><strong><a name="disable_spill_fusing" class="item"><strong>-disable-spill-fusing</strong></a></strong></dt>
+
+<dd>
+<p>Disable fusing of spill code into instructions.</p>
+</dd>
+<dt><strong><a name="enable_correct_eh_support" class="item"><strong>-enable-correct-eh-support</strong></a></strong></dt>
+
+<dd>
+<p>Make the -lowerinvoke pass insert expensive, but correct, EH code.</p>
+</dd>
+<dt><strong><a name="jit_enable_eh" class="item"><strong>-jit-enable-eh</strong></a></strong></dt>
+
+<dd>
+<p>Exception handling should be enabled in the just-in-time compiler.</p>
+</dd>
+<dt><strong><a name="join_liveintervals" class="item"><strong>-join-liveintervals</strong></a></strong></dt>
+
+<dd>
+<p>Coalesce copies (default=true).</p>
+</dd>
+<dt><strong><a name="nozero_initialized_in_bss_don_t_place_zero_initialized_symbols_into_the_bss_section" class="item"><strong>-nozero-initialized-in-bss</strong>
+Don't place zero-initialized symbols into the BSS section.</a></strong></dt>
+
+<dt><strong><a name="pre_ra_sched_scheduler" class="item"><strong>-pre-RA-sched</strong>=<em>scheduler</em></a></strong></dt>
+
+<dd>
+<p>Instruction schedulers available (before register allocation):</p>
+<pre>
+ =default: Best scheduler for the target
+ =none: No scheduling: breadth first sequencing
+ =simple: Simple two pass scheduling: minimize critical path and maximize processor utilization
+ =simple-noitin: Simple two pass scheduling: Same as simple except using generic latency
+ =list-burr: Bottom-up register reduction list scheduling
+ =list-tdrr: Top-down register reduction list scheduling
+ =list-td: Top-down list scheduler -print-machineinstrs - Print generated machine code</pre>
+</dd>
+<dt><strong><a name="regalloc_allocator" class="item"><strong>-regalloc</strong>=<em>allocator</em></a></strong></dt>
+
+<dd>
+<p>Register allocator to use (default=linearscan)</p>
+<pre>
+ =bigblock: Big-block register allocator
+ =linearscan: linear scan register allocator =local - local register allocator
+ =simple: simple register allocator</pre>
+</dd>
+<dt><strong><a name="relocation_model_model" class="item"><strong>-relocation-model</strong>=<em>model</em></a></strong></dt>
+
+<dd>
+<p>Choose relocation model from:</p>
+<pre>
+ =default: Target default relocation model
+ =static: Non-relocatable code =pic - Fully relocatable, position independent code
+ =dynamic-no-pic: Relocatable external references, non-relocatable code</pre>
+</dd>
+<dt><strong><a name="spiller" class="item"><strong>-spiller</strong></a></strong></dt>
+
+<dd>
+<p>Spiller to use (default=local)</p>
+<pre>
+ =simple: simple spiller
+ =local: local spiller</pre>
+</dd>
+<dt><strong><a name="x86_asm_syntax_syntax" class="item"><strong>-x86-asm-syntax</strong>=<em>syntax</em></a></strong></dt>
+
+<dd>
+<p>Choose style of code to emit from X86 backend:</p>
+<pre>
+ =att: Emit AT&T-style assembly
+ =intel: Emit Intel-style assembly</pre>
+</dd>
+</dl>
+<p>
+</p>
+<hr />
+<h1><a name="exit_status">EXIT STATUS</a></h1>
+<p>If <strong>lli</strong> fails to load the program, it will exit with an exit code of 1.
+Otherwise, it will return the exit code of the program it executes.</p>
+<p>
+</p>
+<hr />
+<h1><a name="see_also">SEE ALSO</a></h1>
+<p><a href="././llc.html">llc</a></p>
+<p>
+</p>
+<hr />
+<h1><a name="author">AUTHOR</a></h1>
+<p>Maintained by the LLVM Team (<a href="http://llvm.org/">http://llvm.org/</a>).</p>
+
+</body>
+
+</html>
Added: www-releases/trunk/3.0/docs/CommandGuide/html/llvm-ar.html
URL: http://llvm.org/viewvc/llvm-project/www-releases/trunk/3.0/docs/CommandGuide/html/llvm-ar.html?rev=145591&view=auto
==============================================================================
--- www-releases/trunk/3.0/docs/CommandGuide/html/llvm-ar.html (added)
+++ www-releases/trunk/3.0/docs/CommandGuide/html/llvm-ar.html Thu Dec 1 11:44:59 2011
@@ -0,0 +1,479 @@
+<?xml version="1.0" ?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+<title>llvm-ar</title>
+<link rel="stylesheet" href="manpage.css" type="text/css" />
+<meta http-equiv="content-type" content="text/html; charset=utf-8" />
+<link rev="made" href="mailto:root at localhost" />
+</head>
+
+<body>
+
+
+<!-- INDEX BEGIN -->
+<div name="index">
+<p><a name="__index__"></a></p>
+<!--
+
+<ul>
+
+ <li><a href="#name">NAME</a></li>
+ <li><a href="#synopsis">SYNOPSIS</a></li>
+ <li><a href="#description">DESCRIPTION</a></li>
+ <li><a href="#options">OPTIONS</a></li>
+ <ul>
+
+ <li><a href="#operations">Operations</a></li>
+ <li><a href="#modifiers__operation_specific_">Modifiers (operation specific)</a></li>
+ <li><a href="#modifiers__generic_">Modifiers (generic)</a></li>
+ </ul>
+
+ <li><a href="#standards">STANDARDS</a></li>
+ <li><a href="#file_format">FILE FORMAT</a></li>
+ <li><a href="#exit_status">EXIT STATUS</a></li>
+ <li><a href="#see_also">SEE ALSO</a></li>
+ <li><a href="#authors">AUTHORS</a></li>
+</ul>
+
+-->
+
+
+</div>
+<!-- INDEX END -->
+
+<p>
+</p>
+<hr />
+<h1><a name="name">NAME</a></h1>
+<p>llvm-ar - LLVM archiver</p>
+<p>
+</p>
+<hr />
+<h1><a name="synopsis">SYNOPSIS</a></h1>
+<p><strong>llvm-ar</strong> [-]{dmpqrtx}[Rabfikouz] [relpos] [count] <archive> [files...]</p>
+<p>
+</p>
+<hr />
+<h1><a name="description">DESCRIPTION</a></h1>
+<p>The <strong>llvm-ar</strong> command is similar to the common Unix utility, <code>ar</code>. It
+archives several files together into a single file. The intent for this is
+to produce archive libraries by LLVM bitcode that can be linked into an
+LLVM program. However, the archive can contain any kind of file. By default,
+<strong>llvm-ar</strong> generates a symbol table that makes linking faster because
+only the symbol table needs to be consulted, not each individual file member
+of the archive.</p>
+<p>The <strong>llvm-ar</strong> command can be used to <em>read</em> both SVR4 and BSD style archive
+files. However, it cannot be used to write them. While the <strong>llvm-ar</strong> command
+produces files that are <em>almost</em> identical to the format used by other <code>ar</code>
+implementations, it has two significant departures in order to make the
+archive appropriate for LLVM. The first departure is that <strong>llvm-ar</strong> only
+uses BSD4.4 style long path names (stored immediately after the header) and
+never contains a string table for long names. The second departure is that the
+symbol table is formated for efficient construction of an in-memory data
+structure that permits rapid (red-black tree) lookups. Consequently, archives
+produced with <strong>llvm-ar</strong> usually won't be readable or editable with any
+<code>ar</code> implementation or useful for linking. Using the <a href="#f"><code>f</code></a> modifier to flatten
+file names will make the archive readable by other <code>ar</code> implementations
+but not for linking because the symbol table format for LLVM is unique. If an
+SVR4 or BSD style archive is used with the <code>r</code> (replace) or <code>q</code> (quick
+update) operations, the archive will be reconstructed in LLVM format. This
+means that the string table will be dropped (in deference to BSD 4.4 long names)
+and an LLVM symbol table will be added (by default). The system symbol table
+will be retained.</p>
+<p>Here's where <strong>llvm-ar</strong> departs from previous <code>ar</code> implementations:</p>
+<dl>
+<dt><strong><a name="symbol_table" class="item"><em>Symbol Table</em></a></strong></dt>
+
+<dd>
+<p>Since <strong>llvm-ar</strong> is intended to archive bitcode files, the symbol table
+won't make much sense to anything but LLVM. Consequently, the symbol table's
+format has been simplified. It consists simply of a sequence of pairs
+of a file member index number as an LSB 4byte integer and a null-terminated
+string.</p>
+</dd>
+<dt><strong><a name="long_paths" class="item"><em>Long Paths</em></a></strong></dt>
+
+<dd>
+<p>Some <code>ar</code> implementations (SVR4) use a separate file member to record long
+path names (> 15 characters). <strong>llvm-ar</strong> takes the BSD 4.4 and Mac OS X
+approach which is to simply store the full path name immediately preceding
+the data for the file. The path name is null terminated and may contain the
+slash (/) character.</p>
+</dd>
+<dt><strong><a name="compression" class="item"><em>Compression</em></a></strong></dt>
+
+<dd>
+<p><strong>llvm-ar</strong> can compress the members of an archive to save space. The
+compression used depends on what's available on the platform and what choices
+the LLVM Compressor utility makes. It generally favors bzip2 but will select
+between "no compression" or bzip2 depending on what makes sense for the
+file's content.</p>
+</dd>
+<dt><strong><a name="directory_recursion" class="item"><em>Directory Recursion</em></a></strong></dt>
+
+<dd>
+<p>Most <code>ar</code> implementations do not recurse through directories but simply
+ignore directories if they are presented to the program in the <em class="file">files</em>
+option. <strong>llvm-ar</strong>, however, can recurse through directory structures and
+add all the files under a directory, if requested.</p>
+</dd>
+<dt><strong><a name="toc_verbose_output" class="item"><em>TOC Verbose Output</em></a></strong></dt>
+
+<dd>
+<p>When <strong>llvm-ar</strong> prints out the verbose table of contents (<code>tv</code> option), it
+precedes the usual output with a character indicating the basic kind of
+content in the file. A blank means the file is a regular file. A 'Z' means
+the file is compressed. A 'B' means the file is an LLVM bitcode file. An
+'S' means the file is the symbol table.</p>
+</dd>
+</dl>
+<p>
+</p>
+<hr />
+<h1><a name="options">OPTIONS</a></h1>
+<p>The options to <strong>llvm-ar</strong> are compatible with other <code>ar</code> implementations.
+However, there are a few modifiers (<em class="file">zR</em>) that are not found in other
+<code>ar</code>s. The options to <strong>llvm-ar</strong> specify a single basic operation to
+perform on the archive, a variety of modifiers for that operation, the
+name of the archive file, and an optional list of file names. These options
+are used to determine how <strong>llvm-ar</strong> should process the archive file.</p>
+<p>The Operations and Modifiers are explained in the sections below. The minimal
+set of options is at least one operator and the name of the archive. Typically
+archive files end with a <a href="#a"><code>.a</code></a> suffix, but this is not required. Following
+the <em class="file">archive-name</em> comes a list of <em class="file">files</em> that indicate the specific members
+of the archive to operate on. If the <em class="file">files</em> option is not specified, it
+generally means either "none" or "all" members, depending on the operation.</p>
+<p>
+</p>
+<h2><a name="operations">Operations</a></h2>
+<dl>
+<dt><strong><a name="d" class="item">d</a></strong></dt>
+
+<dd>
+<p>Delete files from the archive. No modifiers are applicable to this operation.
+The <em class="file">files</em> options specify which members should be removed from the
+archive. It is not an error if a specified file does not appear in the archive.
+If no <em class="file">files</em> are specified, the archive is not modified.</p>
+</dd>
+<dt><strong><a name="m_abi" class="item">m[abi]</a></strong></dt>
+
+<dd>
+<p>Move files from one location in the archive to another. The <em class="file">a</em>, <em class="file">b</em>, and
+<em class="file">i</em> modifiers apply to this operation. The <em class="file">files</em> will all be moved
+to the location given by the modifiers. If no modifiers are used, the files
+will be moved to the end of the archive. If no <em class="file">files</em> are specified, the
+archive is not modified.</p>
+</dd>
+<dt><strong><a name="p_k" class="item">p[k]</a></strong></dt>
+
+<dd>
+<p>Print files to the standard output. The <em class="file">k</em> modifier applies to this
+operation. This operation simply prints the <em class="file">files</em> indicated to the
+standard output. If no <em class="file">files</em> are specified, the entire archive is printed.
+Printing bitcode files is ill-advised as they might confuse your terminal
+settings. The <em class="file">p</em> operation never modifies the archive.</p>
+</dd>
+<dt><strong><a name="q_rfz" class="item">q[Rfz]</a></strong></dt>
+
+<dd>
+<p>Quickly append files to the end of the archive. The <em class="file">R</em>, <em class="file">f</em>, and <em class="file">z</em>
+modifiers apply to this operation. This operation quickly adds the
+<em class="file">files</em> to the archive without checking for duplicates that should be
+removed first. If no <em class="file">files</em> are specified, the archive is not modified.
+Because of the way that <strong>llvm-ar</strong> constructs the archive file, its dubious
+whether the <em class="file">q</em> operation is any faster than the <em class="file">r</em> operation.</p>
+</dd>
+<dt><strong><a name="r_rabfuz" class="item">r[Rabfuz]</a></strong></dt>
+
+<dd>
+<p>Replace or insert file members. The <em class="file">R</em>, <em class="file">a</em>, <em class="file">b</em>, <em class="file">f</em>, <em class="file">u</em>, and <em class="file">z</em>
+modifiers apply to this operation. This operation will replace existing
+<em class="file">files</em> or insert them at the end of the archive if they do not exist. If no
+<em class="file">files</em> are specified, the archive is not modified.</p>
+</dd>
+<dt><strong><a name="t_v" class="item">t[v]</a></strong></dt>
+
+<dd>
+<p>Print the table of contents. Without any modifiers, this operation just prints
+the names of the members to the standard output. With the <em class="file">v</em> modifier,
+<strong>llvm-ar</strong> also prints out the file type (B=bitcode, Z=compressed, S=symbol
+table, blank=regular file), the permission mode, the owner and group, the
+size, and the date. If any <em class="file">files</em> are specified, the listing is only for
+those files. If no <em class="file">files</em> are specified, the table of contents for the
+whole archive is printed.</p>
+</dd>
+<dt><strong><a name="x_op" class="item">x[oP]</a></strong></dt>
+
+<dd>
+<p>Extract archive members back to files. The <em class="file">o</em> modifier applies to this
+operation. This operation retrieves the indicated <em class="file">files</em> from the archive
+and writes them back to the operating system's file system. If no
+<em class="file">files</em> are specified, the entire archive is extract.</p>
+</dd>
+</dl>
+<p>
+</p>
+<h2><a name="modifiers__operation_specific_">Modifiers (operation specific)</a></h2>
+<p>The modifiers below are specific to certain operations. See the Operations
+section (above) to determine which modifiers are applicable to which operations.</p>
+<dl>
+<dt><strong><a name="a" class="item">[a]</a></strong></dt>
+
+<dd>
+<p>When inserting or moving member files, this option specifies the destination of
+the new files as being <a href="#a"><code>a</code></a>fter the <em class="file">relpos</em> member. If <em class="file">relpos</em> is not found,
+the files are placed at the end of the archive.</p>
+</dd>
+<dt><strong><a name="b" class="item">[b]</a></strong></dt>
+
+<dd>
+<p>When inserting or moving member files, this option specifies the destination of
+the new files as being <a href="#b"><code>b</code></a>efore the <em class="file">relpos</em> member. If <em class="file">relpos</em> is not
+found, the files are placed at the end of the archive. This modifier is
+identical to the the <em class="file">i</em> modifier.</p>
+</dd>
+<dt><strong><a name="f" class="item">[f]</a></strong></dt>
+
+<dd>
+<p>Normally, <strong>llvm-ar</strong> stores the full path name to a file as presented to it on
+the command line. With this option, truncated (15 characters max) names are
+used. This ensures name compatibility with older versions of <code>ar</code> but may also
+thwart correct extraction of the files (duplicates may overwrite). If used with
+the <em class="file">R</em> option, the directory recursion will be performed but the file names
+will all be <a href="#f"><code>f</code></a>lattened to simple file names.</p>
+</dd>
+<dt><strong><a name="i" class="item">[i]</a></strong></dt>
+
+<dd>
+<p>A synonym for the <em class="file">b</em> option.</p>
+</dd>
+<dt><strong><a name="k" class="item">[k]</a></strong></dt>
+
+<dd>
+<p>Normally, <strong>llvm-ar</strong> will not print the contents of bitcode files when the
+<em class="file">p</em> operation is used. This modifier defeats the default and allows the
+bitcode members to be printed.</p>
+</dd>
+<dt><strong><a name="n" class="item">[N]</a></strong></dt>
+
+<dd>
+<p>This option is ignored by <strong>llvm-ar</strong> but provided for compatibility.</p>
+</dd>
+<dt><strong><a name="o" class="item">[o]</a></strong></dt>
+
+<dd>
+<p>When extracting files, this option will cause <strong>llvm-ar</strong> to preserve the
+original modification times of the files it writes.</p>
+</dd>
+<dt><strong><a name="p" class="item">[P]</a></strong></dt>
+
+<dd>
+<p>use full path names when matching</p>
+</dd>
+<dt><strong><a name="r" class="item">[R]</a></strong></dt>
+
+<dd>
+<p>This modifier instructions the <em class="file">r</em> option to recursively process directories.
+Without <em class="file">R</em>, directories are ignored and only those <em class="file">files</em> that refer to
+files will be added to the archive. When <em class="file">R</em> is used, any directories specified
+with <em class="file">files</em> will be scanned (recursively) to find files to be added to the
+archive. Any file whose name begins with a dot will not be added.</p>
+</dd>
+<dt><strong><a name="u" class="item">[u]</a></strong></dt>
+
+<dd>
+<p>When replacing existing files in the archive, only replace those files that have
+a time stamp than the time stamp of the member in the archive.</p>
+</dd>
+<dt><strong><a name="z" class="item">[z]</a></strong></dt>
+
+<dd>
+<p>When inserting or replacing any file in the archive, compress the file first.
+This
+modifier is safe to use when (previously) compressed bitcode files are added to
+the archive; the compressed bitcode files will not be doubly compressed.</p>
+</dd>
+</dl>
+<p>
+</p>
+<h2><a name="modifiers__generic_">Modifiers (generic)</a></h2>
+<p>The modifiers below may be applied to any operation.</p>
+<dl>
+<dt><strong><a name="c" class="item">[c]</a></strong></dt>
+
+<dd>
+<p>For all operations, <strong>llvm-ar</strong> will always create the archive if it doesn't
+exist. Normally, <strong>llvm-ar</strong> will print a warning message indicating that the
+archive is being created. Using this modifier turns off that warning.</p>
+</dd>
+<dt><strong><a name="s" class="item">[s]</a></strong></dt>
+
+<dd>
+<p>This modifier requests that an archive index (or symbol table) be added to the
+archive. This is the default mode of operation. The symbol table will contain
+all the externally visible functions and global variables defined by all the
+bitcode files in the archive. Using this modifier is more efficient that using
+<a href="././llvm-ranlib.html">llvm-ranlib</a> which also creates the symbol table.</p>
+</dd>
+<dt><strong><a name="s" class="item">[S]</a></strong></dt>
+
+<dd>
+<p>This modifier is the opposite of the <em class="file">s</em> modifier. It instructs <strong>llvm-ar</strong> to
+not build the symbol table. If both <em class="file">s</em> and <em class="file">S</em> are used, the last modifier to
+occur in the options will prevail.</p>
+</dd>
+<dt><strong><a name="v" class="item">[v]</a></strong></dt>
+
+<dd>
+<p>This modifier instructs <strong>llvm-ar</strong> to be verbose about what it is doing. Each
+editing operation taken against the archive will produce a line of output saying
+what is being done.</p>
+</dd>
+</dl>
+<p>
+</p>
+<hr />
+<h1><a name="standards">STANDARDS</a></h1>
+<p>The <strong>llvm-ar</strong> utility is intended to provide a superset of the IEEE Std 1003.2
+(POSIX.2) functionality for <code>ar</code>. <strong>llvm-ar</strong> can read both SVR4 and BSD4.4 (or
+Mac OS X) archives. If the <a href="#f"><code>f</code></a> modifier is given to the <code>x</code> or <code>r</code> operations
+then <strong>llvm-ar</strong> will write SVR4 compatible archives. Without this modifier,
+<strong>llvm-ar</strong> will write BSD4.4 compatible archives that have long names
+immediately after the header and indicated using the "#1/ddd" notation for the
+name in the header.</p>
+<p>
+</p>
+<hr />
+<h1><a name="file_format">FILE FORMAT</a></h1>
+<p>The file format for LLVM Archive files is similar to that of BSD 4.4 or Mac OSX
+archive files. In fact, except for the symbol table, the <code>ar</code> commands on those
+operating systems should be able to read LLVM archive files. The details of the
+file format follow.</p>
+<p>Each archive begins with the archive magic number which is the eight printable
+characters "!<arch>\n" where \n represents the newline character (0x0A).
+Following the magic number, the file is composed of even length members that
+begin with an archive header and end with a \n padding character if necessary
+(to make the length even). Each file member is composed of a header (defined
+below), an optional newline-terminated "long file name" and the contents of
+the file.</p>
+<p>The fields of the header are described in the items below. All fields of the
+header contain only ASCII characters, are left justified and are right padded
+with space characters.</p>
+<dl>
+<dt><strong><a name="name_char_16" class="item">name - char[16]</a></strong></dt>
+
+<dd>
+<p>This field of the header provides the name of the archive member. If the name is
+longer than 15 characters or contains a slash (/) character, then this field
+contains <code>#1/nnn</code> where <code>nnn</code> provides the length of the name and the <code>#1/</code>
+is literal. In this case, the actual name of the file is provided in the <code>nnn</code>
+bytes immediately following the header. If the name is 15 characters or less, it
+is contained directly in this field and terminated with a slash (/) character.</p>
+</dd>
+<dt><strong><a name="date_char_12" class="item">date - char[12]</a></strong></dt>
+
+<dd>
+<p>This field provides the date of modification of the file in the form of a
+decimal encoded number that provides the number of seconds since the epoch
+(since 00:00:00 Jan 1, 1970) per Posix specifications.</p>
+</dd>
+<dt><strong><a name="uid_char_6" class="item">uid - char[6]</a></strong></dt>
+
+<dd>
+<p>This field provides the user id of the file encoded as a decimal ASCII string.
+This field might not make much sense on non-Unix systems. On Unix, it is the
+same value as the st_uid field of the stat structure returned by the <code>stat(2)</code>
+operating system call.</p>
+</dd>
+<dt><strong><a name="gid_char_6" class="item">gid - char[6]</a></strong></dt>
+
+<dd>
+<p>This field provides the group id of the file encoded as a decimal ASCII string.
+This field might not make much sense on non-Unix systems. On Unix, it is the
+same value as the st_gid field of the stat structure returned by the <code>stat(2)</code>
+operating system call.</p>
+</dd>
+<dt><strong><a name="mode_char_8" class="item">mode - char[8]</a></strong></dt>
+
+<dd>
+<p>This field provides the access mode of the file encoded as an octal ASCII
+string. This field might not make much sense on non-Unix systems. On Unix, it
+is the same value as the st_mode field of the stat structure returned by the
+<code>stat(2)</code> operating system call.</p>
+</dd>
+<dt><strong><a name="size_char_10" class="item">size - char[10]</a></strong></dt>
+
+<dd>
+<p>This field provides the size of the file, in bytes, encoded as a decimal ASCII
+string. If the size field is negative (starts with a minus sign, 0x02D), then
+the archive member is stored in compressed form. The first byte of the archive
+member's data indicates the compression type used. A value of 0 (0x30) indicates
+that no compression was used. A value of 2 (0x32) indicates that bzip2
+compression was used.</p>
+</dd>
+<dt><strong><a name="fmag_char_2" class="item">fmag - char[2]</a></strong></dt>
+
+<dd>
+<p>This field is the archive file member magic number. Its content is always the
+two characters back tick (0x60) and newline (0x0A). This provides some measure
+utility in identifying archive files that have been corrupted.</p>
+</dd>
+</dl>
+<p>The LLVM symbol table has the special name "#_LLVM_SYM_TAB_#". It is presumed
+that no regular archive member file will want this name. The LLVM symbol table
+is simply composed of a sequence of triplets: byte offset, length of symbol,
+and the symbol itself. Symbols are not null or newline terminated. Here are
+the details on each of these items:</p>
+<dl>
+<dt><strong><a name="offset_vbr_encoded_32_bit_integer" class="item">offset - vbr encoded 32-bit integer</a></strong></dt>
+
+<dd>
+<p>The offset item provides the offset into the archive file where the bitcode
+member is stored that is associated with the symbol. The offset value is 0
+based at the start of the first "normal" file member. To derive the actual
+file offset of the member, you must add the number of bytes occupied by the file
+signature (8 bytes) and the symbol tables. The value of this item is encoded
+using variable bit rate encoding to reduce the size of the symbol table.
+Variable bit rate encoding uses the high bit (0x80) of each byte to indicate
+if there are more bytes to follow. The remaining 7 bits in each byte carry bits
+from the value. The final byte does not have the high bit set.</p>
+</dd>
+<dt><strong><a name="length_vbr_encoded_32_bit_integer" class="item">length - vbr encoded 32-bit integer</a></strong></dt>
+
+<dd>
+<p>The length item provides the length of the symbol that follows. Like this
+<em>offset</em> item, the length is variable bit rate encoded.</p>
+</dd>
+<dt><strong><a name="symbol_character_array" class="item">symbol - character array</a></strong></dt>
+
+<dd>
+<p>The symbol item provides the text of the symbol that is associated with the
+<em>offset</em>. The symbol is not terminated by any character. Its length is provided
+by the <em>length</em> field. Note that is allowed (but unwise) to use non-printing
+characters (even 0x00) in the symbol. This allows for multiple encodings of
+symbol names.</p>
+</dd>
+</dl>
+<p>
+</p>
+<hr />
+<h1><a name="exit_status">EXIT STATUS</a></h1>
+<p>If <strong>llvm-ar</strong> succeeds, it will exit with 0. A usage error, results
+in an exit code of 1. A hard (file system typically) error results in an
+exit code of 2. Miscellaneous or unknown errors result in an
+exit code of 3.</p>
+<p>
+</p>
+<hr />
+<h1><a name="see_also">SEE ALSO</a></h1>
+<p><a href="././llvm-ranlib.html">llvm-ranlib</a>, <code>ar(1)</code></p>
+<p>
+</p>
+<hr />
+<h1><a name="authors">AUTHORS</a></h1>
+<p>Maintained by the LLVM Team (<a href="http://llvm.org/">http://llvm.org/</a>).</p>
+
+</body>
+
+</html>
Added: www-releases/trunk/3.0/docs/CommandGuide/html/llvm-as.html
URL: http://llvm.org/viewvc/llvm-project/www-releases/trunk/3.0/docs/CommandGuide/html/llvm-as.html?rev=145591&view=auto
==============================================================================
--- www-releases/trunk/3.0/docs/CommandGuide/html/llvm-as.html (added)
+++ www-releases/trunk/3.0/docs/CommandGuide/html/llvm-as.html Thu Dec 1 11:44:59 2011
@@ -0,0 +1,115 @@
+<?xml version="1.0" ?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+<title>llvm-as</title>
+<link rel="stylesheet" href="manpage.css" type="text/css" />
+<meta http-equiv="content-type" content="text/html; charset=utf-8" />
+<link rev="made" href="mailto:root at localhost" />
+</head>
+
+<body>
+
+
+<!-- INDEX BEGIN -->
+<div name="index">
+<p><a name="__index__"></a></p>
+<!--
+
+<ul>
+
+ <li><a href="#name">NAME</a></li>
+ <li><a href="#synopsis">SYNOPSIS</a></li>
+ <li><a href="#description">DESCRIPTION</a></li>
+ <li><a href="#options">OPTIONS</a></li>
+ <li><a href="#exit_status">EXIT STATUS</a></li>
+ <li><a href="#see_also">SEE ALSO</a></li>
+ <li><a href="#authors">AUTHORS</a></li>
+</ul>
+
+-->
+
+
+</div>
+<!-- INDEX END -->
+
+<p>
+</p>
+<hr />
+<h1><a name="name">NAME</a></h1>
+<p>llvm-as - LLVM assembler</p>
+<p>
+</p>
+<hr />
+<h1><a name="synopsis">SYNOPSIS</a></h1>
+<p><strong>llvm-as</strong> [<em>options</em>] [<em>filename</em>]</p>
+<p>
+</p>
+<hr />
+<h1><a name="description">DESCRIPTION</a></h1>
+<p><strong>llvm-as</strong> is the LLVM assembler. It reads a file containing human-readable
+LLVM assembly language, translates it to LLVM bitcode, and writes the result
+into a file or to standard output.</p>
+<p>If <em class="file">filename</em> is omitted or is <code>-</code>, then <strong>llvm-as</strong> reads its input from
+standard input.</p>
+<p>If an output file is not specified with the <strong>-o</strong> option, then
+<strong>llvm-as</strong> sends its output to a file or standard output by following
+these rules:</p>
+<ul>
+<li>
+<p>If the input is standard input, then the output is standard output.</p>
+</li>
+<li>
+<p>If the input is a file that ends with <code>.ll</code>, then the output file is of
+the same name, except that the suffix is changed to <code>.bc</code>.</p>
+</li>
+<li>
+<p>If the input is a file that does not end with the <code>.ll</code> suffix, then the
+output file has the same name as the input file, except that the <code>.bc</code>
+suffix is appended.</p>
+</li>
+</ul>
+<p>
+</p>
+<hr />
+<h1><a name="options">OPTIONS</a></h1>
+<dl>
+<dt><strong><a name="f" class="item"><strong>-f</strong></a></strong></dt>
+
+<dd>
+<p>Enable binary output on terminals. Normally, <strong>llvm-as</strong> will refuse to
+write raw bitcode output if the output stream is a terminal. With this option,
+<strong>llvm-as</strong> will write raw bitcode regardless of the output device.</p>
+</dd>
+<dt><strong><a name="help" class="item"><strong>-help</strong></a></strong></dt>
+
+<dd>
+<p>Print a summary of command line options.</p>
+</dd>
+<dt><strong><a name="o_filename" class="item"><strong>-o</strong> <em class="file">filename</em></a></strong></dt>
+
+<dd>
+<p>Specify the output file name. If <em class="file">filename</em> is <code>-</code>, then <strong>llvm-as</strong>
+sends its output to standard output.</p>
+</dd>
+</dl>
+<p>
+</p>
+<hr />
+<h1><a name="exit_status">EXIT STATUS</a></h1>
+<p>If <strong>llvm-as</strong> succeeds, it will exit with 0. Otherwise, if an error
+occurs, it will exit with a non-zero value.</p>
+<p>
+</p>
+<hr />
+<h1><a name="see_also">SEE ALSO</a></h1>
+<p><a href="././llvm-dis.html">llvm-dis</a>, <em>gccas</em></p>
+<p>
+</p>
+<hr />
+<h1><a name="authors">AUTHORS</a></h1>
+<p>Maintained by the LLVM Team (<a href="http://llvm.org/">http://llvm.org/</a>).</p>
+
+</body>
+
+</html>
Added: www-releases/trunk/3.0/docs/CommandGuide/html/llvm-bcanalyzer.html
URL: http://llvm.org/viewvc/llvm-project/www-releases/trunk/3.0/docs/CommandGuide/html/llvm-bcanalyzer.html?rev=145591&view=auto
==============================================================================
--- www-releases/trunk/3.0/docs/CommandGuide/html/llvm-bcanalyzer.html (added)
+++ www-releases/trunk/3.0/docs/CommandGuide/html/llvm-bcanalyzer.html Thu Dec 1 11:44:59 2011
@@ -0,0 +1,409 @@
+<?xml version="1.0" ?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+<title>llvm-bcanalyzer</title>
+<link rel="stylesheet" href="manpage.css" type="text/css" />
+<meta http-equiv="content-type" content="text/html; charset=utf-8" />
+<link rev="made" href="mailto:root at localhost" />
+</head>
+
+<body>
+
+
+<!-- INDEX BEGIN -->
+<div name="index">
+<p><a name="__index__"></a></p>
+<!--
+
+<ul>
+
+ <li><a href="#name">NAME</a></li>
+ <li><a href="#synopsis">SYNOPSIS</a></li>
+ <li><a href="#description">DESCRIPTION</a></li>
+ <li><a href="#options">OPTIONS</a></li>
+ <li><a href="#exit_status">EXIT STATUS</a></li>
+ <li><a href="#summary_output_definitions">SUMMARY OUTPUT DEFINITIONS</a></li>
+ <li><a href="#detailed_output_definitions">DETAILED OUTPUT DEFINITIONS</a></li>
+ <li><a href="#see_also">SEE ALSO</a></li>
+ <li><a href="#authors">AUTHORS</a></li>
+</ul>
+
+-->
+
+
+</div>
+<!-- INDEX END -->
+
+<p>
+</p>
+<hr />
+<h1><a name="name">NAME</a></h1>
+<p>llvm-bcanalyzer - LLVM bitcode analyzer</p>
+<p>
+</p>
+<hr />
+<h1><a name="synopsis">SYNOPSIS</a></h1>
+<p><strong>llvm-bcanalyzer</strong> [<em>options</em>] [<em class="file">filename</em>]</p>
+<p>
+</p>
+<hr />
+<h1><a name="description">DESCRIPTION</a></h1>
+<p>The <strong>llvm-bcanalyzer</strong> command is a small utility for analyzing bitcode files.
+The tool reads a bitcode file (such as generated with the <strong>llvm-as</strong> tool) and
+produces a statistical report on the contents of the bitcode file. The tool
+can also dump a low level but human readable version of the bitcode file.
+This tool is probably not of much interest or utility except for those working
+directly with the bitcode file format. Most LLVM users can just ignore
+this tool.</p>
+<p>If <em class="file">filename</em> is omitted or is <code>-</code>, then <strong>llvm-bcanalyzer</strong> reads its input
+from standard input. This is useful for combining the tool into a pipeline.
+Output is written to the standard output.</p>
+<p>
+</p>
+<hr />
+<h1><a name="options">OPTIONS</a></h1>
+<dl>
+<dt><strong><a name="nodetails" class="item"><strong>-nodetails</strong></a></strong></dt>
+
+<dd>
+<p>Causes <strong>llvm-bcanalyzer</strong> to abbreviate its output by writing out only a module
+level summary. The details for individual functions are not displayed.</p>
+</dd>
+<dt><strong><a name="dump" class="item"><strong>-dump</strong></a></strong></dt>
+
+<dd>
+<p>Causes <strong>llvm-bcanalyzer</strong> to dump the bitcode in a human readable format. This
+format is significantly different from LLVM assembly and provides details about
+the encoding of the bitcode file.</p>
+</dd>
+<dt><strong><a name="verify" class="item"><strong>-verify</strong></a></strong></dt>
+
+<dd>
+<p>Causes <strong>llvm-bcanalyzer</strong> to verify the module produced by reading the
+bitcode. This ensures that the statistics generated are based on a consistent
+module.</p>
+</dd>
+<dt><strong><a name="help" class="item"><strong>-help</strong></a></strong></dt>
+
+<dd>
+<p>Print a summary of command line options.</p>
+</dd>
+</dl>
+<p>
+</p>
+<hr />
+<h1><a name="exit_status">EXIT STATUS</a></h1>
+<p>If <strong>llvm-bcanalyzer</strong> succeeds, it will exit with 0. Otherwise, if an error
+occurs, it will exit with a non-zero value, usually 1.</p>
+<p>
+</p>
+<hr />
+<h1><a name="summary_output_definitions">SUMMARY OUTPUT DEFINITIONS</a></h1>
+<p>The following items are always printed by llvm-bcanalyzer. They comprize the
+summary output.</p>
+<dl>
+<dt><strong><a name="bitcode_analysis_of_module" class="item"><strong>Bitcode Analysis Of Module</strong></a></strong></dt>
+
+<dd>
+<p>This just provides the name of the module for which bitcode analysis is being
+generated.</p>
+</dd>
+<dt><strong><a name="bitcode_version_number" class="item"><strong>Bitcode Version Number</strong></a></strong></dt>
+
+<dd>
+<p>The bitcode version (not LLVM version) of the file read by the analyzer.</p>
+</dd>
+<dt><strong><a name="file_size" class="item"><strong>File Size</strong></a></strong></dt>
+
+<dd>
+<p>The size, in bytes, of the entire bitcode file.</p>
+</dd>
+<dt><strong><a name="module_bytes" class="item"><strong>Module Bytes</strong></a></strong></dt>
+
+<dd>
+<p>The size, in bytes, of the module block. Percentage is relative to File Size.</p>
+</dd>
+<dt><strong><a name="function_bytes" class="item"><strong>Function Bytes</strong></a></strong></dt>
+
+<dd>
+<p>The size, in bytes, of all the function blocks. Percentage is relative to File
+Size.</p>
+</dd>
+<dt><strong><a name="global_types_bytes" class="item"><strong>Global Types Bytes</strong></a></strong></dt>
+
+<dd>
+<p>The size, in bytes, of the Global Types Pool. Percentage is relative to File
+Size. This is the size of the definitions of all types in the bitcode file.</p>
+</dd>
+<dt><strong><a name="constant_pool_bytes" class="item"><strong>Constant Pool Bytes</strong></a></strong></dt>
+
+<dd>
+<p>The size, in bytes, of the Constant Pool Blocks Percentage is relative to File
+Size.</p>
+</dd>
+<dt><strong><a name="module_globals_bytes" class="item"><strong>Module Globals Bytes</strong></a></strong></dt>
+
+<dd>
+<p>Ths size, in bytes, of the Global Variable Definitions and their initializers.
+Percentage is relative to File Size.</p>
+</dd>
+<dt><strong><a name="instruction_list_bytes" class="item"><strong>Instruction List Bytes</strong></a></strong></dt>
+
+<dd>
+<p>The size, in bytes, of all the instruction lists in all the functions.
+Percentage is relative to File Size. Note that this value is also included in
+the Function Bytes.</p>
+</dd>
+<dt><strong><a name="compaction_table_bytes" class="item"><strong>Compaction Table Bytes</strong></a></strong></dt>
+
+<dd>
+<p>The size, in bytes, of all the compaction tables in all the functions.
+Percentage is relative to File Size. Note that this value is also included in
+the Function Bytes.</p>
+</dd>
+<dt><strong><a name="symbol_table_bytes" class="item"><strong>Symbol Table Bytes</strong></a></strong></dt>
+
+<dd>
+<p>The size, in bytes, of all the symbol tables in all the functions. Percentage is
+relative to File Size. Note that this value is also included in the Function
+Bytes.</p>
+</dd>
+<dt><strong><a name="dependent_libraries_bytes" class="item"><strong>Dependent Libraries Bytes</strong></a></strong></dt>
+
+<dd>
+<p>The size, in bytes, of the list of dependent libraries in the module. Percentage
+is relative to File Size. Note that this value is also included in the Module
+Global Bytes.</p>
+</dd>
+<dt><strong><a name="number_of_bitcode_blocks" class="item"><strong>Number Of Bitcode Blocks</strong></a></strong></dt>
+
+<dd>
+<p>The total number of blocks of any kind in the bitcode file.</p>
+</dd>
+<dt><strong><a name="number_of_functions" class="item"><strong>Number Of Functions</strong></a></strong></dt>
+
+<dd>
+<p>The total number of function definitions in the bitcode file.</p>
+</dd>
+<dt><strong><a name="number_of_types" class="item"><strong>Number Of Types</strong></a></strong></dt>
+
+<dd>
+<p>The total number of types defined in the Global Types Pool.</p>
+</dd>
+<dt><strong><a name="number_of_constants" class="item"><strong>Number Of Constants</strong></a></strong></dt>
+
+<dd>
+<p>The total number of constants (of any type) defined in the Constant Pool.</p>
+</dd>
+<dt><strong><a name="number_of_basic_blocks" class="item"><strong>Number Of Basic Blocks</strong></a></strong></dt>
+
+<dd>
+<p>The total number of basic blocks defined in all functions in the bitcode file.</p>
+</dd>
+<dt><strong><a name="number_of_instructions" class="item"><strong>Number Of Instructions</strong></a></strong></dt>
+
+<dd>
+<p>The total number of instructions defined in all functions in the bitcode file.</p>
+</dd>
+<dt><strong><a name="number_of_long_instructions" class="item"><strong>Number Of Long Instructions</strong></a></strong></dt>
+
+<dd>
+<p>The total number of long instructions defined in all functions in the bitcode
+file. Long instructions are those taking greater than 4 bytes. Typically long
+instructions are GetElementPtr with several indices, PHI nodes, and calls to
+functions with large numbers of arguments.</p>
+</dd>
+<dt><strong><a name="number_of_operands" class="item"><strong>Number Of Operands</strong></a></strong></dt>
+
+<dd>
+<p>The total number of operands used in all instructions in the bitcode file.</p>
+</dd>
+<dt><strong><a name="number_of_compaction_tables" class="item"><strong>Number Of Compaction Tables</strong></a></strong></dt>
+
+<dd>
+<p>The total number of compaction tables in all functions in the bitcode file.</p>
+</dd>
+<dt><strong><a name="number_of_symbol_tables" class="item"><strong>Number Of Symbol Tables</strong></a></strong></dt>
+
+<dd>
+<p>The total number of symbol tables in all functions in the bitcode file.</p>
+</dd>
+<dt><strong><a name="number_of_dependent_libs" class="item"><strong>Number Of Dependent Libs</strong></a></strong></dt>
+
+<dd>
+<p>The total number of dependent libraries found in the bitcode file.</p>
+</dd>
+<dt><strong><a name="total_instruction_size" class="item"><strong>Total Instruction Size</strong></a></strong></dt>
+
+<dd>
+<p>The total size of the instructions in all functions in the bitcode file.</p>
+</dd>
+<dt><strong><a name="average_instruction_size" class="item"><strong>Average Instruction Size</strong></a></strong></dt>
+
+<dd>
+<p>The average number of bytes per instruction across all functions in the bitcode
+file. This value is computed by dividing Total Instruction Size by Number Of
+Instructions.</p>
+</dd>
+<dt><strong><a name="maximum_type_slot_number" class="item"><strong>Maximum Type Slot Number</strong></a></strong></dt>
+
+<dd>
+<p>The maximum value used for a type's slot number. Larger slot number values take
+more bytes to encode.</p>
+</dd>
+<dt><strong><a name="maximum_value_slot_number" class="item"><strong>Maximum Value Slot Number</strong></a></strong></dt>
+
+<dd>
+<p>The maximum value used for a value's slot number. Larger slot number values take
+more bytes to encode.</p>
+</dd>
+<dt><strong><a name="bytes_per_value" class="item"><strong>Bytes Per Value</strong></a></strong></dt>
+
+<dd>
+<p>The average size of a Value definition (of any type). This is computed by
+dividing File Size by the total number of values of any type.</p>
+</dd>
+<dt><strong><a name="bytes_per_global" class="item"><strong>Bytes Per Global</strong></a></strong></dt>
+
+<dd>
+<p>The average size of a global definition (constants and global variables).</p>
+</dd>
+<dt><strong><a name="bytes_per_function" class="item"><strong>Bytes Per Function</strong></a></strong></dt>
+
+<dd>
+<p>The average number of bytes per function definition. This is computed by
+dividing Function Bytes by Number Of Functions.</p>
+</dd>
+<dt><strong><a name="of_vbr_32_bit_integers" class="item"><strong># of VBR 32-bit Integers</strong></a></strong></dt>
+
+<dd>
+<p>The total number of 32-bit integers encoded using the Variable Bit Rate
+encoding scheme.</p>
+</dd>
+<dt><strong><a name="of_vbr_64_bit_integers" class="item"><strong># of VBR 64-bit Integers</strong></a></strong></dt>
+
+<dd>
+<p>The total number of 64-bit integers encoded using the Variable Bit Rate encoding
+scheme.</p>
+</dd>
+<dt><strong><a name="of_vbr_compressed_bytes" class="item"><strong># of VBR Compressed Bytes</strong></a></strong></dt>
+
+<dd>
+<p>The total number of bytes consumed by the 32-bit and 64-bit integers that use
+the Variable Bit Rate encoding scheme.</p>
+</dd>
+<dt><strong><a name="of_vbr_expanded_bytes" class="item"><strong># of VBR Expanded Bytes</strong></a></strong></dt>
+
+<dd>
+<p>The total number of bytes that would have been consumed by the 32-bit and 64-bit
+integers had they not been compressed with the Variable Bit Rage encoding
+scheme.</p>
+</dd>
+<dt><strong><a name="bytes_saved_with_vbr" class="item"><strong>Bytes Saved With VBR</strong></a></strong></dt>
+
+<dd>
+<p>The total number of bytes saved by using the Variable Bit Rate encoding scheme.
+The percentage is relative to # of VBR Expanded Bytes.</p>
+</dd>
+</dl>
+<p>
+</p>
+<hr />
+<h1><a name="detailed_output_definitions">DETAILED OUTPUT DEFINITIONS</a></h1>
+<p>The following definitions occur only if the -nodetails option was not given.
+The detailed output provides additional information on a per-function basis.</p>
+<dl>
+<dt><strong><a name="type" class="item"><strong>Type</strong></a></strong></dt>
+
+<dd>
+<p>The type signature of the function.</p>
+</dd>
+<dt><strong><a name="byte_size" class="item"><strong>Byte Size</strong></a></strong></dt>
+
+<dd>
+<p>The total number of bytes in the function's block.</p>
+</dd>
+<dt><strong><a name="basic_blocks" class="item"><strong>Basic Blocks</strong></a></strong></dt>
+
+<dd>
+<p>The number of basic blocks defined by the function.</p>
+</dd>
+<dt><strong><a name="instructions" class="item"><strong>Instructions</strong></a></strong></dt>
+
+<dd>
+<p>The number of instructions defined by the function.</p>
+</dd>
+<dt><strong><a name="long_instructions" class="item"><strong>Long Instructions</strong></a></strong></dt>
+
+<dd>
+<p>The number of instructions using the long instruction format in the function.</p>
+</dd>
+<dt><strong><a name="operands" class="item"><strong>Operands</strong></a></strong></dt>
+
+<dd>
+<p>The number of operands used by all instructions in the function.</p>
+</dd>
+<dt><strong><a name="instruction_size" class="item"><strong>Instruction Size</strong></a></strong></dt>
+
+<dd>
+<p>The number of bytes consumed by instructions in the function.</p>
+</dd>
+<dt><strong><a name="average_instruction_size2" class="item"><strong>Average Instruction Size</strong></a></strong></dt>
+
+<dd>
+<p>The average number of bytes consumed by the instructions in the function. This
+value is computed by dividing Instruction Size by Instructions.</p>
+</dd>
+<dt><strong><a name="bytes_per_instruction" class="item"><strong>Bytes Per Instruction</strong></a></strong></dt>
+
+<dd>
+<p>The average number of bytes used by the function per instruction. This value is
+computed by dividing Byte Size by Instructions. Note that this is not the same
+as Average Instruction Size. It computes a number relative to the total function
+size not just the size of the instruction list.</p>
+</dd>
+<dt><strong><a name="number_of_vbr_32_bit_integers" class="item"><strong>Number of VBR 32-bit Integers</strong></a></strong></dt>
+
+<dd>
+<p>The total number of 32-bit integers found in this function (for any use).</p>
+</dd>
+<dt><strong><a name="number_of_vbr_64_bit_integers" class="item"><strong>Number of VBR 64-bit Integers</strong></a></strong></dt>
+
+<dd>
+<p>The total number of 64-bit integers found in this function (for any use).</p>
+</dd>
+<dt><strong><a name="number_of_vbr_compressed_bytes" class="item"><strong>Number of VBR Compressed Bytes</strong></a></strong></dt>
+
+<dd>
+<p>The total number of bytes in this function consumed by the 32-bit and 64-bit
+integers that use the Variable Bit Rate encoding scheme.</p>
+</dd>
+<dt><strong><a name="number_of_vbr_expanded_bytes" class="item"><strong>Number of VBR Expanded Bytes</strong></a></strong></dt>
+
+<dd>
+<p>The total number of bytes in this function that would have been consumed by
+the 32-bit and 64-bit integers had they not been compressed with the Variable
+Bit Rate encoding scheme.</p>
+</dd>
+<dt><strong><a name="bytes_saved_with_vbr2" class="item"><strong>Bytes Saved With VBR</strong></a></strong></dt>
+
+<dd>
+<p>The total number of bytes saved in this function by using the Variable Bit
+Rate encoding scheme. The percentage is relative to # of VBR Expanded Bytes.</p>
+</dd>
+</dl>
+<p>
+</p>
+<hr />
+<h1><a name="see_also">SEE ALSO</a></h1>
+<p><a href="././llvm-dis.html">llvm-dis</a>, <a href="http://llvm.org/docs/BitCodeFormat.html">http://llvm.org/docs/BitCodeFormat.html</a></p>
+<p>
+</p>
+<hr />
+<h1><a name="authors">AUTHORS</a></h1>
+<p>Maintained by the LLVM Team (<a href="http://llvm.org/">http://llvm.org/</a>).</p>
+
+</body>
+
+</html>
Added: www-releases/trunk/3.0/docs/CommandGuide/html/llvm-config.html
URL: http://llvm.org/viewvc/llvm-project/www-releases/trunk/3.0/docs/CommandGuide/html/llvm-config.html?rev=145591&view=auto
==============================================================================
--- www-releases/trunk/3.0/docs/CommandGuide/html/llvm-config.html (added)
+++ www-releases/trunk/3.0/docs/CommandGuide/html/llvm-config.html Thu Dec 1 11:44:59 2011
@@ -0,0 +1,192 @@
+<?xml version="1.0" ?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+<title>llvm-config</title>
+<link rel="stylesheet" href="manpage.css" type="text/css" />
+<meta http-equiv="content-type" content="text/html; charset=utf-8" />
+<link rev="made" href="mailto:root at localhost" />
+</head>
+
+<body>
+
+
+<!-- INDEX BEGIN -->
+<div name="index">
+<p><a name="__index__"></a></p>
+<!--
+
+<ul>
+
+ <li><a href="#name">NAME</a></li>
+ <li><a href="#synopsis">SYNOPSIS</a></li>
+ <li><a href="#description">DESCRIPTION</a></li>
+ <li><a href="#examples">EXAMPLES</a></li>
+ <li><a href="#options">OPTIONS</a></li>
+ <li><a href="#components">COMPONENTS</a></li>
+ <li><a href="#exit_status">EXIT STATUS</a></li>
+ <li><a href="#authors">AUTHORS</a></li>
+</ul>
+
+-->
+
+
+</div>
+<!-- INDEX END -->
+
+<p>
+</p>
+<hr />
+<h1><a name="name">NAME</a></h1>
+<p>llvm-config - Print LLVM compilation options</p>
+<p>
+</p>
+<hr />
+<h1><a name="synopsis">SYNOPSIS</a></h1>
+<p><strong>llvm-config</strong> <em>option</em> [<em>components</em>...]</p>
+<p>
+</p>
+<hr />
+<h1><a name="description">DESCRIPTION</a></h1>
+<p><strong>llvm-config</strong> makes it easier to build applications that use LLVM. It can
+print the compiler flags, linker flags and object libraries needed to link
+against LLVM.</p>
+<p>
+</p>
+<hr />
+<h1><a name="examples">EXAMPLES</a></h1>
+<p>To link against the JIT:</p>
+<pre>
+ g++ `llvm-config --cxxflags` -o HowToUseJIT.o -c HowToUseJIT.cpp
+ g++ `llvm-config --ldflags` -o HowToUseJIT HowToUseJIT.o \
+ `llvm-config --libs engine bcreader scalaropts`</pre>
+<p>
+</p>
+<hr />
+<h1><a name="options">OPTIONS</a></h1>
+<dl>
+<dt><strong><a name="version" class="item"><strong>--version</strong></a></strong></dt>
+
+<dd>
+<p>Print the version number of LLVM.</p>
+</dd>
+<dt><strong><a name="help" class="item"><strong>-help</strong></a></strong></dt>
+
+<dd>
+<p>Print a summary of <strong>llvm-config</strong> arguments.</p>
+</dd>
+<dt><strong><a name="prefix" class="item"><strong>--prefix</strong></a></strong></dt>
+
+<dd>
+<p>Print the installation prefix for LLVM.</p>
+</dd>
+<dt><strong><a name="src_root" class="item"><strong>--src-root</strong></a></strong></dt>
+
+<dd>
+<p>Print the source root from which LLVM was built.</p>
+</dd>
+<dt><strong><a name="obj_root" class="item"><strong>--obj-root</strong></a></strong></dt>
+
+<dd>
+<p>Print the object root used to build LLVM.</p>
+</dd>
+<dt><strong><a name="bindir" class="item"><strong>--bindir</strong></a></strong></dt>
+
+<dd>
+<p>Print the installation directory for LLVM binaries.</p>
+</dd>
+<dt><strong><a name="includedir" class="item"><strong>--includedir</strong></a></strong></dt>
+
+<dd>
+<p>Print the installation directory for LLVM headers.</p>
+</dd>
+<dt><strong><a name="libdir" class="item"><strong>--libdir</strong></a></strong></dt>
+
+<dd>
+<p>Print the installation directory for LLVM libraries.</p>
+</dd>
+<dt><strong><a name="cxxflags" class="item"><strong>--cxxflags</strong></a></strong></dt>
+
+<dd>
+<p>Print the C++ compiler flags needed to use LLVM headers.</p>
+</dd>
+<dt><strong><a name="ldflags" class="item"><strong>--ldflags</strong></a></strong></dt>
+
+<dd>
+<p>Print the flags needed to link against LLVM libraries.</p>
+</dd>
+<dt><strong><a name="libs" class="item"><strong>--libs</strong></a></strong></dt>
+
+<dd>
+<p>Print all the libraries needed to link against the specified LLVM
+<em>components</em>, including any dependencies.</p>
+</dd>
+<dt><strong><a name="libnames" class="item"><strong>--libnames</strong></a></strong></dt>
+
+<dd>
+<p>Similar to <strong>--libs</strong>, but prints the bare filenames of the libraries
+without <strong>-l</strong> or pathnames. Useful for linking against a not-yet-installed
+copy of LLVM.</p>
+</dd>
+<dt><strong><a name="libfiles" class="item"><strong>--libfiles</strong></a></strong></dt>
+
+<dd>
+<p>Similar to <strong>--libs</strong>, but print the full path to each library file. This is
+useful when creating makefile dependencies, to ensure that a tool is relinked if
+any library it uses changes.</p>
+</dd>
+<dt><strong><a name="components" class="item"><strong>--components</strong></a></strong></dt>
+
+<dd>
+<p>Print all valid component names.</p>
+</dd>
+<dt><strong><a name="targets_built" class="item"><strong>--targets-built</strong></a></strong></dt>
+
+<dd>
+<p>Print the component names for all targets supported by this copy of LLVM.</p>
+</dd>
+<dt><strong><a name="build_mode" class="item"><strong>--build-mode</strong></a></strong></dt>
+
+<dd>
+<p>Print the build mode used when LLVM was built (e.g. Debug or Release)</p>
+</dd>
+</dl>
+<p>
+</p>
+<hr />
+<h1><a name="components">COMPONENTS</a></h1>
+<p>To print a list of all available components, run <strong>llvm-config
+--components</strong>. In most cases, components correspond directly to LLVM
+libraries. Useful "virtual" components include:</p>
+<dl>
+<dt><strong><a name="all" class="item"><strong>all</strong></a></strong></dt>
+
+<dd>
+<p>Includes all LLVM libaries. The default if no components are specified.</p>
+</dd>
+<dt><strong><a name="backend" class="item"><strong>backend</strong></a></strong></dt>
+
+<dd>
+<p>Includes either a native backend or the C backend.</p>
+</dd>
+<dt><strong><a name="engine" class="item"><strong>engine</strong></a></strong></dt>
+
+<dd>
+<p>Includes either a native JIT or the bitcode interpreter.</p>
+</dd>
+</dl>
+<p>
+</p>
+<hr />
+<h1><a name="exit_status">EXIT STATUS</a></h1>
+<p>If <strong>llvm-config</strong> succeeds, it will exit with 0. Otherwise, if an error
+occurs, it will exit with a non-zero value.</p>
+<p>
+</p>
+<hr />
+<h1><a name="authors">AUTHORS</a></h1>
+<p>Maintained by the LLVM Team (<a href="http://llvm.org/">http://llvm.org/</a>).</p>
+
+</body>
+
+</html>
Added: www-releases/trunk/3.0/docs/CommandGuide/html/llvm-diff.html
URL: http://llvm.org/viewvc/llvm-project/www-releases/trunk/3.0/docs/CommandGuide/html/llvm-diff.html?rev=145591&view=auto
==============================================================================
--- www-releases/trunk/3.0/docs/CommandGuide/html/llvm-diff.html (added)
+++ www-releases/trunk/3.0/docs/CommandGuide/html/llvm-diff.html Thu Dec 1 11:44:59 2011
@@ -0,0 +1,89 @@
+<?xml version="1.0" ?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+<title>llvm-diff</title>
+<link rel="stylesheet" href="manpage.css" type="text/css" />
+<meta http-equiv="content-type" content="text/html; charset=utf-8" />
+<link rev="made" href="mailto:root at localhost" />
+</head>
+
+<body>
+
+
+<!-- INDEX BEGIN -->
+<div name="index">
+<p><a name="__index__"></a></p>
+<!--
+
+<ul>
+
+ <li><a href="#name">NAME</a></li>
+ <li><a href="#synopsis">SYNOPSIS</a></li>
+ <li><a href="#description">DESCRIPTION</a></li>
+ <li><a href="#exit_status">EXIT STATUS</a></li>
+ <li><a href="#bugs">BUGS</a></li>
+ <li><a href="#authors">AUTHORS</a></li>
+</ul>
+
+-->
+
+
+</div>
+<!-- INDEX END -->
+
+<p>
+</p>
+<hr />
+<h1><a name="name">NAME</a></h1>
+<p>llvm-diff - LLVM structural 'diff'</p>
+<p>
+</p>
+<hr />
+<h1><a name="synopsis">SYNOPSIS</a></h1>
+<p><strong>llvm-diff</strong> [<em>options</em>] <em>module 1</em> <em>module 2</em> [<em>global name ...</em>]</p>
+<p>
+</p>
+<hr />
+<h1><a name="description">DESCRIPTION</a></h1>
+<p><strong>llvm-diff</strong> compares the structure of two LLVM modules, primarily
+focusing on differences in function definitions. Insignificant
+differences, such as changes in the ordering of globals or in the
+names of local values, are ignored.</p>
+<p>An input module will be interpreted as an assembly file if its name
+ends in '.ll'; otherwise it will be read in as a bitcode file.</p>
+<p>If a list of global names is given, just the values with those names
+are compared; otherwise, all global values are compared, and
+diagnostics are produced for globals which only appear in one module
+or the other.</p>
+<p><strong>llvm-diff</strong> compares two functions by comparing their basic blocks,
+beginning with the entry blocks. If the terminators seem to match,
+then the corresponding successors are compared; otherwise they are
+ignored. This algorithm is very sensitive to changes in control flow,
+which tend to stop any downstream changes from being detected.</p>
+<p><strong>llvm-diff</strong> is intended as a debugging tool for writers of LLVM
+passes and frontends. It does not have a stable output format.</p>
+<p>
+</p>
+<hr />
+<h1><a name="exit_status">EXIT STATUS</a></h1>
+<p>If <strong>llvm-diff</strong> finds no differences between the modules, it will exit
+with 0 and produce no output. Otherwise it will exit with a non-zero
+value.</p>
+<p>
+</p>
+<hr />
+<h1><a name="bugs">BUGS</a></h1>
+<p>Many important differences, like changes in linkage or function
+attributes, are not diagnosed.</p>
+<p>Changes in memory behavior (for example, coalescing loads) can cause
+massive detected differences in blocks.</p>
+<p>
+</p>
+<hr />
+<h1><a name="authors">AUTHORS</a></h1>
+<p>Maintained by the LLVM Team (<a href="http://llvm.org/">http://llvm.org/</a>).</p>
+
+</body>
+
+</html>
Added: www-releases/trunk/3.0/docs/CommandGuide/html/llvm-dis.html
URL: http://llvm.org/viewvc/llvm-project/www-releases/trunk/3.0/docs/CommandGuide/html/llvm-dis.html?rev=145591&view=auto
==============================================================================
--- www-releases/trunk/3.0/docs/CommandGuide/html/llvm-dis.html (added)
+++ www-releases/trunk/3.0/docs/CommandGuide/html/llvm-dis.html Thu Dec 1 11:44:59 2011
@@ -0,0 +1,103 @@
+<?xml version="1.0" ?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+<title>llvm-dis</title>
+<link rel="stylesheet" href="manpage.css" type="text/css" />
+<meta http-equiv="content-type" content="text/html; charset=utf-8" />
+<link rev="made" href="mailto:root at localhost" />
+</head>
+
+<body>
+
+
+<!-- INDEX BEGIN -->
+<div name="index">
+<p><a name="__index__"></a></p>
+<!--
+
+<ul>
+
+ <li><a href="#name">NAME</a></li>
+ <li><a href="#synopsis">SYNOPSIS</a></li>
+ <li><a href="#description">DESCRIPTION</a></li>
+ <li><a href="#options">OPTIONS</a></li>
+ <li><a href="#exit_status">EXIT STATUS</a></li>
+ <li><a href="#see_also">SEE ALSO</a></li>
+ <li><a href="#authors">AUTHORS</a></li>
+</ul>
+
+-->
+
+
+</div>
+<!-- INDEX END -->
+
+<p>
+</p>
+<hr />
+<h1><a name="name">NAME</a></h1>
+<p>llvm-dis - LLVM disassembler</p>
+<p>
+</p>
+<hr />
+<h1><a name="synopsis">SYNOPSIS</a></h1>
+<p><strong>llvm-dis</strong> [<em>options</em>] [<em>filename</em>]</p>
+<p>
+</p>
+<hr />
+<h1><a name="description">DESCRIPTION</a></h1>
+<p>The <strong>llvm-dis</strong> command is the LLVM disassembler. It takes an LLVM
+bitcode file and converts it into human-readable LLVM assembly language.</p>
+<p>If filename is omitted or specified as <code>-</code>, <strong>llvm-dis</strong> reads its
+input from standard input.</p>
+<p>If the input is being read from standard input, then <strong>llvm-dis</strong>
+will send its output to standard output by default. Otherwise, the
+output will be written to a file named after the input file, with
+a <code>.ll</code> suffix added (any existing <code>.bc</code> suffix will first be
+removed). You can override the choice of output file using the
+<strong>-o</strong> option.</p>
+<p>
+</p>
+<hr />
+<h1><a name="options">OPTIONS</a></h1>
+<dl>
+<dt><strong><a name="f" class="item"><strong>-f</strong></a></strong></dt>
+
+<dd>
+<p>Enable binary output on terminals. Normally, <strong>llvm-dis</strong> will refuse to
+write raw bitcode output if the output stream is a terminal. With this option,
+<strong>llvm-dis</strong> will write raw bitcode regardless of the output device.</p>
+</dd>
+<dt><strong><a name="help" class="item"><strong>-help</strong></a></strong></dt>
+
+<dd>
+<p>Print a summary of command line options.</p>
+</dd>
+<dt><strong><a name="o_filename" class="item"><strong>-o</strong> <em class="file">filename</em></a></strong></dt>
+
+<dd>
+<p>Specify the output file name. If <em class="file">filename</em> is -, then the output is sent
+to standard output.</p>
+</dd>
+</dl>
+<p>
+</p>
+<hr />
+<h1><a name="exit_status">EXIT STATUS</a></h1>
+<p>If <strong>llvm-dis</strong> succeeds, it will exit with 0. Otherwise, if an error
+occurs, it will exit with a non-zero value.</p>
+<p>
+</p>
+<hr />
+<h1><a name="see_also">SEE ALSO</a></h1>
+<p><a href="././llvm-as.html">llvm-as</a></p>
+<p>
+</p>
+<hr />
+<h1><a name="authors">AUTHORS</a></h1>
+<p>Maintained by the LLVM Team (<a href="http://llvm.org/">http://llvm.org/</a>).</p>
+
+</body>
+
+</html>
Added: www-releases/trunk/3.0/docs/CommandGuide/html/llvm-extract.html
URL: http://llvm.org/viewvc/llvm-project/www-releases/trunk/3.0/docs/CommandGuide/html/llvm-extract.html?rev=145591&view=auto
==============================================================================
--- www-releases/trunk/3.0/docs/CommandGuide/html/llvm-extract.html (added)
+++ www-releases/trunk/3.0/docs/CommandGuide/html/llvm-extract.html Thu Dec 1 11:44:59 2011
@@ -0,0 +1,133 @@
+<?xml version="1.0" ?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+<title>llvm-extract</title>
+<link rel="stylesheet" href="manpage.css" type="text/css" />
+<meta http-equiv="content-type" content="text/html; charset=utf-8" />
+<link rev="made" href="mailto:root at localhost" />
+</head>
+
+<body>
+
+
+<!-- INDEX BEGIN -->
+<div name="index">
+<p><a name="__index__"></a></p>
+<!--
+
+<ul>
+
+ <li><a href="#name">NAME</a></li>
+ <li><a href="#synopsis">SYNOPSIS</a></li>
+ <li><a href="#description">DESCRIPTION</a></li>
+ <li><a href="#options">OPTIONS</a></li>
+ <li><a href="#exit_status">EXIT STATUS</a></li>
+ <li><a href="#see_also">SEE ALSO</a></li>
+ <li><a href="#authors">AUTHORS</a></li>
+</ul>
+
+-->
+
+
+</div>
+<!-- INDEX END -->
+
+<p>
+</p>
+<hr />
+<h1><a name="name">NAME</a></h1>
+<p>llvm-extract - extract a function from an LLVM module</p>
+<p>
+</p>
+<hr />
+<h1><a name="synopsis">SYNOPSIS</a></h1>
+<p><strong>llvm-extract</strong> [<em>options</em>] <strong>--func</strong> <em>function-name</em> [<em>filename</em>]</p>
+<p>
+</p>
+<hr />
+<h1><a name="description">DESCRIPTION</a></h1>
+<p>The <strong>llvm-extract</strong> command takes the name of a function and extracts it from
+the specified LLVM bitcode file. It is primarily used as a debugging tool to
+reduce test cases from larger programs that are triggering a bug.</p>
+<p>In addition to extracting the bitcode of the specified function,
+<strong>llvm-extract</strong> will also remove unreachable global variables, prototypes, and
+unused types.</p>
+<p>The <strong>llvm-extract</strong> command reads its input from standard input if filename is
+omitted or if filename is -. The output is always written to standard output,
+unless the <strong>-o</strong> option is specified (see below).</p>
+<p>
+</p>
+<hr />
+<h1><a name="options">OPTIONS</a></h1>
+<dl>
+<dt><strong><a name="f" class="item"><strong>-f</strong></a></strong></dt>
+
+<dd>
+<p>Enable binary output on terminals. Normally, <strong>llvm-extract</strong> will refuse to
+write raw bitcode output if the output stream is a terminal. With this option,
+<strong>llvm-extract</strong> will write raw bitcode regardless of the output device.</p>
+</dd>
+<dt><strong><a name="func_function_name" class="item"><strong>--func</strong> <em>function-name</em></a></strong></dt>
+
+<dd>
+<p>Extract the function named <em>function-name</em> from the LLVM bitcode. May be
+specified multiple times to extract multiple functions at once.</p>
+</dd>
+<dt><strong><a name="rfunc_function_regular_expr" class="item"><strong>--rfunc</strong> <em>function-regular-expr</em></a></strong></dt>
+
+<dd>
+<p>Extract the function(s) matching <em>function-regular-expr</em> from the LLVM bitcode.
+All functions matching the regular expression will be extracted. May be
+specified multiple times.</p>
+</dd>
+<dt><strong><a name="glob_global_name" class="item"><strong>--glob</strong> <em>global-name</em></a></strong></dt>
+
+<dd>
+<p>Extract the global variable named <em>global-name</em> from the LLVM bitcode. May be
+specified multiple times to extract multiple global variables at once.</p>
+</dd>
+<dt><strong><a name="rglob_glob_regular_expr" class="item"><strong>--rglob</strong> <em>glob-regular-expr</em></a></strong></dt>
+
+<dd>
+<p>Extract the global variable(s) matching <em>global-regular-expr</em> from the LLVM
+bitcode. All global variables matching the regular expression will be extracted.
+May be specified multiple times.</p>
+</dd>
+<dt><strong><a name="help" class="item"><strong>-help</strong></a></strong></dt>
+
+<dd>
+<p>Print a summary of command line options.</p>
+</dd>
+<dt><strong><a name="o_filename" class="item"><strong>-o</strong> <em>filename</em></a></strong></dt>
+
+<dd>
+<p>Specify the output filename. If filename is "-" (the default), then
+<strong>llvm-extract</strong> sends its output to standard output.</p>
+</dd>
+<dt><strong><a name="s" class="item"><strong>-S</strong></a></strong></dt>
+
+<dd>
+<p>Write output in LLVM intermediate language (instead of bitcode).</p>
+</dd>
+</dl>
+<p>
+</p>
+<hr />
+<h1><a name="exit_status">EXIT STATUS</a></h1>
+<p>If <strong>llvm-extract</strong> succeeds, it will exit with 0. Otherwise, if an error
+occurs, it will exit with a non-zero value.</p>
+<p>
+</p>
+<hr />
+<h1><a name="see_also">SEE ALSO</a></h1>
+<p><a href="././bugpoint.html">bugpoint</a></p>
+<p>
+</p>
+<hr />
+<h1><a name="authors">AUTHORS</a></h1>
+<p>Maintained by the LLVM Team (<a href="http://llvm.org/">http://llvm.org/</a>).</p>
+
+</body>
+
+</html>
Added: www-releases/trunk/3.0/docs/CommandGuide/html/llvm-ld.html
URL: http://llvm.org/viewvc/llvm-project/www-releases/trunk/3.0/docs/CommandGuide/html/llvm-ld.html?rev=145591&view=auto
==============================================================================
--- www-releases/trunk/3.0/docs/CommandGuide/html/llvm-ld.html (added)
+++ www-releases/trunk/3.0/docs/CommandGuide/html/llvm-ld.html Thu Dec 1 11:44:59 2011
@@ -0,0 +1,308 @@
+<?xml version="1.0" ?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+<title>llvm-ld</title>
+<link rel="stylesheet" href="manpage.css" type="text/css" />
+<meta http-equiv="content-type" content="text/html; charset=utf-8" />
+<link rev="made" href="mailto:root at localhost" />
+</head>
+
+<body>
+
+
+<!-- INDEX BEGIN -->
+<div name="index">
+<p><a name="__index__"></a></p>
+<!--
+
+<ul>
+
+ <li><a href="#name">NAME</a></li>
+ <li><a href="#synopsis">SYNOPSIS</a></li>
+ <li><a href="#description">DESCRIPTION</a></li>
+ <ul>
+
+ <li><a href="#search_order">Search Order</a></li>
+ <li><a href="#link_order">Link order</a></li>
+ <li><a href="#library_linkage">Library Linkage</a></li>
+ <li><a href="#native_code_generation">Native code generation</a></li>
+ </ul>
+
+ <li><a href="#options">OPTIONS</a></li>
+ <ul>
+
+ <li><a href="#general_options">General Options</a></li>
+ <li><a href="#input_output_options">Input/Output Options</a></li>
+ <li><a href="#optimization_options">Optimization Options</a></li>
+ </ul>
+
+ <li><a href="#exit_status">EXIT STATUS</a></li>
+ <li><a href="#environment">ENVIRONMENT</a></li>
+ <li><a href="#see_also">SEE ALSO</a></li>
+ <li><a href="#authors">AUTHORS</a></li>
+</ul>
+
+-->
+
+
+</div>
+<!-- INDEX END -->
+
+<p>
+</p>
+<hr />
+<h1><a name="name">NAME</a></h1>
+<p>llvm-ld - LLVM linker</p>
+<p>
+</p>
+<hr />
+<h1><a name="synopsis">SYNOPSIS</a></h1>
+<p><strong>llvm-ld</strong> <options> <files></p>
+<p>
+</p>
+<hr />
+<h1><a name="description">DESCRIPTION</a></h1>
+<p>The <strong>llvm-ld</strong> tool takes a set of LLVM bitcode files and links them
+together into a single LLVM bitcode file. The output bitcode file can be
+another bitcode file or an executable bitcode program. Using additional
+options, <strong>llvm-ld</strong> is able to produce native code executables.</p>
+<p>The <strong>llvm-ld</strong> tool is the main linker for LLVM. It is used to link together
+the output of LLVM front-end compilers and run "link time" optimizations (mostly
+the inter-procedural kind).</p>
+<p>The <strong>llvm-ld</strong> tools attempts to mimic the interface provided by the default
+system linker so that it can act as a <em>drop-in</em> replacement.</p>
+<p>
+</p>
+<h2><a name="search_order">Search Order</a></h2>
+<p>When looking for objects specified on the command line, <strong>llvm-ld</strong> will search
+for the object first in the current directory and then in the directory
+specified by the <strong>LLVM_LIB_SEARCH_PATH</strong> environment variable. If it cannot
+find the object, it fails.</p>
+<p>When looking for a library specified with the <strong>-l</strong> option, <strong>llvm-ld</strong> first
+attempts to load a file with that name from the current directory. If that
+fails, it looks for lib<em>library</em>.bc, lib<em>library</em>.a, or lib<em>library</em>.<em>shared
+library extension</em>, in that order, in each directory added to the library search
+path with the <strong>-L</strong> option. These directories are searched in the order they
+are specified. If the library cannot be located, then <strong>llvm-ld</strong> looks in the
+directory specified by the <strong>LLVM_LIB_SEARCH_PATH</strong> environment variable. If it
+does not find a library there, it fails.</p>
+<p>The <em>shared library extension</em> may be <em>.so</em>, <em>.dyld</em>, <em>.dll</em>, or something
+different, depending upon the system.</p>
+<p>The <strong>-L</strong> option is global. It does not matter where it is specified in the
+list of command line arguments; the directory is simply added to the search path
+and is applied to all libraries, preceding or succeeding, in the command line.</p>
+<p>
+</p>
+<h2><a name="link_order">Link order</a></h2>
+<p>All object and bitcode files are linked first in the order they were
+specified on the command line. All library files are linked next.
+Some libraries may not be linked into the object program; see below.</p>
+<p>
+</p>
+<h2><a name="library_linkage">Library Linkage</a></h2>
+<p>Object files and static bitcode objects are always linked into the output
+file. Library archives (.a files) load only the objects within the archive
+that define symbols needed by the output file. Hence, libraries should be
+listed after the object files and libraries which need them; otherwise, the
+library may not be linked in, and the dependent library will not have its
+undefined symbols defined.</p>
+<p>
+</p>
+<h2><a name="native_code_generation">Native code generation</a></h2>
+<p>The <strong>llvm-ld</strong> program has limited support for native code generation, when
+using the <strong>-native</strong> or <strong>-native-cbe</strong> options. Native code generation is
+performed by converting the linked bitcode into native assembly (.s) or C code
+and running the system compiler (typically gcc) on the result.</p>
+<p>
+</p>
+<hr />
+<h1><a name="options">OPTIONS</a></h1>
+<p>
+</p>
+<h2><a name="general_options">General Options</a></h2>
+<dl>
+<dt><strong><a name="help" class="item"><strong>-help</strong></a></strong></dt>
+
+<dd>
+<p>Print a summary of command line options.</p>
+</dd>
+<dt><strong><a name="v" class="item"><strong>-v</strong></a></strong></dt>
+
+<dd>
+<p>Specifies verbose mode. In this mode the linker will print additional
+information about the actions it takes, programs it executes, etc.</p>
+</dd>
+<dt><strong><a name="stats" class="item"><strong>-stats</strong></a></strong></dt>
+
+<dd>
+<p>Print statistics.</p>
+</dd>
+<dt><strong><a name="time_passes" class="item"><strong>-time-passes</strong></a></strong></dt>
+
+<dd>
+<p>Record the amount of time needed for each pass and print it to standard
+error.</p>
+</dd>
+</dl>
+<p>
+</p>
+<h2><a name="input_output_options">Input/Output Options</a></h2>
+<dl>
+<dt><strong><a name="o_filename" class="item"><strong>-o</strong> <em class="file">filename</em></a></strong></dt>
+
+<dd>
+<p>This overrides the default output file and specifies the name of the file that
+should be generated by the linker. By default, <strong>llvm-ld</strong> generates a file named
+<em class="file">a.out</em> for compatibility with <strong>ld</strong>. The output will be written to
+<em class="file">filename</em>.</p>
+</dd>
+<dt><strong><a name="b_filename" class="item"><strong>-b</strong> <em class="file">filename</em></a></strong></dt>
+
+<dd>
+<p>This option can be used to override the output bitcode file name. By default,
+the name of the bitcode output file is one more ".bc" suffix added to the name
+specified by <strong>-o filename</strong> option.</p>
+</dd>
+<dt><strong><a name="lname" class="item"><strong>-l</strong><em class="file">name</em></a></strong></dt>
+
+<dd>
+<p>This option specifies the <em class="file">name</em> of a library to search when resolving symbols
+for the program. Only the base name should be specified as <em class="file">name</em>, without a
+<em class="file">lib</em> prefix or any suffix.</p>
+</dd>
+<dt><strong><a name="lpath" class="item"><strong>-L</strong><em class="file">Path</em></a></strong></dt>
+
+<dd>
+<p>This option tells <strong>llvm-ld</strong> to look in <em class="file">Path</em> to find any library subsequently
+specified with the <strong>-l</strong> option. The paths will be searched in the order in
+which they are specified on the command line. If the library is still not found,
+a small set of system specific directories will also be searched. Note that
+libraries specified with the <strong>-l</strong> option that occur <em>before</em> any <strong>-L</strong> options
+will not search the paths given by the <strong>-L</strong> options following it.</p>
+</dd>
+<dt><strong><a name="link_as_library" class="item"><strong>-link-as-library</strong></a></strong></dt>
+
+<dd>
+<p>Link the bitcode files together as a library, not an executable. In this mode,
+undefined symbols will be permitted.</p>
+</dd>
+<dt><strong><a name="r" class="item"><strong>-r</strong></a></strong></dt>
+
+<dd>
+<p>An alias for -link-as-library.</p>
+</dd>
+<dt><strong><a name="native" class="item"><strong>-native</strong></a></strong></dt>
+
+<dd>
+<p>Generate a native machine code executable.</p>
+<p>When generating native executables, <strong>llvm-ld</strong> first checks for a bitcode
+version of the library and links it in, if necessary. If the library is
+missing, <strong>llvm-ld</strong> skips it. Then, <strong>llvm-ld</strong> links in the same
+libraries as native code.</p>
+<p>In this way, <strong>llvm-ld</strong> should be able to link in optimized bitcode
+subsets of common libraries and then link in any part of the library that
+hasn't been converted to bitcode.</p>
+</dd>
+<dt><strong><a name="native_cbe" class="item"><strong>-native-cbe</strong></a></strong></dt>
+
+<dd>
+<p>Generate a native machine code executable with the LLVM C backend.</p>
+<pre>
+
+This option is identical to the B<-native> option, but uses the
+C backend to generate code for the program instead of an LLVM native
+code generator.</pre>
+</dd>
+</dl>
+<p>
+</p>
+<h2><a name="optimization_options">Optimization Options</a></h2>
+<dl>
+<dt><strong><a name="disable_inlining" class="item"><strong>-disable-inlining</strong></a></strong></dt>
+
+<dd>
+<p>Do not run the inlining pass. Functions will not be inlined into other
+functions.</p>
+</dd>
+<dt><strong><a name="disable_opt" class="item"><strong>-disable-opt</strong></a></strong></dt>
+
+<dd>
+<p>Completely disable optimization.</p>
+</dd>
+<dt><strong><a name="disable_internalize" class="item"><strong>-disable-internalize</strong></a></strong></dt>
+
+<dd>
+<p>Do not mark all symbols as internal.</p>
+</dd>
+<dt><strong><a name="verify_each" class="item"><strong>-verify-each</strong></a></strong></dt>
+
+<dd>
+<p>Run the verification pass after each of the passes to verify intermediate
+results.</p>
+</dd>
+<dt><strong><a name="strip_all" class="item"><strong>-strip-all</strong></a></strong></dt>
+
+<dd>
+<p>Strip all debug and symbol information from the executable to make it smaller.</p>
+</dd>
+<dt><strong><a name="strip_debug" class="item"><strong>-strip-debug</strong></a></strong></dt>
+
+<dd>
+<p>Strip all debug information from the executable to make it smaller.</p>
+</dd>
+<dt><strong><a name="s" class="item"><strong>-s</strong></a></strong></dt>
+
+<dd>
+<p>An alias for <strong>-strip-all</strong>.</p>
+</dd>
+<dt><strong><a name="s" class="item"><strong>-S</strong></a></strong></dt>
+
+<dd>
+<p>An alias for <strong>-strip-debug</strong>.</p>
+</dd>
+<dt><strong><a name="export_dynamic" class="item"><strong>-export-dynamic</strong></a></strong></dt>
+
+<dd>
+<p>An alias for <strong>-disable-internalize</strong></p>
+</dd>
+<dt><strong><a name="post_link_optpath" class="item"><strong>-post-link-opt</strong><em class="file">Path</em></a></strong></dt>
+
+<dd>
+<p>Run post-link optimization program. After linking is completed a bitcode file
+will be generated. It will be passed to the program specified by <em class="file">Path</em> as the
+first argument. The second argument to the program will be the name of a
+temporary file into which the program should place its optimized output. For
+example, the "no-op optimization" would be a simple shell script:</p>
+<pre>
+ #!/bin/bash
+ cp $1 $2</pre>
+</dd>
+</dl>
+<p>
+</p>
+<hr />
+<h1><a name="exit_status">EXIT STATUS</a></h1>
+<p>If <strong>llvm-ld</strong> succeeds, it will exit with 0 return code. If an error occurs,
+it will exit with a non-zero return code.</p>
+<p>
+</p>
+<hr />
+<h1><a name="environment">ENVIRONMENT</a></h1>
+<p>The <code>LLVM_LIB_SEARCH_PATH</code> environment variable is used to find bitcode
+libraries. Any paths specified in this variable will be searched after the <code>-L</code>
+options.</p>
+<p>
+</p>
+<hr />
+<h1><a name="see_also">SEE ALSO</a></h1>
+<p><a href="././llvm-link.html">llvm-link</a></p>
+<p>
+</p>
+<hr />
+<h1><a name="authors">AUTHORS</a></h1>
+<p>Maintained by the LLVM Team (<a href="http://llvm.org/">http://llvm.org/</a>).</p>
+
+</body>
+
+</html>
Added: www-releases/trunk/3.0/docs/CommandGuide/html/llvm-link.html
URL: http://llvm.org/viewvc/llvm-project/www-releases/trunk/3.0/docs/CommandGuide/html/llvm-link.html?rev=145591&view=auto
==============================================================================
--- www-releases/trunk/3.0/docs/CommandGuide/html/llvm-link.html (added)
+++ www-releases/trunk/3.0/docs/CommandGuide/html/llvm-link.html Thu Dec 1 11:44:59 2011
@@ -0,0 +1,127 @@
+<?xml version="1.0" ?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+<title>llvm-link</title>
+<link rel="stylesheet" href="manpage.css" type="text/css" />
+<meta http-equiv="content-type" content="text/html; charset=utf-8" />
+<link rev="made" href="mailto:root at localhost" />
+</head>
+
+<body>
+
+
+<!-- INDEX BEGIN -->
+<div name="index">
+<p><a name="__index__"></a></p>
+<!--
+
+<ul>
+
+ <li><a href="#name">NAME</a></li>
+ <li><a href="#synopsis">SYNOPSIS</a></li>
+ <li><a href="#description">DESCRIPTION</a></li>
+ <li><a href="#options">OPTIONS</a></li>
+ <li><a href="#exit_status">EXIT STATUS</a></li>
+ <li><a href="#see_also">SEE ALSO</a></li>
+ <li><a href="#authors">AUTHORS</a></li>
+</ul>
+
+-->
+
+
+</div>
+<!-- INDEX END -->
+
+<p>
+</p>
+<hr />
+<h1><a name="name">NAME</a></h1>
+<p>llvm-link - LLVM linker</p>
+<p>
+</p>
+<hr />
+<h1><a name="synopsis">SYNOPSIS</a></h1>
+<p><strong>llvm-link</strong> [<em>options</em>] <em>filename ...</em></p>
+<p>
+</p>
+<hr />
+<h1><a name="description">DESCRIPTION</a></h1>
+<p><strong>llvm-link</strong> takes several LLVM bitcode files and links them together into a
+single LLVM bitcode file. It writes the output file to standard output, unless
+the <strong>-o</strong> option is used to specify a filename.</p>
+<p><strong>llvm-link</strong> attempts to load the input files from the current directory. If
+that fails, it looks for each file in each of the directories specified by the
+<strong>-L</strong> options on the command line. The library search paths are global; each
+one is searched for every input file if necessary. The directories are searched
+in the order they were specified on the command line.</p>
+<p>
+</p>
+<hr />
+<h1><a name="options">OPTIONS</a></h1>
+<dl>
+<dt><strong><a name="l_directory" class="item"><strong>-L</strong> <em class="file">directory</em></a></strong></dt>
+
+<dd>
+<p>Add the specified <em class="file">directory</em> to the library search path. When looking for
+libraries, <strong>llvm-link</strong> will look in path name for libraries. This option can be
+specified multiple times; <strong>llvm-link</strong> will search inside these directories in
+the order in which they were specified on the command line.</p>
+</dd>
+<dt><strong><a name="f" class="item"><strong>-f</strong></a></strong></dt>
+
+<dd>
+<p>Enable binary output on terminals. Normally, <strong>llvm-link</strong> will refuse to
+write raw bitcode output if the output stream is a terminal. With this option,
+<strong>llvm-link</strong> will write raw bitcode regardless of the output device.</p>
+</dd>
+<dt><strong><a name="o_filename" class="item"><strong>-o</strong> <em class="file">filename</em></a></strong></dt>
+
+<dd>
+<p>Specify the output file name. If <em class="file">filename</em> is <code>-</code>, then <strong>llvm-link</strong> will
+write its output to standard output.</p>
+</dd>
+<dt><strong><a name="s" class="item"><strong>-S</strong></a></strong></dt>
+
+<dd>
+<p>Write output in LLVM intermediate language (instead of bitcode).</p>
+</dd>
+<dt><strong><a name="d" class="item"><strong>-d</strong></a></strong></dt>
+
+<dd>
+<p>If specified, <strong>llvm-link</strong> prints a human-readable version of the output
+bitcode file to standard error.</p>
+</dd>
+<dt><strong><a name="help" class="item"><strong>-help</strong></a></strong></dt>
+
+<dd>
+<p>Print a summary of command line options.</p>
+</dd>
+<dt><strong><a name="v" class="item"><strong>-v</strong></a></strong></dt>
+
+<dd>
+<p>Verbose mode. Print information about what <strong>llvm-link</strong> is doing. This
+typically includes a message for each bitcode file linked in and for each
+library found.</p>
+</dd>
+</dl>
+<p>
+</p>
+<hr />
+<h1><a name="exit_status">EXIT STATUS</a></h1>
+<p>If <strong>llvm-link</strong> succeeds, it will exit with 0. Otherwise, if an error
+occurs, it will exit with a non-zero value.</p>
+<p>
+</p>
+<hr />
+<h1><a name="see_also">SEE ALSO</a></h1>
+<p><em>gccld</em></p>
+<p>
+</p>
+<hr />
+<h1><a name="authors">AUTHORS</a></h1>
+<p>Maintained by the LLVM Team (<a href="http://llvm.org/">http://llvm.org/</a>).</p>
+
+</body>
+
+</html>
Added: www-releases/trunk/3.0/docs/CommandGuide/html/llvm-nm.html
URL: http://llvm.org/viewvc/llvm-project/www-releases/trunk/3.0/docs/CommandGuide/html/llvm-nm.html?rev=145591&view=auto
==============================================================================
--- www-releases/trunk/3.0/docs/CommandGuide/html/llvm-nm.html (added)
+++ www-releases/trunk/3.0/docs/CommandGuide/html/llvm-nm.html Thu Dec 1 11:44:59 2011
@@ -0,0 +1,176 @@
+<?xml version="1.0" ?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+<title>llvm-nm</title>
+<link rel="stylesheet" href="manpage.css" type="text/css" />
+<meta http-equiv="content-type" content="text/html; charset=utf-8" />
+<link rev="made" href="mailto:root at localhost" />
+</head>
+
+<body>
+
+
+<!-- INDEX BEGIN -->
+<div name="index">
+<p><a name="__index__"></a></p>
+<!--
+
+<ul>
+
+ <li><a href="#name">NAME</a></li>
+ <li><a href="#synopsis">SYNOPSIS</a></li>
+ <li><a href="#description">DESCRIPTION</a></li>
+ <li><a href="#options">OPTIONS</a></li>
+ <li><a href="#bugs">BUGS</a></li>
+ <li><a href="#exit_status">EXIT STATUS</a></li>
+ <li><a href="#see_also">SEE ALSO</a></li>
+ <li><a href="#author">AUTHOR</a></li>
+</ul>
+
+-->
+
+
+</div>
+<!-- INDEX END -->
+
+<p>
+</p>
+<hr />
+<h1><a name="name">NAME</a></h1>
+<p>llvm-nm - list LLVM bitcode file's symbol table</p>
+<p>
+</p>
+<hr />
+<h1><a name="synopsis">SYNOPSIS</a></h1>
+<p><strong>llvm-nm</strong> [<em>options</em>] [<em>filenames...</em>]</p>
+<p>
+</p>
+<hr />
+<h1><a name="description">DESCRIPTION</a></h1>
+<p>The <strong>llvm-nm</strong> utility lists the names of symbols from the LLVM bitcode files,
+or <strong>ar</strong> archives containing LLVM bitcode files, named on the command line.
+Each symbol is listed along with some simple information about its provenance.
+If no file name is specified, or <em>-</em> is used as a file name, <strong>llvm-nm</strong> will
+process a bitcode file on its standard input stream.</p>
+<p><strong>llvm-nm</strong>'s default output format is the traditional BSD <strong>nm</strong> output format.
+Each such output record consists of an (optional) 8-digit hexadecimal address,
+followed by a type code character, followed by a name, for each symbol. One
+record is printed per line; fields are separated by spaces. When the address is
+omitted, it is replaced by 8 spaces.</p>
+<p>Type code characters currently supported, and their meanings, are as follows:</p>
+<dl>
+<dt><strong><a name="u" class="item">U</a></strong></dt>
+
+<dd>
+<p>Named object is referenced but undefined in this bitcode file</p>
+</dd>
+<dt><strong><a name="c" class="item">C</a></strong></dt>
+
+<dd>
+<p>Common (multiple definitions link together into one def)</p>
+</dd>
+<dt><strong><a name="w" class="item">W</a></strong></dt>
+
+<dd>
+<p>Weak reference (multiple definitions link together into zero or one definitions)</p>
+</dd>
+<dt><strong><a name="t" class="item">t</a></strong></dt>
+
+<dd>
+<p>Local function (text) object</p>
+</dd>
+<dt><strong><a name="t" class="item">T</a></strong></dt>
+
+<dd>
+<p>Global function (text) object</p>
+</dd>
+<dt><strong><a name="d" class="item">d</a></strong></dt>
+
+<dd>
+<p>Local data object</p>
+</dd>
+<dt><strong><a name="d" class="item">D</a></strong></dt>
+
+<dd>
+<p>Global data object</p>
+</dd>
+<dt><strong><a name="" class="item">?</a></strong></dt>
+
+<dd>
+<p>Something unrecognizable</p>
+</dd>
+</dl>
+<p>Because LLVM bitcode files typically contain objects that are not considered to
+have addresses until they are linked into an executable image or dynamically
+compiled "just-in-time", <strong>llvm-nm</strong> does not print an address for any symbol,
+even symbols which are defined in the bitcode file.</p>
+<p>
+</p>
+<hr />
+<h1><a name="options">OPTIONS</a></h1>
+<dl>
+<dt><strong><a name="p" class="item"><strong>-P</strong></a></strong></dt>
+
+<dd>
+<p>Use POSIX.2 output format. Alias for <strong>--format=posix</strong>.</p>
+</dd>
+<dt><strong><a name="b" class="item"><strong>-B</strong> (default)</a></strong></dt>
+
+<dd>
+<p>Use BSD output format. Alias for <strong>--format=bsd</strong>.</p>
+</dd>
+<dt><strong><a name="help" class="item"><strong>-help</strong></a></strong></dt>
+
+<dd>
+<p>Print a summary of command-line options and their meanings.</p>
+</dd>
+<dt><strong><a name="defined_only" class="item"><strong>--defined-only</strong></a></strong></dt>
+
+<dd>
+<p>Print only symbols defined in this bitcode file (as opposed to
+symbols which may be referenced by objects in this file, but not
+defined in this file.)</p>
+</dd>
+<dt><strong><a name="extern_only_g" class="item"><strong>--extern-only</strong>, <strong>-g</strong></a></strong></dt>
+
+<dd>
+<p>Print only symbols whose definitions are external; that is, accessible
+from other bitcode files.</p>
+</dd>
+<dt><strong><a name="undefined_only_u" class="item"><strong>--undefined-only</strong>, <strong>-u</strong></a></strong></dt>
+
+<dd>
+<p>Print only symbols referenced but not defined in this bitcode file.</p>
+</dd>
+<dt><strong><a name="format_fmt_f" class="item"><strong>--format=</strong><em>fmt</em>, <strong>-f</strong></a></strong></dt>
+
+<dd>
+<p>Select an output format; <em>fmt</em> may be <em>sysv</em>, <em>posix</em>, or <em>bsd</em>. The
+default is <em>bsd</em>.</p>
+</dd>
+</dl>
+<p>
+</p>
+<hr />
+<h1><a name="bugs">BUGS</a></h1>
+<p><strong>llvm-nm</strong> cannot demangle C++ mangled names, like GNU <strong>nm</strong> can.</p>
+<p>
+</p>
+<hr />
+<h1><a name="exit_status">EXIT STATUS</a></h1>
+<p><strong>llvm-nm</strong> exits with an exit code of zero.</p>
+<p>
+</p>
+<hr />
+<h1><a name="see_also">SEE ALSO</a></h1>
+<p><a href="././llvm-dis.html">llvm-dis</a>, <code>ar(1)</code>, <code>nm(1)</code></p>
+<p>
+</p>
+<hr />
+<h1><a name="author">AUTHOR</a></h1>
+<p>Maintained by the LLVM Team (<a href="http://llvm.org/">http://llvm.org/</a>).</p>
+
+</body>
+
+</html>
Added: www-releases/trunk/3.0/docs/CommandGuide/html/llvm-prof.html
URL: http://llvm.org/viewvc/llvm-project/www-releases/trunk/3.0/docs/CommandGuide/html/llvm-prof.html?rev=145591&view=auto
==============================================================================
--- www-releases/trunk/3.0/docs/CommandGuide/html/llvm-prof.html (added)
+++ www-releases/trunk/3.0/docs/CommandGuide/html/llvm-prof.html Thu Dec 1 11:44:59 2011
@@ -0,0 +1,99 @@
+<?xml version="1.0" ?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+<title>llvm-prof</title>
+<link rel="stylesheet" href="manpage.css" type="text/css" />
+<meta http-equiv="content-type" content="text/html; charset=utf-8" />
+<link rev="made" href="mailto:root at localhost" />
+</head>
+
+<body>
+
+
+<!-- INDEX BEGIN -->
+<div name="index">
+<p><a name="__index__"></a></p>
+<!--
+
+<ul>
+
+ <li><a href="#name">NAME</a></li>
+ <li><a href="#synopsis">SYNOPSIS</a></li>
+ <li><a href="#description">DESCRIPTION</a></li>
+ <li><a href="#options">OPTIONS</a></li>
+ <li><a href="#exit_status">EXIT STATUS</a></li>
+ <li><a href="#author">AUTHOR</a></li>
+</ul>
+
+-->
+
+
+</div>
+<!-- INDEX END -->
+
+<p>
+</p>
+<hr />
+<h1><a name="name">NAME</a></h1>
+<p>llvm-prof - print execution profile of LLVM program</p>
+<p>
+</p>
+<hr />
+<h1><a name="synopsis">SYNOPSIS</a></h1>
+<p><strong>llvm-prof</strong> [<em>options</em>] [<em>bitcode file</em>] [<em>llvmprof.out</em>]</p>
+<p>
+</p>
+<hr />
+<h1><a name="description">DESCRIPTION</a></h1>
+<p>The <strong>llvm-prof</strong> tool reads in an <em class="file">llvmprof.out</em> file (which can
+optionally use a specific file with the third program argument), a bitcode file
+for the program, and produces a human readable report, suitable for determining
+where the program hotspots are.</p>
+<p>This program is often used in conjunction with the <em class="file">utils/profile.pl</em>
+script. This script automatically instruments a program, runs it with the JIT,
+then runs <strong>llvm-prof</strong> to format a report. To get more information about
+<em class="file">utils/profile.pl</em>, execute it with the <strong>-help</strong> option.</p>
+<p>
+</p>
+<hr />
+<h1><a name="options">OPTIONS</a></h1>
+<dl>
+<dt><strong><a name="annotated_llvm_or_a" class="item"><strong>--annotated-llvm</strong> or <strong>-A</strong></a></strong></dt>
+
+<dd>
+<p>In addition to the normal report printed, print out the code for the
+program, annotated with execution frequency information. This can be
+particularly useful when trying to visualize how frequently basic blocks
+are executed. This is most useful with basic block profiling
+information or better.</p>
+</dd>
+<dt><strong><a name="print_all_code" class="item"><strong>--print-all-code</strong></a></strong></dt>
+
+<dd>
+<p>Using this option enables the <strong>--annotated-llvm</strong> option, but it
+prints the entire module, instead of just the most commonly executed
+functions.</p>
+</dd>
+<dt><strong><a name="time_passes" class="item"><strong>--time-passes</strong></a></strong></dt>
+
+<dd>
+<p>Record the amount of time needed for each pass and print it to standard
+error.</p>
+</dd>
+</dl>
+<p>
+</p>
+<hr />
+<h1><a name="exit_status">EXIT STATUS</a></h1>
+<p><strong>llvm-prof</strong> returns 1 if it cannot load the bitcode file or the profile
+information. Otherwise, it exits with zero.</p>
+<p>
+</p>
+<hr />
+<h1><a name="author">AUTHOR</a></h1>
+<p><strong>llvm-prof</strong> is maintained by the LLVM Team (<a href="http://llvm.org/">http://llvm.org/</a>).</p>
+
+</body>
+
+</html>
Added: www-releases/trunk/3.0/docs/CommandGuide/html/llvm-ranlib.html
URL: http://llvm.org/viewvc/llvm-project/www-releases/trunk/3.0/docs/CommandGuide/html/llvm-ranlib.html?rev=145591&view=auto
==============================================================================
--- www-releases/trunk/3.0/docs/CommandGuide/html/llvm-ranlib.html (added)
+++ www-releases/trunk/3.0/docs/CommandGuide/html/llvm-ranlib.html Thu Dec 1 11:44:59 2011
@@ -0,0 +1,97 @@
+<?xml version="1.0" ?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+<title>llvm-ranlib</title>
+<link rel="stylesheet" href="manpage.css" type="text/css" />
+<meta http-equiv="content-type" content="text/html; charset=utf-8" />
+<link rev="made" href="mailto:root at localhost" />
+</head>
+
+<body>
+
+
+<!-- INDEX BEGIN -->
+<div name="index">
+<p><a name="__index__"></a></p>
+<!--
+
+<ul>
+
+ <li><a href="#name">NAME</a></li>
+ <li><a href="#synopsis">SYNOPSIS</a></li>
+ <li><a href="#description">DESCRIPTION</a></li>
+ <li><a href="#options">OPTIONS</a></li>
+ <li><a href="#exit_status">EXIT STATUS</a></li>
+ <li><a href="#see_also">SEE ALSO</a></li>
+ <li><a href="#authors">AUTHORS</a></li>
+</ul>
+
+-->
+
+
+</div>
+<!-- INDEX END -->
+
+<p>
+</p>
+<hr />
+<h1><a name="name">NAME</a></h1>
+<p>llvm-ranlib - Generate index for LLVM archive</p>
+<p>
+</p>
+<hr />
+<h1><a name="synopsis">SYNOPSIS</a></h1>
+<p><strong>llvm-ranlib</strong> [--version] [-help] <archive-file></p>
+<p>
+</p>
+<hr />
+<h1><a name="description">DESCRIPTION</a></h1>
+<p>The <strong>llvm-ranlib</strong> command is similar to the common Unix utility, <code>ranlib</code>. It
+adds or updates the symbol table in an LLVM archive file. Note that using the
+<strong>llvm-ar</strong> modifier <em class="file">s</em> is usually more efficient than running <strong>llvm-ranlib</strong>
+which is only provided only for completness and compatibility. Unlike other
+implementations of <code>ranlib</code>, <strong>llvm-ranlib</strong> indexes LLVM bitcode files, not
+native object modules. You can list the contents of the symbol table with the
+<code>llvm-nm -s</code> command.</p>
+<p>
+</p>
+<hr />
+<h1><a name="options">OPTIONS</a></h1>
+<dl>
+<dt><strong><a name="archive_file" class="item"><em class="file">archive-file</em></a></strong></dt>
+
+<dd>
+<p>Specifies the archive-file to which the symbol table is added or updated.</p>
+</dd>
+<dt><strong><a name="version" class="item"><em class="file">--version</em></a></strong></dt>
+
+<dd>
+<p>Print the version of <strong>llvm-ranlib</strong> and exit without building a symbol table.</p>
+</dd>
+<dt><strong><a name="help" class="item"><em class="file">-help</em></a></strong></dt>
+
+<dd>
+<p>Print usage help for <strong>llvm-ranlib</strong> and exit without building a symbol table.</p>
+</dd>
+</dl>
+<p>
+</p>
+<hr />
+<h1><a name="exit_status">EXIT STATUS</a></h1>
+<p>If <strong>llvm-ranlib</strong> succeeds, it will exit with 0. If an error occurs, a non-zero
+exit code will be returned.</p>
+<p>
+</p>
+<hr />
+<h1><a name="see_also">SEE ALSO</a></h1>
+<p><a href="././llvm-ar.html">llvm-ar</a>, <code>ranlib(1)</code></p>
+<p>
+</p>
+<hr />
+<h1><a name="authors">AUTHORS</a></h1>
+<p>Maintained by the LLVM Team (<a href="http://llvm.org/">http://llvm.org/</a>).</p>
+
+</body>
+
+</html>
Added: www-releases/trunk/3.0/docs/CommandGuide/html/opt.html
URL: http://llvm.org/viewvc/llvm-project/www-releases/trunk/3.0/docs/CommandGuide/html/opt.html?rev=145591&view=auto
==============================================================================
--- www-releases/trunk/3.0/docs/CommandGuide/html/opt.html (added)
+++ www-releases/trunk/3.0/docs/CommandGuide/html/opt.html Thu Dec 1 11:44:59 2011
@@ -0,0 +1,195 @@
+<?xml version="1.0" ?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+<title>opt</title>
+<link rel="stylesheet" href="manpage.css" type="text/css" />
+<meta http-equiv="content-type" content="text/html; charset=utf-8" />
+<link rev="made" href="mailto:root at localhost" />
+</head>
+
+<body>
+
+
+<!-- INDEX BEGIN -->
+<div name="index">
+<p><a name="__index__"></a></p>
+<!--
+
+<ul>
+
+ <li><a href="#name">NAME</a></li>
+ <li><a href="#synopsis">SYNOPSIS</a></li>
+ <li><a href="#description">DESCRIPTION</a></li>
+ <li><a href="#options">OPTIONS</a></li>
+ <li><a href="#exit_status">EXIT STATUS</a></li>
+ <li><a href="#authors">AUTHORS</a></li>
+</ul>
+
+-->
+
+
+</div>
+<!-- INDEX END -->
+
+<p>
+</p>
+<hr />
+<h1><a name="name">NAME</a></h1>
+<p>opt - LLVM optimizer</p>
+<p>
+</p>
+<hr />
+<h1><a name="synopsis">SYNOPSIS</a></h1>
+<p><strong>opt</strong> [<em>options</em>] [<em>filename</em>]</p>
+<p>
+</p>
+<hr />
+<h1><a name="description">DESCRIPTION</a></h1>
+<p>The <strong>opt</strong> command is the modular LLVM optimizer and analyzer. It takes LLVM
+source files as input, runs the specified optimizations or analyses on it, and then
+outputs the optimized file or the analysis results. The function of
+<strong>opt</strong> depends on whether the <strong>-analyze</strong> option is given.</p>
+<p>When <strong>-analyze</strong> is specified, <strong>opt</strong> performs various analyses of the input
+source. It will usually print the results on standard output, but in a few
+cases, it will print output to standard error or generate a file with the
+analysis output, which is usually done when the output is meant for another
+program.</p>
+<p>While <strong>-analyze</strong> is <em>not</em> given, <strong>opt</strong> attempts to produce an optimized
+output file. The optimizations available via <strong>opt</strong> depend upon what
+libraries were linked into it as well as any additional libraries that have
+been loaded with the <strong>-load</strong> option. Use the <strong>-help</strong> option to determine
+what optimizations you can use.</p>
+<p>If <em>filename</em> is omitted from the command line or is <em>-</em>, <strong>opt</strong> reads its
+input from standard input. Inputs can be in either the LLVM assembly language
+format (.ll) or the LLVM bitcode format (.bc).</p>
+<p>If an output filename is not specified with the <strong>-o</strong> option, <strong>opt</strong>
+writes its output to the standard output.</p>
+<p>
+</p>
+<hr />
+<h1><a name="options">OPTIONS</a></h1>
+<dl>
+<dt><strong><a name="f" class="item"><strong>-f</strong></a></strong></dt>
+
+<dd>
+<p>Enable binary output on terminals. Normally, <strong>opt</strong> will refuse to
+write raw bitcode output if the output stream is a terminal. With this option,
+<strong>opt</strong> will write raw bitcode regardless of the output device.</p>
+</dd>
+<dt><strong><a name="help" class="item"><strong>-help</strong></a></strong></dt>
+
+<dd>
+<p>Print a summary of command line options.</p>
+</dd>
+<dt><strong><a name="o_filename" class="item"><strong>-o</strong> <em>filename</em></a></strong></dt>
+
+<dd>
+<p>Specify the output filename.</p>
+</dd>
+<dt><strong><a name="s" class="item"><strong>-S</strong></a></strong></dt>
+
+<dd>
+<p>Write output in LLVM intermediate language (instead of bitcode).</p>
+</dd>
+<dt><strong><a name="passname" class="item"><strong>-{passname}</strong></a></strong></dt>
+
+<dd>
+<p><strong>opt</strong> provides the ability to run any of LLVM's optimization or analysis passes
+in any order. The <strong>-help</strong> option lists all the passes available. The order in
+which the options occur on the command line are the order in which they are
+executed (within pass constraints).</p>
+</dd>
+<dt><strong><a name="std_compile_opts" class="item"><strong>-std-compile-opts</strong></a></strong></dt>
+
+<dd>
+<p>This is short hand for a standard list of <em>compile time optimization</em> passes.
+This is typically used to optimize the output from the llvm-gcc front end. It
+might be useful for other front end compilers as well. To discover the full set
+of options available, use the following command:</p>
+<pre>
+ llvm-as < /dev/null | opt -std-compile-opts -disable-output -debug-pass=Arguments</pre>
+</dd>
+<dt><strong><a name="disable_inlining" class="item"><strong>-disable-inlining</strong></a></strong></dt>
+
+<dd>
+<p>This option is only meaningful when <strong>-std-compile-opts</strong> is given. It simply
+removes the inlining pass from the standard list.</p>
+</dd>
+<dt><strong><a name="disable_opt" class="item"><strong>-disable-opt</strong></a></strong></dt>
+
+<dd>
+<p>This option is only meaningful when <strong>-std-compile-opts</strong> is given. It disables
+most, but not all, of the <strong>-std-compile-opts</strong>. The ones that remain are
+<strong>-verify</strong>, <strong>-lower-setjmp</strong>, and <strong>-funcresolve</strong>.</p>
+</dd>
+<dt><strong><a name="strip_debug" class="item"><strong>-strip-debug</strong></a></strong></dt>
+
+<dd>
+<p>This option causes opt to strip debug information from the module before
+applying other optimizations. It is essentially the same as <strong>-strip</strong> but it
+ensures that stripping of debug information is done first.</p>
+</dd>
+<dt><strong><a name="verify_each" class="item"><strong>-verify-each</strong></a></strong></dt>
+
+<dd>
+<p>This option causes opt to add a verify pass after every pass otherwise specified
+on the command line (including <strong>-verify</strong>). This is useful for cases where it
+is suspected that a pass is creating an invalid module but it is not clear which
+pass is doing it. The combination of <strong>-std-compile-opts</strong> and <strong>-verify-each</strong>
+can quickly track down this kind of problem.</p>
+</dd>
+<dt><strong><a name="profile_info_file_filename" class="item"><strong>-profile-info-file</strong> <em>filename</em></a></strong></dt>
+
+<dd>
+<p>Specify the name of the file loaded by the -profile-loader option.</p>
+</dd>
+<dt><strong><a name="stats" class="item"><strong>-stats</strong></a></strong></dt>
+
+<dd>
+<p>Print statistics.</p>
+</dd>
+<dt><strong><a name="time_passes" class="item"><strong>-time-passes</strong></a></strong></dt>
+
+<dd>
+<p>Record the amount of time needed for each pass and print it to standard
+error.</p>
+</dd>
+<dt><strong><a name="debug" class="item"><strong>-debug</strong></a></strong></dt>
+
+<dd>
+<p>If this is a debug build, this option will enable debug printouts
+from passes which use the <em>DEBUG()</em> macro. See the <strong>LLVM Programmer's
+Manual</strong>, section <em>#DEBUG</em> for more information.</p>
+</dd>
+<dt><strong><a name="load_plugin" class="item"><strong>-load</strong>=<em>plugin</em></a></strong></dt>
+
+<dd>
+<p>Load the dynamic object <em>plugin</em>. This object should register new optimization
+or analysis passes. Once loaded, the object will add new command line options to
+enable various optimizations or analyses. To see the new complete list of
+optimizations, use the <strong>-help</strong> and <strong>-load</strong> options together. For example:</p>
+<pre>
+ opt -load=plugin.so -help</pre>
+</dd>
+<dt><strong><a name="p" class="item"><strong>-p</strong></a></strong></dt>
+
+<dd>
+<p>Print module after each transformation.</p>
+</dd>
+</dl>
+<p>
+</p>
+<hr />
+<h1><a name="exit_status">EXIT STATUS</a></h1>
+<p>If <strong>opt</strong> succeeds, it will exit with 0. Otherwise, if an error
+occurs, it will exit with a non-zero value.</p>
+<p>
+</p>
+<hr />
+<h1><a name="authors">AUTHORS</a></h1>
+<p>Maintained by the LLVM Team (<a href="http://llvm.org/">http://llvm.org/</a>).</p>
+
+</body>
+
+</html>
Added: www-releases/trunk/3.0/docs/CommandGuide/html/tblgen.html
URL: http://llvm.org/viewvc/llvm-project/www-releases/trunk/3.0/docs/CommandGuide/html/tblgen.html?rev=145591&view=auto
==============================================================================
--- www-releases/trunk/3.0/docs/CommandGuide/html/tblgen.html (added)
+++ www-releases/trunk/3.0/docs/CommandGuide/html/tblgen.html Thu Dec 1 11:44:59 2011
@@ -0,0 +1,170 @@
+<?xml version="1.0" ?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+<title>tblgen</title>
+<link rel="stylesheet" href="manpage.css" type="text/css" />
+<meta http-equiv="content-type" content="text/html; charset=utf-8" />
+<link rev="made" href="mailto:root at localhost" />
+</head>
+
+<body>
+
+
+<!-- INDEX BEGIN -->
+<div name="index">
+<p><a name="__index__"></a></p>
+<!--
+
+<ul>
+
+ <li><a href="#name">NAME</a></li>
+ <li><a href="#synopsis">SYNOPSIS</a></li>
+ <li><a href="#description">DESCRIPTION</a></li>
+ <li><a href="#options">OPTIONS</a></li>
+ <li><a href="#exit_status">EXIT STATUS</a></li>
+ <li><a href="#authors">AUTHORS</a></li>
+</ul>
+
+-->
+
+
+</div>
+<!-- INDEX END -->
+
+<p>
+</p>
+<hr />
+<h1><a name="name">NAME</a></h1>
+<p>tblgen - Target Description To C++ Code Generator</p>
+<p>
+</p>
+<hr />
+<h1><a name="synopsis">SYNOPSIS</a></h1>
+<p><strong>tblgen</strong> [<em>options</em>] [<em>filename</em>]</p>
+<p>
+</p>
+<hr />
+<h1><a name="description">DESCRIPTION</a></h1>
+<p><strong>tblgen</strong> translates from target description (.td) files into C++ code that can
+be included in the definition of an LLVM target library. Most users of LLVM will
+not need to use this program. It is only for assisting with writing an LLVM
+target backend.</p>
+<p>The input and output of <strong>tblgen</strong> is beyond the scope of this short
+introduction. Please see the <em>CodeGeneration</em> page in the LLVM documentation.</p>
+<p>The <em class="file">filename</em> argument specifies the name of a Target Description (.td) file
+to read as input.</p>
+<p>
+</p>
+<hr />
+<h1><a name="options">OPTIONS</a></h1>
+<dl>
+<dt><strong><a name="help" class="item"><strong>-help</strong></a></strong></dt>
+
+<dd>
+<p>Print a summary of command line options.</p>
+</dd>
+<dt><strong><a name="o_filename" class="item"><strong>-o</strong> <em class="file">filename</em></a></strong></dt>
+
+<dd>
+<p>Specify the output file name. If <em class="file">filename</em> is <code>-</code>, then <strong>tblgen</strong>
+sends its output to standard output.</p>
+</dd>
+<dt><strong><a name="i_directory" class="item"><strong>-I</strong> <em class="file">directory</em></a></strong></dt>
+
+<dd>
+<p>Specify where to find other target description files for inclusion. The
+<em class="file">directory</em> value should be a full or partial path to a directory that contains
+target description files.</p>
+</dd>
+<dt><strong><a name="asmwriternum_n" class="item"><strong>-asmwriternum</strong> <em class="file">N</em></a></strong></dt>
+
+<dd>
+<p>Make -gen-asm-writer emit assembly writer number <em class="file">N</em>.</p>
+</dd>
+<dt><strong><a name="class_class_name" class="item"><strong>-class</strong> <em class="file">class Name</em></a></strong></dt>
+
+<dd>
+<p>Print the enumeration list for this class.</p>
+</dd>
+<dt><strong><a name="print_records" class="item"><strong>-print-records</strong></a></strong></dt>
+
+<dd>
+<p>Print all records to standard output (default).</p>
+</dd>
+<dt><strong><a name="print_enums" class="item"><strong>-print-enums</strong></a></strong></dt>
+
+<dd>
+<p>Print enumeration values for a class</p>
+</dd>
+<dt><strong><a name="gen_emitter" class="item"><strong>-gen-emitter</strong></a></strong></dt>
+
+<dd>
+<p>Generate machine code emitter.</p>
+</dd>
+<dt><strong><a name="gen_register_enums" class="item"><strong>-gen-register-enums</strong></a></strong></dt>
+
+<dd>
+<p>Generate the enumeration values for all registers.</p>
+</dd>
+<dt><strong><a name="gen_register_desc" class="item"><strong>-gen-register-desc</strong></a></strong></dt>
+
+<dd>
+<p>Generate a register info description for each register.</p>
+</dd>
+<dt><strong><a name="gen_register_desc_header" class="item"><strong>-gen-register-desc-header</strong></a></strong></dt>
+
+<dd>
+<p>Generate a register info description header for each register.</p>
+</dd>
+<dt><strong><a name="gen_instr_enums" class="item"><strong>-gen-instr-enums</strong></a></strong></dt>
+
+<dd>
+<p>Generate enumeration values for instructions.</p>
+</dd>
+<dt><strong><a name="gen_instr_desc" class="item"><strong>-gen-instr-desc</strong></a></strong></dt>
+
+<dd>
+<p>Generate instruction descriptions.</p>
+</dd>
+<dt><strong><a name="gen_asm_writer" class="item"><strong>-gen-asm-writer</strong></a></strong></dt>
+
+<dd>
+<p>Generate the assembly writer.</p>
+</dd>
+<dt><strong><a name="gen_dag_isel" class="item"><strong>-gen-dag-isel</strong></a></strong></dt>
+
+<dd>
+<p>Generate a DAG (Directed Acycle Graph) instruction selector.</p>
+</dd>
+<dt><strong><a name="gen_subtarget" class="item"><strong>-gen-subtarget</strong></a></strong></dt>
+
+<dd>
+<p>Generate subtarget enumerations.</p>
+</dd>
+<dt><strong><a name="gen_intrinsic" class="item"><strong>-gen-intrinsic</strong></a></strong></dt>
+
+<dd>
+<p>Generate intrinsic information.</p>
+</dd>
+<dt><strong><a name="version" class="item"><strong>-version</strong></a></strong></dt>
+
+<dd>
+<p>Show the version number of this program.</p>
+</dd>
+</dl>
+<p>
+</p>
+<hr />
+<h1><a name="exit_status">EXIT STATUS</a></h1>
+<p>If <strong>tblgen</strong> succeeds, it will exit with 0. Otherwise, if an error
+occurs, it will exit with a non-zero value.</p>
+<p>
+</p>
+<hr />
+<h1><a name="authors">AUTHORS</a></h1>
+<p>Maintained by The LLVM Team (<a href="http://llvm.org/">http://llvm.org/</a>).</p>
+
+</body>
+
+</html>
More information about the llvm-commits
mailing list