[llvm-commits] CVS: llvm-www/releases/2.1/docs/CommandGuide/html/bugpoint.html llc.html lli.html llvm-ar.html llvm-as.html llvm-bcanalyzer.html llvm-config.html llvm-db.html llvm-dis.html llvm-extract.html llvm-ld.html llvm-link.html llvm-nm.html llvm-prof.html llvm-ranlib.html llvm-upgrade.html llvm2cpp.html llvmc.html llvmgcc.html llvmgxx.html manpage.css opt.html stkrc.html tblgen.html
Tanya Lattner
tonic at nondot.org
Wed Sep 26 22:43:39 PDT 2007
Changes in directory llvm-www/releases/2.1/docs/CommandGuide/html:
bugpoint.html added (r1.1)
llc.html added (r1.1)
lli.html added (r1.1)
llvm-ar.html added (r1.1)
llvm-as.html added (r1.1)
llvm-bcanalyzer.html added (r1.1)
llvm-config.html added (r1.1)
llvm-db.html added (r1.1)
llvm-dis.html added (r1.1)
llvm-extract.html added (r1.1)
llvm-ld.html added (r1.1)
llvm-link.html added (r1.1)
llvm-nm.html added (r1.1)
llvm-prof.html added (r1.1)
llvm-ranlib.html added (r1.1)
llvm-upgrade.html added (r1.1)
llvm2cpp.html added (r1.1)
llvmc.html added (r1.1)
llvmgcc.html added (r1.1)
llvmgxx.html added (r1.1)
manpage.css added (r1.1)
opt.html added (r1.1)
stkrc.html added (r1.1)
tblgen.html added (r1.1)
---
Log message:
Add docs for 2.1 release
---
Diffs of the changes: (+5072 -0)
bugpoint.html | 203 +++++++++++++++++++
llc.html | 262 +++++++++++++++++++++++++
lli.html | 310 ++++++++++++++++++++++++++++++
llvm-ar.html | 502 ++++++++++++++++++++++++++++++++++++++++++++++++
llvm-as.html | 108 ++++++++++
llvm-bcanalyzer.html | 451 +++++++++++++++++++++++++++++++++++++++++++
llvm-config.html | 201 +++++++++++++++++++
llvm-db.html | 43 ++++
llvm-dis.html | 97 +++++++++
llvm-extract.html | 102 +++++++++
llvm-ld.html | 377 ++++++++++++++++++++++++++++++++++++
llvm-link.html | 118 +++++++++++
llvm-nm.html | 181 +++++++++++++++++
llvm-prof.html | 93 +++++++++
llvm-ranlib.html | 91 ++++++++
llvm-upgrade.html | 97 +++++++++
llvm2cpp.html | 282 +++++++++++++++++++++++++++
llvmc.html | 525 +++++++++++++++++++++++++++++++++++++++++++++++++++
llvmgcc.html | 131 ++++++++++++
llvmgxx.html | 131 ++++++++++++
manpage.css | 256 ++++++++++++++++++++++++
opt.html | 199 +++++++++++++++++++
stkrc.html | 133 ++++++++++++
tblgen.html | 179 +++++++++++++++++
24 files changed, 5072 insertions(+)
Index: llvm-www/releases/2.1/docs/CommandGuide/html/bugpoint.html
diff -c /dev/null llvm-www/releases/2.1/docs/CommandGuide/html/bugpoint.html:1.1
*** /dev/null Thu Sep 27 00:43:29 2007
--- llvm-www/releases/2.1/docs/CommandGuide/html/bugpoint.html Thu Sep 27 00:43:19 2007
***************
*** 0 ****
--- 1,203 ----
+ <!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" />
+ <link rev="made" href="mailto:root at localhost" />
+ </head>
+
+ <body>
+
+ <p><a name="__index__"></a></p>
+ <!-- INDEX BEGIN -->
+ <!--
+
+ <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>
+ -->
+ <!-- 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>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="item__2d_2dadditional_2dso_library"><strong>--additional-so</strong> <em>library</em></a></strong><br />
+ </dt>
+ <dd>
+ Load the dynamic shared object <em>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.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2d_2dargs_program_args"><strong>--args</strong> <em>program args</em></a></strong><br />
+ </dt>
+ <dd>
+ 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:
+ </dd>
+ <dd>
+ <pre>
+ bugpoint [bugpoint args] --args -- [program args]</pre>
+ </dd>
+ <dd>
+ <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>
+ <p></p>
+ <dt><strong><a name="item__2d_2dtool_2dargs_tool_args"><strong>--tool-args</strong> <em>tool args</em></a></strong><br />
+ </dt>
+ <dd>
+ 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:
+ </dd>
+ <dd>
+ <pre>
+ bugpoint [bugpoint args] --tool-args -- [tool args]</pre>
+ </dd>
+ <dd>
+ <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>
+ <p></p>
+ <dt><strong><a name="item__2d_2dcheck_2dexit_2dcode_3d_7btrue_2cfalse_7d"><strong>--check-exit-code</strong>=<em>{true,false}</em></a></strong><br />
+ </dt>
+ <dd>
+ Assume a non-zero exit code or core dump from the test program is a failure.
+ Defaults to true.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2d_2ddisable_2d_7bdce_2csimplifycfg_7d"><strong>--disable-{dce,simplifycfg}</strong></a></strong><br />
+ </dt>
+ <dd>
+ 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.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2d_2denable_2dvalgrind"><strong>--enable-valgrind</strong></a></strong><br />
+ </dt>
+ <dd>
+ Use valgrind to find faults in the optimization phase. This will allow
+ bugpoint to find otherwise asymptomatic problems caused by memory
+ mis-management.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2dfind_2dbugs"><strong>-find-bugs</strong></a></strong><br />
+ </dt>
+ <dd>
+ Continually randomize the specified passes and run them on the test program
+ until a bug is found or the user kills <strong>bugpoint</strong>.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2d_2dhelp"><strong>--help</strong></a></strong><br />
+ </dt>
+ <dd>
+ Print a summary of command line options.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2d_2dinput_filename"><strong>--input</strong> <em>filename</em></a></strong><br />
+ </dt>
+ <dd>
+ Open <em>filename</em> and redirect the standard input of the test program, whenever
+ it runs, to come from that file.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2d_2dload_plugin"><strong>--load</strong> <em>plugin</em></a></strong><br />
+ </dt>
+ <dd>
+ Load the dynamic object <em>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:
+ </dd>
+ <dd>
+ <pre>
+ bugpoint --load myNewPass.so --help</pre>
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2d_2dmlimit_megabytes"><strong>--mlimit</strong> <em>megabytes</em></a></strong><br />
+ </dt>
+ <dd>
+ Specifies an upper limit on memory usage of the optimization and codegen. Set
+ to zero to disable the limit.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2d_2doutput_filename"><strong>--output</strong> <em>filename</em></a></strong><br />
+ </dt>
+ <dd>
+ Whenever the test program produces output on its standard output stream, it
+ should match the contents of <em>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 C backend and running it.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2d_2dprofile_2dinfo_2dfile_filename"><strong>--profile-info-file</strong> <em>filename</em></a></strong><br />
+ </dt>
+ <dd>
+ Profile file loaded by <strong>--profile-loader</strong>.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2d_2drun_2d_7bint_2cjit_2cllc_2ccbe_7d"><strong>--run-{int,jit,llc,cbe}</strong></a></strong><br />
+ </dt>
+ <dd>
+ 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, or the C
+ backend, respectively.
+ </dd>
+ <p></p></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>
Index: llvm-www/releases/2.1/docs/CommandGuide/html/llc.html
diff -c /dev/null llvm-www/releases/2.1/docs/CommandGuide/html/llc.html:1.1
*** /dev/null Thu Sep 27 00:43:39 2007
--- llvm-www/releases/2.1/docs/CommandGuide/html/llc.html Thu Sep 27 00:43:19 2007
***************
*** 0 ****
--- 1,262 ----
+ <!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" />
+ <link rev="made" href="mailto:root at localhost" />
+ </head>
+
+ <body>
+
+ <p><a name="__index__"></a></p>
+ <!-- INDEX BEGIN -->
+ <!--
+
+ <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="#enduser_options">End-user Options</a></li>
+ <li><a href="#tuning_configuration_options">Tuning/Configuration Options</a></li>
+ <li><a href="#intel_ia32specific_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>
+ -->
+ <!-- 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 bitcode 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 bitcode 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 LLVM bitcode from standard input.
+ Otherwise, it will read LLVM bitcode from <em>filename</em>.</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>.bc</em> extension, and adding a <em>.s</em> suffix.</p>
+ <p>Other <strong>llc</strong> options are as follows:</p>
+ <p>
+ </p>
+ <h2><a name="enduser_options">End-user Options</a></h2>
+ <dl>
+ <dt><strong><a name="item__2d_2dhelp"><strong>--help</strong></a></strong><br />
+ </dt>
+ <dd>
+ Print a summary of command line options.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2df"><strong>-f</strong></a></strong><br />
+ </dt>
+ <dd>
+ Overwrite output files. By default, <strong>llc</strong> will refuse to overwrite
+ an output file which already exists.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2dmtriple_3dtarget_triple"><strong>-mtriple</strong>=<em>target triple</em></a></strong><br />
+ </dt>
+ <dd>
+ Override the target triple specified in the input bitcode file with the
+ specified string.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2dmarch_3darch"><strong>-march</strong>=<em>arch</em></a></strong><br />
+ </dt>
+ <dd>
+ 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.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2dmcpu_3dcpuname"><strong>-mcpu</strong>=<em>cpuname</em></a></strong><br />
+ </dt>
+ <dd>
+ 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>
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2dmattr_3da1_2c_2ba2_2c_2da3_2c_2e_2e_2e"><strong>-mattr</strong>=<em>a1,+a2,-a3,...</em></a></strong><br />
+ </dt>
+ <dd>
+ 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>
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2d_2ddisable_2dfp_2delim"><strong>--disable-fp-elim</strong></a></strong><br />
+ </dt>
+ <dd>
+ Disable frame pointer elimination optimization.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2d_2ddisable_2dexcess_2dfp_2dprecision"><strong>--disable-excess-fp-precision</strong></a></strong><br />
+ </dt>
+ <dd>
+ 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).
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2d_2denable_2dunsafe_2dfp_2dmath"><strong>--enable-unsafe-fp-math</strong></a></strong><br />
+ </dt>
+ <dd>
+ 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).
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2d_2denable_2dcorrect_2deh_2dsupport"><strong>--enable-correct-eh-support</strong></a></strong><br />
+ </dt>
+ <dd>
+ Instruct the <strong>lowerinvoke</strong> pass to insert code for correct exception handling
+ support. This is expensive and is by default omitted for efficiency.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2d_2dstats"><strong>--stats</strong></a></strong><br />
+ </dt>
+ <dd>
+ Print statistics recorded by code-generation passes.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2d_2dtime_2dpasses"><strong>--time-passes</strong></a></strong><br />
+ </dt>
+ <dd>
+ Record the amount of time needed for each pass and print a report to standard
+ error.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2d_2dload_3ddso_path"><strong>--load</strong>=<em>dso_path</em></a></strong><br />
+ </dt>
+ <dd>
+ Dynamically load <em>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.
+ </dd>
+ <p></p></dl>
+ <p>
+ </p>
+ <h2><a name="tuning_configuration_options">Tuning/Configuration Options</a></h2>
+ <dl>
+ <dt><strong><a name="item__2d_2dprint_2dmachineinstrs"><strong>--print-machineinstrs</strong></a></strong><br />
+ </dt>
+ <dd>
+ Print generated machine code between compilation phases (useful for debugging).
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2d_2dregalloc_3dallocator"><strong>--regalloc</strong>=<em>allocator</em></a></strong><br />
+ </dt>
+ <dd>
+ Specify the register allocator to use. The default <em>allocator</em> is <em>local</em>.
+ Valid register allocators are:
+ </dd>
+ <dl>
+ <dt><strong><a name="item_simple"><em>simple</em></a></strong><br />
+ </dt>
+ <dd>
+ Very simple ``always spill'' register allocator
+ </dd>
+ <p></p>
+ <dt><strong><a name="item_local"><em>local</em></a></strong><br />
+ </dt>
+ <dd>
+ Local register allocator
+ </dd>
+ <p></p>
+ <dt><strong><a name="item_linearscan"><em>linearscan</em></a></strong><br />
+ </dt>
+ <dd>
+ Linear scan global register allocator
+ </dd>
+ <p></p>
+ <dt><strong><a name="item_iterativescan"><em>iterativescan</em></a></strong><br />
+ </dt>
+ <dd>
+ Iterative scan global register allocator
+ </dd>
+ <p></p></dl>
+ <dt><strong><a name="item__2d_2dspiller_3dspiller"><strong>--spiller</strong>=<em>spiller</em></a></strong><br />
+ </dt>
+ <dd>
+ 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:
+ </dd>
+ <dl>
+ <dt><strong><em>simple</em></strong><br />
+ </dt>
+ <dd>
+ Simple spiller
+ </dd>
+ <p></p>
+ <dt><strong><em>local</em></strong><br />
+ </dt>
+ <dd>
+ Local spiller
+ </dd>
+ <p></p></dl>
+ </dl>
+ <p>
+ </p>
+ <h2><a name="intel_ia32specific_options">Intel IA-32-specific Options</a></h2>
+ <dl>
+ <dt><strong><a name="item__2d_2dx86_2dasm_2dsyntax_3datt_7cintel"><strong>--x86-asm-syntax=att|intel</strong></a></strong><br />
+ </dt>
+ <dd>
+ Specify whether to emit assembly code in AT&T syntax (the default) or intel
+ syntax.
+ </dd>
+ <p></p></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>
Index: llvm-www/releases/2.1/docs/CommandGuide/html/lli.html
diff -c /dev/null llvm-www/releases/2.1/docs/CommandGuide/html/lli.html:1.1
*** /dev/null Thu Sep 27 00:43:39 2007
--- llvm-www/releases/2.1/docs/CommandGuide/html/lli.html Thu Sep 27 00:43:19 2007
***************
*** 0 ****
--- 1,310 ----
+ <!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" />
+ <link rev="made" href="mailto:root at localhost" />
+ </head>
+
+ <body>
+
+ <p><a name="__index__"></a></p>
+ <!-- INDEX BEGIN -->
+ <!--
+
+ <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>
+ -->
+ <!-- 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="item__2dfake_2dargv0_3dexecutable"><strong>-fake-argv0</strong>=<em>executable</em></a></strong><br />
+ </dt>
+ <dd>
+ Override the <code>argv[0]</code> value passed into the executing program.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2dforce_2dinterpreter_3d_7bfalse_2ctrue_7d"><strong>-force-interpreter</strong>=<em>{false,true}</em></a></strong><br />
+ </dt>
+ <dd>
+ If set to true, use the interpreter even if a just-in-time compiler is available
+ for this architecture. Defaults to false.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2dhelp"><strong>-help</strong></a></strong><br />
+ </dt>
+ <dd>
+ Print a summary of command line options.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2dload_3dpuginfilename"><strong>-load</strong>=<em>puginfilename</em></a></strong><br />
+ </dt>
+ <dd>
+ Causes <strong>lli</strong> to load the plugin (shared object) named <em>pluginfilename</em> and use
+ it for optimization.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2dstats"><strong>-stats</strong></a></strong><br />
+ </dt>
+ <dd>
+ Print statistics from the code-generation passes. This is only meaningful for
+ the just-in-time compiler, at present.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2dtime_2dpasses"><strong>-time-passes</strong></a></strong><br />
+ </dt>
+ <dd>
+ Record the amount of time needed for each code-generation pass and print it to
+ standard error.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2dversion"><strong>-version</strong></a></strong><br />
+ </dt>
+ <dd>
+ Print out the version of <strong>lli</strong> and exit without doing anything else.
+ </dd>
+ <p></p></dl>
+ <p>
+ </p>
+ <hr />
+ <h1><a name="target_options">TARGET OPTIONS</a></h1>
+ <dl>
+ <dt><strong><a name="item__2dmtriple_3dtarget_triple"><strong>-mtriple</strong>=<em>target triple</em></a></strong><br />
+ </dt>
+ <dd>
+ 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.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2dmarch_3darch"><strong>-march</strong>=<em>arch</em></a></strong><br />
+ </dt>
+ <dd>
+ 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.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2dmcpu_3dcpuname"><strong>-mcpu</strong>=<em>cpuname</em></a></strong><br />
+ </dt>
+ <dd>
+ 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>
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2dmattr_3da1_2c_2ba2_2c_2da3_2c_2e_2e_2e"><strong>-mattr</strong>=<em>a1,+a2,-a3,...</em></a></strong><br />
+ </dt>
+ <dd>
+ 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>
+ </dd>
+ <p></p></dl>
+ <p>
+ </p>
+ <hr />
+ <h1><a name="floating_point_options">FLOATING POINT OPTIONS</a></h1>
+ <dl>
+ <dt><strong><a name="item__2ddisable_2dexcess_2dfp_2dprecision"><strong>-disable-excess-fp-precision</strong></a></strong><br />
+ </dt>
+ <dd>
+ Disable optimizations that may increase floating point precision.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2denable_2dfinite_2donly_2dfp_2dmath"><strong>-enable-finite-only-fp-math</strong></a></strong><br />
+ </dt>
+ <dd>
+ Enable optimizations that assumes only finite floating point math. That is,
+ there is no NAN or Inf values.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2denable_2dunsafe_2dfp_2dmath"><strong>-enable-unsafe-fp-math</strong></a></strong><br />
+ </dt>
+ <dd>
+ Causes <strong>lli</strong> to enable optimizations that may decrease floating point
+ precision.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2dsoft_2dfloat"><strong>-soft-float</strong></a></strong><br />
+ </dt>
+ <dd>
+ Causes <strong>lli</strong> to generate software floating point library calls instead of
+ equivalent hardware instructions.
+ </dd>
+ <p></p></dl>
+ <p>
+ </p>
+ <hr />
+ <h1><a name="code_generation_options">CODE GENERATION OPTIONS</a></h1>
+ <dl>
+ <dt><strong><a name="item__2dcode_2dmodel_3dmodel"><strong>-code-model</strong>=<em>model</em></a></strong><br />
+ </dt>
+ <dd>
+ Choose the code model from:
+ </dd>
+ <dd>
+ <pre>
+ default: Target default code model
+ small: Small code model
+ kernel: Kernel code model
+ medium: Medium code model
+ large: Large code model</pre>
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2ddisable_2dpost_2dra_2dscheduler"><strong>-disable-post-RA-scheduler</strong></a></strong><br />
+ </dt>
+ <dd>
+ Disable scheduling after register allocation.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2ddisable_2dspill_2dfusing"><strong>-disable-spill-fusing</strong></a></strong><br />
+ </dt>
+ <dd>
+ Disable fusing of spill code into instructions.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2denable_2dcorrect_2deh_2dsupport"><strong>-enable-correct-eh-support</strong></a></strong><br />
+ </dt>
+ <dd>
+ Make the -lowerinvoke pass insert expensive, but correct, EH code.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2denable_2deh"><strong>-enable-eh</strong></a></strong><br />
+ </dt>
+ <dd>
+ Exception handling should be emitted.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2djoin_2dliveintervals"><strong>-join-liveintervals</strong></a></strong><br />
+ </dt>
+ <dd>
+ Coalesce copies (default=true).
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2dnozero_2dinitialized_2din_2dbss_don_27t_place_z"><strong>-nozero-initialized-in-bss</strong>
+ Don't place zero-initialized symbols into the BSS section.</a></strong><br />
+ </dt>
+ <dt><strong><a name="item__2dpre_2dra_2dsched_3dscheduler"><strong>-pre-RA-sched</strong>=<em>scheduler</em></a></strong><br />
+ </dt>
+ <dd>
+ Instruction schedulers available (before register allocation):
+ </dd>
+ <dd>
+ <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>
+ <p></p>
+ <dt><strong><a name="item__2dregalloc_3dallocator"><strong>-regalloc</strong>=<em>allocator</em></a></strong><br />
+ </dt>
+ <dd>
+ Register allocator to use: (default = linearscan)
+ </dd>
+ <dd>
+ <pre>
+ =bigblock: Big-block register allocator
+ =linearscan: linear scan register allocator =local - local register allocator
+ =simple: simple register allocator</pre>
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2drelocation_2dmodel_3dmodel"><strong>-relocation-model</strong>=<em>model</em></a></strong><br />
+ </dt>
+ <dd>
+ Choose relocation model from:
+ </dd>
+ <dd>
+ <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>
+ <p></p>
+ <dt><strong><a name="item__2dspiller"><strong>-spiller</strong></a></strong><br />
+ </dt>
+ <dd>
+ Spiller to use: (default: local)
+ </dd>
+ <dd>
+ <pre>
+ =simple: simple spiller
+ =local: local spiller</pre>
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2dx86_2dasm_2dsyntax_3dsyntax"><strong>-x86-asm-syntax</strong>=<em>syntax</em></a></strong><br />
+ </dt>
+ <dd>
+ Choose style of code to emit from X86 backend:
+ </dd>
+ <dd>
+ <pre>
+ =att: Emit AT&T-style assembly
+ =intel: Emit Intel-style assembly</pre>
+ </dd>
+ <p></p></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>
Index: llvm-www/releases/2.1/docs/CommandGuide/html/llvm-ar.html
diff -c /dev/null llvm-www/releases/2.1/docs/CommandGuide/html/llvm-ar.html:1.1
*** /dev/null Thu Sep 27 00:43:39 2007
--- llvm-www/releases/2.1/docs/CommandGuide/html/llvm-ar.html Thu Sep 27 00:43:19 2007
***************
*** 0 ****
--- 1,502 ----
+ <!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" />
+ <link rev="made" href="mailto:root at localhost" />
+ </head>
+
+ <body>
+
+ <p><a name="__index__"></a></p>
+ <!-- INDEX BEGIN -->
+ <!--
+
+ <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>
+ -->
+ <!-- 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 <code>f</code> 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="item_symbol_table"><em>Symbol Table</em></a></strong><br />
+ </dt>
+ <dd>
+ 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.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item_long_paths"><em>Long Paths</em></a></strong><br />
+ </dt>
+ <dd>
+ 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.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item_compression"><em>Compression</em></a></strong><br />
+ </dt>
+ <dd>
+ <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.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item_directory_recursion"><em>Directory Recursion</em></a></strong><br />
+ </dt>
+ <dd>
+ Most <code>ar</code> implementations do not recurse through directories but simply
+ ignore directories if they are presented to the program in the <em>files</em>
+ option. <strong>llvm-ar</strong>, however, can recurse through directory structures and
+ add all the files under a directory, if requested.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item_toc_verbose_output"><em>TOC Verbose Output</em></a></strong><br />
+ </dt>
+ <dd>
+ 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.
+ </dd>
+ <p></p></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>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 <code>.a</code> suffix, but this is not required. Following
+ the <em>archive-name</em> comes a list of <em>files</em> that indicate the specific members
+ of the archive to operate on. If the <em>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="item_d">d</a></strong><br />
+ </dt>
+ <dd>
+ Delete files from the archive. No modifiers are applicable to this operation.
+ The <em>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>files</em> are specified, the archive is not modified.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item_m_5babi_5d">m[abi]</a></strong><br />
+ </dt>
+ <dd>
+ Move files from one location in the archive to another. The <em>a</em>, <em>b</em>, and
+ <em>i</em> modifiers apply to this operation. The <em>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>files</em> are specified, the
+ archive is not modified.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item_p_5bk_5d">p[k]</a></strong><br />
+ </dt>
+ <dd>
+ Print files to the standard output. The <em>k</em> modifier applies to this
+ operation. This operation simply prints the <em>files</em> indicated to the
+ standard output. If no <em>files</em> are specified, the entire archive is printed.
+ Printing bitcode files is ill-advised as they might confuse your terminal
+ settings. The <em>p</em> operation never modifies the archive.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item_q_5brfz_5d">q[Rfz]</a></strong><br />
+ </dt>
+ <dd>
+ Quickly append files to the end of the archive. The <em>R</em>, <em>f</em>, and <em>z</em>
+ modifiers apply to this operation. This operation quickly adds the
+ <em>files</em> to the archive without checking for duplicates that should be
+ removed first. If no <em>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>q</em> operation is any faster than the <em>r</em> operation.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item_r_5brabfuz_5d">r[Rabfuz]</a></strong><br />
+ </dt>
+ <dd>
+ Replace or insert file members. The <em>R</em>, <em>a</em>, <em>b</em>, <em>f</em>, <em>u</em>, and <em>z</em>
+ modifiers apply to this operation. This operation will replace existing
+ <em>files</em> or insert them at the end of the archive if they do not exist. If no
+ <em>files</em> are specified, the archive is not modified.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item_t_5bv_5d">t[v]</a></strong><br />
+ </dt>
+ <dd>
+ Print the table of contents. Without any modifiers, this operation just prints
+ the names of the members to the standard output. With the <em>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>files</em> are specified, the listing is only for
+ those files. If no <em>files</em> are specified, the table of contents for the
+ whole archive is printed.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item_x_5bop_5d">x[oP]</a></strong><br />
+ </dt>
+ <dd>
+ Extract archive members back to files. The <em>o</em> modifier applies to this
+ operation. This operation retrieves the indicated <em>files</em> from the archive
+ and writes them back to the operating system's file system. If no
+ <em>files</em> are specified, the entire archive is extract.
+ </dd>
+ <p></p></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="item__5ba_5d">[a]</a></strong><br />
+ </dt>
+ <dd>
+ When inserting or moving member files, this option specifies the destination of
+ the new files as being <code>a</code>fter the <em>relpos</em> member. If <em>relpos</em> is not found,
+ the files are placed at the end of the archive.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__5bb_5d">[b]</a></strong><br />
+ </dt>
+ <dd>
+ When inserting or moving member files, this option specifies the destination of
+ the new files as being <code>b</code>efore the <em>relpos</em> member. If <em>relpos</em> is not
+ found, the files are placed at the end of the archive. This modifier is
+ identical to the the <em>i</em> modifier.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__5bf_5d">[f]</a></strong><br />
+ </dt>
+ <dd>
+ 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>R</em> option, the directory recursion will be performed but the file names
+ will all be <code>f</code>lattened to simple file names.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__5bi_5d">[i]</a></strong><br />
+ </dt>
+ <dd>
+ A synonym for the <em>b</em> option.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__5bk_5d">[k]</a></strong><br />
+ </dt>
+ <dd>
+ Normally, <strong>llvm-ar</strong> will not print the contents of bitcode files when the
+ <em>p</em> operation is used. This modifier defeats the default and allows the
+ bitcode members to be printed.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__5bn_5d">[N]</a></strong><br />
+ </dt>
+ <dd>
+ This option is ignored by <strong>llvm-ar</strong> but provided for compatibility.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__5bo_5d">[o]</a></strong><br />
+ </dt>
+ <dd>
+ When extracting files, this option will cause <strong>llvm-ar</strong> to preserve the
+ original modification times of the files it writes.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__5bp_5d">[P]</a></strong><br />
+ </dt>
+ <dd>
+ use full path names when matching
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__5br_5d">[R]</a></strong><br />
+ </dt>
+ <dd>
+ This modifier instructions the <em>r</em> option to recursively process directories.
+ Without <em>R</em>, directories are ignored and only those <em>files</em> that refer to
+ files will be added to the archive. When <em>R</em> is used, any directories specified
+ with <em>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.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__5bu_5d">[u]</a></strong><br />
+ </dt>
+ <dd>
+ 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.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__5bz_5d">[z]</a></strong><br />
+ </dt>
+ <dd>
+ 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.
+ </dd>
+ <p></p></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="item__5bc_5d">[c]</a></strong><br />
+ </dt>
+ <dd>
+ 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.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__5bs_5d">[s]</a></strong><br />
+ </dt>
+ <dd>
+ 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.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__5bs_5d">[S]</a></strong><br />
+ </dt>
+ <dd>
+ This modifier is the opposite of the <em>s</em> modifier. It instructs <strong>llvm-ar</strong> to
+ not build the symbol table. If both <em>s</em> and <em>S</em> are used, the last modifier to
+ occur in the options will prevail.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__5bv_5d">[v]</a></strong><br />
+ </dt>
+ <dd>
+ 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.
+ </dd>
+ <p></p></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 <code>f</code> 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="item_name__2d_char_5b16_5d">name - char[16]</a></strong><br />
+ </dt>
+ <dd>
+ 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.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item_date__2d_char_5b12_5d">date - char[12]</a></strong><br />
+ </dt>
+ <dd>
+ 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.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item_uid__2d_char_5b6_5d">uid - char[6]</a></strong><br />
+ </dt>
+ <dd>
+ 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.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item_gid__2d_char_5b6_5d">gid - char[6]</a></strong><br />
+ </dt>
+ <dd>
+ 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.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item_mode__2d_char_5b8_5d">mode - char[8]</a></strong><br />
+ </dt>
+ <dd>
+ 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.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item_size__2d_char_5b10_5d">size - char[10]</a></strong><br />
+ </dt>
+ <dd>
+ 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.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item_fmag__2d_char_5b2_5d">fmag - char[2]</a></strong><br />
+ </dt>
+ <dd>
+ 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.
+ </dd>
+ <p></p></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="item_offset__2d_vbr_encoded_32_2dbit_integer">offset - vbr encoded 32-bit integer</a></strong><br />
+ </dt>
+ <dd>
+ 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.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item_length__2d_vbr_encoded_32_2dbit_integer">length - vbr encoded 32-bit integer</a></strong><br />
+ </dt>
+ <dd>
+ The length item provides the length of the symbol that follows. Like this
+ <em>offset</em> item, the length is variable bit rate encoded.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item_symbol__2d_character_array">symbol - character array</a></strong><br />
+ </dt>
+ <dd>
+ 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.
+ </dd>
+ <p></p></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>
Index: llvm-www/releases/2.1/docs/CommandGuide/html/llvm-as.html
diff -c /dev/null llvm-www/releases/2.1/docs/CommandGuide/html/llvm-as.html:1.1
*** /dev/null Thu Sep 27 00:43:39 2007
--- llvm-www/releases/2.1/docs/CommandGuide/html/llvm-as.html Thu Sep 27 00:43:19 2007
***************
*** 0 ****
--- 1,108 ----
+ <!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" />
+ <link rev="made" href="mailto:root at localhost" />
+ </head>
+
+ <body>
+
+ <p><a name="__index__"></a></p>
+ <!-- INDEX BEGIN -->
+ <!--
+
+ <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>
+ -->
+ <!-- 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>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></li>
+ If the input is standard input, then the output is standard output.
+ <p></p>
+ <li></li>
+ 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></p>
+ <li></li>
+ 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></p></ul>
+ <p>
+ </p>
+ <hr />
+ <h1><a name="options">OPTIONS</a></h1>
+ <dl>
+ <dt><strong><a name="item__2df"><strong>-f</strong></a></strong><br />
+ </dt>
+ <dd>
+ Force overwrite. Normally, <strong>llvm-as</strong> will refuse to overwrite an
+ output file that already exists. With this option, <strong>llvm-as</strong>
+ will overwrite the output file and replace it with new bitcode.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2d_2dhelp"><strong>--help</strong></a></strong><br />
+ </dt>
+ <dd>
+ Print a summary of command line options.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2do_filename"><strong>-o</strong> <em>filename</em></a></strong><br />
+ </dt>
+ <dd>
+ Specify the output file name. If <em>filename</em> is <code>-</code>, then <strong>llvm-as</strong>
+ sends its output to standard output.
+ </dd>
+ <p></p></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>
Index: llvm-www/releases/2.1/docs/CommandGuide/html/llvm-bcanalyzer.html
diff -c /dev/null llvm-www/releases/2.1/docs/CommandGuide/html/llvm-bcanalyzer.html:1.1
*** /dev/null Thu Sep 27 00:43:39 2007
--- llvm-www/releases/2.1/docs/CommandGuide/html/llvm-bcanalyzer.html Thu Sep 27 00:43:19 2007
***************
*** 0 ****
--- 1,451 ----
+ <!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" />
+ <link rev="made" href="mailto:root at localhost" />
+ </head>
+
+ <body>
+
+ <p><a name="__index__"></a></p>
+ <!-- INDEX BEGIN -->
+ <!--
+
+ <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>
+ -->
+ <!-- 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>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>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="item__2dnodetails"><strong>-nodetails</strong></a></strong><br />
+ </dt>
+ <dd>
+ 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.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2ddump"><strong>-dump</strong></a></strong><br />
+ </dt>
+ <dd>
+ 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.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2dverify"><strong>-verify</strong></a></strong><br />
+ </dt>
+ <dd>
+ 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.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2d_2dhelp"><strong>--help</strong></a></strong><br />
+ </dt>
+ <dd>
+ Print a summary of command line options.
+ </dd>
+ <p></p></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="item_bitcode_analysis_of_module"><strong>Bitcode Analysis Of Module</strong></a></strong><br />
+ </dt>
+ <dd>
+ This just provides the name of the module for which bitcode analysis is being
+ generated.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item_bitcode_version_number"><strong>Bitcode Version Number</strong></a></strong><br />
+ </dt>
+ <dd>
+ The bitcode version (not LLVM version) of the file read by the analyzer.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item_file_size"><strong>File Size</strong></a></strong><br />
+ </dt>
+ <dd>
+ The size, in bytes, of the entire bitcode file.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item_module_bytes"><strong>Module Bytes</strong></a></strong><br />
+ </dt>
+ <dd>
+ The size, in bytes, of the module block. Percentage is relative to File Size.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item_function_bytes"><strong>Function Bytes</strong></a></strong><br />
+ </dt>
+ <dd>
+ The size, in bytes, of all the function blocks. Percentage is relative to File
+ Size.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item_global_types_bytes"><strong>Global Types Bytes</strong></a></strong><br />
+ </dt>
+ <dd>
+ 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.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item_constant_pool_bytes"><strong>Constant Pool Bytes</strong></a></strong><br />
+ </dt>
+ <dd>
+ The size, in bytes, of the Constant Pool Blocks Percentage is relative to File
+ Size.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item_module_globals_bytes"><strong>Module Globals Bytes</strong></a></strong><br />
+ </dt>
+ <dd>
+ Ths size, in bytes, of the Global Variable Definitions and their initializers.
+ Percentage is relative to File Size.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item_instruction_list_bytes"><strong>Instruction List Bytes</strong></a></strong><br />
+ </dt>
+ <dd>
+ 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.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item_compaction_table_bytes"><strong>Compaction Table Bytes</strong></a></strong><br />
+ </dt>
+ <dd>
+ 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.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item_symbol_table_bytes"><strong>Symbol Table Bytes</strong></a></strong><br />
+ </dt>
+ <dd>
+ 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.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item_dependent_libraries_bytes"><strong>Dependent Libraries Bytes</strong></a></strong><br />
+ </dt>
+ <dd>
+ 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.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item_number_of_bitcode_blocks"><strong>Number Of Bitcode Blocks</strong></a></strong><br />
+ </dt>
+ <dd>
+ The total number of blocks of any kind in the bitcode file.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item_number_of_functions"><strong>Number Of Functions</strong></a></strong><br />
+ </dt>
+ <dd>
+ The total number of function definitions in the bitcode file.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item_number_of_types"><strong>Number Of Types</strong></a></strong><br />
+ </dt>
+ <dd>
+ The total number of types defined in the Global Types Pool.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item_number_of_constants"><strong>Number Of Constants</strong></a></strong><br />
+ </dt>
+ <dd>
+ The total number of constants (of any type) defined in the Constant Pool.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item_number_of_basic_blocks"><strong>Number Of Basic Blocks</strong></a></strong><br />
+ </dt>
+ <dd>
+ The total number of basic blocks defined in all functions in the bitcode file.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item_number_of_instructions"><strong>Number Of Instructions</strong></a></strong><br />
+ </dt>
+ <dd>
+ The total number of instructions defined in all functions in the bitcode file.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item_number_of_long_instructions"><strong>Number Of Long Instructions</strong></a></strong><br />
+ </dt>
+ <dd>
+ 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.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item_number_of_operands"><strong>Number Of Operands</strong></a></strong><br />
+ </dt>
+ <dd>
+ The total number of operands used in all instructions in the bitcode file.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item_number_of_compaction_tables"><strong>Number Of Compaction Tables</strong></a></strong><br />
+ </dt>
+ <dd>
+ The total number of compaction tables in all functions in the bitcode file.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item_number_of_symbol_tables"><strong>Number Of Symbol Tables</strong></a></strong><br />
+ </dt>
+ <dd>
+ The total number of symbol tables in all functions in the bitcode file.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item_number_of_dependent_libs"><strong>Number Of Dependent Libs</strong></a></strong><br />
+ </dt>
+ <dd>
+ The total number of dependent libraries found in the bitcode file.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item_total_instruction_size"><strong>Total Instruction Size</strong></a></strong><br />
+ </dt>
+ <dd>
+ The total size of the instructions in all functions in the bitcode file.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item_average_instruction_size"><strong>Average Instruction Size</strong></a></strong><br />
+ </dt>
+ <dd>
+ 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.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item_maximum_type_slot_number"><strong>Maximum Type Slot Number</strong></a></strong><br />
+ </dt>
+ <dd>
+ The maximum value used for a type's slot number. Larger slot number values take
+ more bytes to encode.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item_maximum_value_slot_number"><strong>Maximum Value Slot Number</strong></a></strong><br />
+ </dt>
+ <dd>
+ The maximum value used for a value's slot number. Larger slot number values take
+ more bytes to encode.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item_bytes_per_value"><strong>Bytes Per Value</strong></a></strong><br />
+ </dt>
+ <dd>
+ 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.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item_bytes_per_global"><strong>Bytes Per Global</strong></a></strong><br />
+ </dt>
+ <dd>
+ The average size of a global definition (constants and global variables).
+ </dd>
+ <p></p>
+ <dt><strong><a name="item_bytes_per_function"><strong>Bytes Per Function</strong></a></strong><br />
+ </dt>
+ <dd>
+ The average number of bytes per function definition. This is computed by
+ dividing Function Bytes by Number Of Functions.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__23_of_vbr_32_2dbit_integers"><strong># of VBR 32-bit Integers</strong></a></strong><br />
+ </dt>
+ <dd>
+ The total number of 32-bit integers encoded using the Variable Bit Rate
+ encoding scheme.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__23_of_vbr_64_2dbit_integers"><strong># of VBR 64-bit Integers</strong></a></strong><br />
+ </dt>
+ <dd>
+ The total number of 64-bit integers encoded using the Variable Bit Rate encoding
+ scheme.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__23_of_vbr_compressed_bytes"><strong># of VBR Compressed Bytes</strong></a></strong><br />
+ </dt>
+ <dd>
+ The total number of bytes consumed by the 32-bit and 64-bit integers that use
+ the Variable Bit Rate encoding scheme.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__23_of_vbr_expanded_bytes"><strong># of VBR Expanded Bytes</strong></a></strong><br />
+ </dt>
+ <dd>
+ 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.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item_bytes_saved_with_vbr"><strong>Bytes Saved With VBR</strong></a></strong><br />
+ </dt>
+ <dd>
+ The total number of bytes saved by using the Variable Bit Rate encoding scheme.
+ The percentage is relative to # of VBR Expanded Bytes.
+ </dd>
+ <p></p></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="item_type"><strong>Type</strong></a></strong><br />
+ </dt>
+ <dd>
+ The type signature of the function.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item_byte_size"><strong>Byte Size</strong></a></strong><br />
+ </dt>
+ <dd>
+ The total number of bytes in the function's block.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item_basic_blocks"><strong>Basic Blocks</strong></a></strong><br />
+ </dt>
+ <dd>
+ The number of basic blocks defined by the function.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item_instructions"><strong>Instructions</strong></a></strong><br />
+ </dt>
+ <dd>
+ The number of instructions defined by the function.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item_long_instructions"><strong>Long Instructions</strong></a></strong><br />
+ </dt>
+ <dd>
+ The number of instructions using the long instruction format in the function.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item_operands"><strong>Operands</strong></a></strong><br />
+ </dt>
+ <dd>
+ The number of operands used by all instructions in the function.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item_instruction_size"><strong>Instruction Size</strong></a></strong><br />
+ </dt>
+ <dd>
+ The number of bytes consumed by instructions in the function.
+ </dd>
+ <p></p>
+ <dt><strong><strong>Average Instruction Size</strong></strong><br />
+ </dt>
+ <dd>
+ The average number of bytes consumed by the instructions in the funtion. This
+ value is computed by dividing Instruction Size by Instructions.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item_bytes_per_instruction"><strong>Bytes Per Instruction</strong></a></strong><br />
+ </dt>
+ <dd>
+ 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.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item_number_of_vbr_32_2dbit_integers"><strong>Number of VBR 32-bit Integers</strong></a></strong><br />
+ </dt>
+ <dd>
+ The total number of 32-bit integers found in this function (for any use).
+ </dd>
+ <p></p>
+ <dt><strong><a name="item_number_of_vbr_64_2dbit_integers"><strong>Number of VBR 64-bit Integers</strong></a></strong><br />
+ </dt>
+ <dd>
+ The total number of 64-bit integers found in this function (for any use).
+ </dd>
+ <p></p>
+ <dt><strong><a name="item_number_of_vbr_compressed_bytes"><strong>Number of VBR Compressed Bytes</strong></a></strong><br />
+ </dt>
+ <dd>
+ 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.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item_number_of_vbr_expanded_bytes"><strong>Number of VBR Expanded Bytes</strong></a></strong><br />
+ </dt>
+ <dd>
+ 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.
+ </dd>
+ <p></p>
+ <dt><strong><strong>Bytes Saved With VBR</strong></strong><br />
+ </dt>
+ <dd>
+ 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.
+ </dd>
+ <p></p></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>
Index: llvm-www/releases/2.1/docs/CommandGuide/html/llvm-config.html
diff -c /dev/null llvm-www/releases/2.1/docs/CommandGuide/html/llvm-config.html:1.1
*** /dev/null Thu Sep 27 00:43:39 2007
--- llvm-www/releases/2.1/docs/CommandGuide/html/llvm-config.html Thu Sep 27 00:43:19 2007
***************
*** 0 ****
--- 1,201 ----
+ <!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" />
+ <link rev="made" href="mailto:root at localhost" />
+ </head>
+
+ <body>
+
+ <p><a name="__index__"></a></p>
+ <!-- INDEX BEGIN -->
+ <!--
+
+ <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>
+ -->
+ <!-- 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="item__2d_2dversion"><strong>--version</strong></a></strong><br />
+ </dt>
+ <dd>
+ Print the version number of LLVM.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2d_2dhelp"><strong>--help</strong></a></strong><br />
+ </dt>
+ <dd>
+ Print a summary of <strong>llvm-config</strong> arguments.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2d_2dprefix"><strong>--prefix</strong></a></strong><br />
+ </dt>
+ <dd>
+ Print the installation prefix for LLVM.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2d_2dsrc_2droot"><strong>--src-root</strong></a></strong><br />
+ </dt>
+ <dd>
+ Print the source root from which LLVM was built.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2d_2dobj_2droot"><strong>--obj-root</strong></a></strong><br />
+ </dt>
+ <dd>
+ Print the object root used to build LLVM.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2d_2dbindir"><strong>--bindir</strong></a></strong><br />
+ </dt>
+ <dd>
+ Print the installation directory for LLVM binaries.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2d_2dincludedir"><strong>--includedir</strong></a></strong><br />
+ </dt>
+ <dd>
+ Print the installation directory for LLVM headers.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2d_2dlibdir"><strong>--libdir</strong></a></strong><br />
+ </dt>
+ <dd>
+ Print the installation directory for LLVM libraries.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2d_2dcxxflags"><strong>--cxxflags</strong></a></strong><br />
+ </dt>
+ <dd>
+ Print the C++ compiler flags needed to use LLVM headers.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2d_2dldflags"><strong>--ldflags</strong></a></strong><br />
+ </dt>
+ <dd>
+ Print the flags needed to link against LLVM libraries.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2d_2dlibs"><strong>--libs</strong></a></strong><br />
+ </dt>
+ <dd>
+ Print all the libraries needed to link against the specified LLVM
+ <em>components</em>, including any dependencies.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2d_2dlibnames"><strong>--libnames</strong></a></strong><br />
+ </dt>
+ <dd>
+ 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.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2d_2dlibfiles"><strong>--libfiles</strong></a></strong><br />
+ </dt>
+ <dd>
+ 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.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2d_2dcomponents"><strong>--components</strong></a></strong><br />
+ </dt>
+ <dd>
+ Print all valid component names.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2d_2dtargets_2dbuilt"><strong>--targets-built</strong></a></strong><br />
+ </dt>
+ <dd>
+ Print the component names for all targets supported by this copy of LLVM.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2d_2dbuild_2dmode"><strong>--build-mode</strong></a></strong><br />
+ </dt>
+ <dd>
+ Print the build mode used when LLVM was built (e.g. Debug or Release)
+ </dd>
+ <p></p></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="item_all"><strong>all</strong></a></strong><br />
+ </dt>
+ <dd>
+ Includes all LLVM libaries. The default if no components are specified.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item_backend"><strong>backend</strong></a></strong><br />
+ </dt>
+ <dd>
+ Includes either a native backend or the C backend.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item_engine"><strong>engine</strong></a></strong><br />
+ </dt>
+ <dd>
+ Includes either a native JIT or the bitcode interpreter.
+ </dd>
+ <p></p></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>
Index: llvm-www/releases/2.1/docs/CommandGuide/html/llvm-db.html
diff -c /dev/null llvm-www/releases/2.1/docs/CommandGuide/html/llvm-db.html:1.1
*** /dev/null Thu Sep 27 00:43:39 2007
--- llvm-www/releases/2.1/docs/CommandGuide/html/llvm-db.html Thu Sep 27 00:43:19 2007
***************
*** 0 ****
--- 1,43 ----
+ <!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-db</title>
+ <link rel="stylesheet" href="manpage.css" type="text/css" />
+ <link rev="made" href="mailto:root at localhost" />
+ </head>
+
+ <body>
+
+ <p><a name="__index__"></a></p>
+ <!-- INDEX BEGIN -->
+ <!--
+
+ <ul>
+
+ <li><a href="#name">NAME</a></li>
+ <li><a href="#synopsis">SYNOPSIS</a></li>
+ <li><a href="#authors">AUTHORS</a></li>
+ </ul>
+ -->
+ <!-- INDEX END -->
+
+ <p>
+ </p>
+ <hr />
+ <h1><a name="name">NAME</a></h1>
+ <p>llvm-db - LLVM debugger (alpha)</p>
+ <p>
+ </p>
+ <hr />
+ <h1><a name="synopsis">SYNOPSIS</a></h1>
+ <p>Details coming soon. Please see
+ <a href="http://llvm.org/docs/SourceLevelDebugging.html">http://llvm.org/docs/SourceLevelDebugging.html</a> in the meantime.</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>
Index: llvm-www/releases/2.1/docs/CommandGuide/html/llvm-dis.html
diff -c /dev/null llvm-www/releases/2.1/docs/CommandGuide/html/llvm-dis.html:1.1
*** /dev/null Thu Sep 27 00:43:39 2007
--- llvm-www/releases/2.1/docs/CommandGuide/html/llvm-dis.html Thu Sep 27 00:43:19 2007
***************
*** 0 ****
--- 1,97 ----
+ <!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" />
+ <link rev="made" href="mailto:root at localhost" />
+ </head>
+
+ <body>
+
+ <p><a name="__index__"></a></p>
+ <!-- INDEX BEGIN -->
+ <!--
+
+ <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>
+ -->
+ <!-- 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="item__2df"><strong>-f</strong></a></strong><br />
+ </dt>
+ <dd>
+ Force overwrite. Normally, <strong>llvm-dis</strong> will refuse to overwrite
+ an output file that already exists. With this option, <strong>llvm-dis</strong>
+ will overwrite the output file.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2d_2dhelp"><strong>--help</strong></a></strong><br />
+ </dt>
+ <dd>
+ Print a summary of command line options.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2do_filename"><strong>-o</strong> <em>filename</em></a></strong><br />
+ </dt>
+ <dd>
+ Specify the output file name. If <em>filename</em> is -, then the output is sent
+ to standard output.
+ </dd>
+ <p></p></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>
Index: llvm-www/releases/2.1/docs/CommandGuide/html/llvm-extract.html
diff -c /dev/null llvm-www/releases/2.1/docs/CommandGuide/html/llvm-extract.html:1.1
*** /dev/null Thu Sep 27 00:43:39 2007
--- llvm-www/releases/2.1/docs/CommandGuide/html/llvm-extract.html Thu Sep 27 00:43:19 2007
***************
*** 0 ****
--- 1,102 ----
+ <!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" />
+ <link rev="made" href="mailto:root at localhost" />
+ </head>
+
+ <body>
+
+ <p><a name="__index__"></a></p>
+ <!-- INDEX BEGIN -->
+ <!--
+
+ <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>
+ -->
+ <!-- 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="item__2df"><strong>-f</strong></a></strong><br />
+ </dt>
+ <dd>
+ Force overwrite. Normally, <strong>llvm-extract</strong> will refuse to overwrite an
+ output file that already exists. With this option, <strong>llvm-extract</strong>
+ will overwrite the output file and replace it with new bitcode.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2d_2dfunc_function_2dname"><strong>--func</strong> <em>function-name</em></a></strong><br />
+ </dt>
+ <dd>
+ Extract the function named <em>function-name</em> from the LLVM bitcode.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2d_2dhelp"><strong>--help</strong></a></strong><br />
+ </dt>
+ <dd>
+ Print a summary of command line options.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2do_filename"><strong>-o</strong> <em>filename</em></a></strong><br />
+ </dt>
+ <dd>
+ Specify the output filename. If filename is ``-'' (the default), then
+ <strong>llvm-extract</strong> sends its output to standard output.
+ </dd>
+ <p></p></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>
Index: llvm-www/releases/2.1/docs/CommandGuide/html/llvm-ld.html
diff -c /dev/null llvm-www/releases/2.1/docs/CommandGuide/html/llvm-ld.html:1.1
*** /dev/null Thu Sep 27 00:43:39 2007
--- llvm-www/releases/2.1/docs/CommandGuide/html/llvm-ld.html Thu Sep 27 00:43:19 2007
***************
*** 0 ****
--- 1,377 ----
+ <!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" />
+ <link rev="made" href="mailto:root at localhost" />
+ </head>
+
+ <body>
+
+ <p><a name="__index__"></a></p>
+ <!-- INDEX BEGIN -->
+ <!--
+
+ <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>
+ -->
+ <!-- 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="item__2dhelp"><strong>-help</strong></a></strong><br />
+ </dt>
+ <dd>
+ Print a summary of command line options.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2dv"><strong>-v</strong></a></strong><br />
+ </dt>
+ <dd>
+ Specifies verbose mode. In this mode the linker will print additional
+ information about the actions it takes, programs it executes, etc.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2dstats"><strong>-stats</strong></a></strong><br />
+ </dt>
+ <dd>
+ Print statistics.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2dtime_2dpasses"><strong>-time-passes</strong></a></strong><br />
+ </dt>
+ <dd>
+ Record the amount of time needed for each pass and print it to standard
+ error.
+ </dd>
+ <p></p></dl>
+ <p>
+ </p>
+ <h2><a name="input_output_options">Input/Output Options</a></h2>
+ <dl>
+ <dt><strong><a name="item__2do_filename"><strong>-o</strong> <em>filename</em></a></strong><br />
+ </dt>
+ <dd>
+ 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>a.out</em> for compatibility with <strong>ld</strong>. The output will be written to
+ <em>filename</em>.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2dlname"><strong>-l</strong><em>name</em></a></strong><br />
+ </dt>
+ <dd>
+ This option specifies the <em>name</em> of a library to search when resolving symbols
+ for the program. Only the base name should be specified as <em>name</em>, without a
+ <em>lib</em> prefix or any suffix.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2dlpath"><strong>-L</strong><em>Path</em></a></strong><br />
+ </dt>
+ <dd>
+ This option tells <strong>llvm-ld</strong> to look in <em>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.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2dlink_2das_2dlibrary"><strong>-link-as-library</strong></a></strong><br />
+ </dt>
+ <dd>
+ Link the bitcode files together as a library, not an executable. In this mode,
+ undefined symbols will be permitted.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2dr"><strong>-r</strong></a></strong><br />
+ </dt>
+ <dd>
+ An alias for -link-as-library.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2dmarch_3dtarget"><strong>-march=</strong><code>target</code></a></strong><br />
+ </dt>
+ <dd>
+ Specifies the kind of machine for which code or assembly should be generated.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2dnative"><strong>-native</strong></a></strong><br />
+ </dt>
+ <dd>
+ Generate a native machine code executable.
+ </dd>
+ <dd>
+ <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>
+ </dd>
+ <dd>
+ <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>
+ <p></p>
+ <dt><strong><a name="item__2dnative_2dcbe"><strong>-native-cbe</strong></a></strong><br />
+ </dt>
+ <dd>
+ Generate a native machine code executable with the LLVM C backend.
+
+ </dd>
+ <dd>
+ <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>
+ <p></p></dl>
+ <p>
+ </p>
+ <h2><a name="optimization_options">Optimization Options</a></h2>
+ <dl>
+ <dt><strong><a name="item__2do0"><strong>-O0</strong></a></strong><br />
+ </dt>
+ <dd>
+ An alias for the -O1 option.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2do1"><strong>-O1</strong></a></strong><br />
+ </dt>
+ <dd>
+ Optimize for linking speed, not execution speed. The optimizer will attempt to
+ reduce the size of the linked program to reduce I/O but will not otherwise
+ perform any link-time optimizations.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2do2"><strong>-O2</strong></a></strong><br />
+ </dt>
+ <dd>
+ Perform only the minimal or required set of scalar optimizations.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2d03"><strong>-03</strong></a></strong><br />
+ </dt>
+ <dd>
+ An alias for the -O2 option.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2d04"><strong>-04</strong></a></strong><br />
+ </dt>
+ <dd>
+ Perform the standard link time inter-procedural optimizations. This will
+ attempt to optimize the program taking the entire program into consideration.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2do5"><strong>-O5</strong></a></strong><br />
+ </dt>
+ <dd>
+ Perform aggressive link time optimizations. This is the same as -O4 but works
+ more aggressively to optimize the program.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2ddisable_2dinlining"><strong>-disable-inlining</strong></a></strong><br />
+ </dt>
+ <dd>
+ Do not run the inlining pass. Functions will not be inlined into other
+ functions.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2ddisable_2dopt"><strong>-disable-opt</strong></a></strong><br />
+ </dt>
+ <dd>
+ Completely disable optimization. The various <strong>-On</strong> options will be ignored and
+ no link time optimization passes will be run.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2ddisable_2dinternalize"><strong>-disable-internalize</strong></a></strong><br />
+ </dt>
+ <dd>
+ Do not mark all symbols as internal.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2dverify_2deach"><strong>-verify-each</strong></a></strong><br />
+ </dt>
+ <dd>
+ Run the verification pass after each of the passes to verify intermediate
+ results.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2dstrip_2dall"><strong>-strip-all</strong></a></strong><br />
+ </dt>
+ <dd>
+ Strip all debug and symbol information from the executable to make it smaller.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2dstrip_2ddebug"><strong>-strip-debug</strong></a></strong><br />
+ </dt>
+ <dd>
+ Strip all debug information from the executable to make it smaller.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2ds"><strong>-s</strong></a></strong><br />
+ </dt>
+ <dd>
+ An alias for <strong>-strip-all</strong>.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2ds"><strong>-S</strong></a></strong><br />
+ </dt>
+ <dd>
+ An alias for <strong>-strip-debug</strong>.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2dexport_2ddynamic"><strong>-export-dynamic</strong></a></strong><br />
+ </dt>
+ <dd>
+ An alias for <strong>-disable-internalize</strong>
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2dload_module"><strong>-load</strong> <em>module</em></a></strong><br />
+ </dt>
+ <dd>
+ Load an optimization module, <em>module</em>, which is expected to be a dynamic
+ library that provides the function name <code>RunOptimizations</code>. This function will
+ be passed the PassManager, and the optimization level (values 0-5 based on the
+ <strong>-On</strong> option). This function may add passes to the PassManager that should be
+ run. This feature allows the optimization passes of <strong>llvm-ld</strong> to be extended.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2dpost_2dlink_2doptpath"><strong>-post-link-opt</strong><em>Path</em></a></strong><br />
+ </dt>
+ <dd>
+ 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>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:
+ </dd>
+ <dd>
+ <pre>
+ #!/bin/bash
+ cp $1 $2</pre>
+ </dd>
+ <p></p></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>
Index: llvm-www/releases/2.1/docs/CommandGuide/html/llvm-link.html
diff -c /dev/null llvm-www/releases/2.1/docs/CommandGuide/html/llvm-link.html:1.1
*** /dev/null Thu Sep 27 00:43:39 2007
--- llvm-www/releases/2.1/docs/CommandGuide/html/llvm-link.html Thu Sep 27 00:43:19 2007
***************
*** 0 ****
--- 1,118 ----
+ <!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" />
+ <link rev="made" href="mailto:root at localhost" />
+ </head>
+
+ <body>
+
+ <p><a name="__index__"></a></p>
+ <!-- INDEX BEGIN -->
+ <!--
+
+ <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>
+ -->
+ <!-- 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="item__2dl_directory"><strong>-L</strong> <em>directory</em></a></strong><br />
+ </dt>
+ <dd>
+ Add the specified <em>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.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2df"><strong>-f</strong></a></strong><br />
+ </dt>
+ <dd>
+ Overwrite output files. By default, <strong>llvm-link</strong> will not overwrite an output
+ file if it already exists.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2do_filename"><strong>-o</strong> <em>filename</em></a></strong><br />
+ </dt>
+ <dd>
+ Specify the output file name. If <em>filename</em> is <code>-</code>, then <strong>llvm-link</strong> will
+ write its output to standard output.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2dd"><strong>-d</strong></a></strong><br />
+ </dt>
+ <dd>
+ If specified, <strong>llvm-link</strong> prints a human-readable version of the output
+ bitcode file to standard error.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2d_2dhelp"><strong>--help</strong></a></strong><br />
+ </dt>
+ <dd>
+ Print a summary of command line options.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2dv"><strong>-v</strong></a></strong><br />
+ </dt>
+ <dd>
+ 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.
+ </dd>
+ <p></p></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>
Index: llvm-www/releases/2.1/docs/CommandGuide/html/llvm-nm.html
diff -c /dev/null llvm-www/releases/2.1/docs/CommandGuide/html/llvm-nm.html:1.1
*** /dev/null Thu Sep 27 00:43:39 2007
--- llvm-www/releases/2.1/docs/CommandGuide/html/llvm-nm.html Thu Sep 27 00:43:19 2007
***************
*** 0 ****
--- 1,181 ----
+ <!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" />
+ <link rev="made" href="mailto:root at localhost" />
+ </head>
+
+ <body>
+
+ <p><a name="__index__"></a></p>
+ <!-- INDEX BEGIN -->
+ <!--
+
+ <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>
+ -->
+ <!-- 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="item_u">U</a></strong><br />
+ </dt>
+ <dd>
+ Named object is referenced but undefined in this bitcode file
+ </dd>
+ <p></p>
+ <dt><strong><a name="item_c">C</a></strong><br />
+ </dt>
+ <dd>
+ Common (multiple definitions link together into one def)
+ </dd>
+ <p></p>
+ <dt><strong><a name="item_w">W</a></strong><br />
+ </dt>
+ <dd>
+ Weak reference (multiple definitions link together into zero or one definitions)
+ </dd>
+ <p></p>
+ <dt><strong><a name="item_t">t</a></strong><br />
+ </dt>
+ <dd>
+ Local function (text) object
+ </dd>
+ <p></p>
+ <dt><strong><a name="item_t">T</a></strong><br />
+ </dt>
+ <dd>
+ Global function (text) object
+ </dd>
+ <p></p>
+ <dt><strong><a name="item_d">d</a></strong><br />
+ </dt>
+ <dd>
+ Local data object
+ </dd>
+ <p></p>
+ <dt><strong><a name="item_d">D</a></strong><br />
+ </dt>
+ <dd>
+ Global data object
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__3f">?</a></strong><br />
+ </dt>
+ <dd>
+ Something unrecognizable
+ </dd>
+ <p></p></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="item__2dp"><strong>-P</strong></a></strong><br />
+ </dt>
+ <dd>
+ Use POSIX.2 output format. Alias for <strong>--format=posix</strong>.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item_b"><strong>-B</strong> (default)</a></strong><br />
+ </dt>
+ <dd>
+ Use BSD output format. Alias for <strong>--format=bsd</strong>.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2d_2dhelp"><strong>--help</strong></a></strong><br />
+ </dt>
+ <dd>
+ Print a summary of command-line options and their meanings.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2d_2ddefined_2donly"><strong>--defined-only</strong></a></strong><br />
+ </dt>
+ <dd>
+ 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.)
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2d_2dextern_2donly_2c__2dg"><strong>--extern-only</strong>, <strong>-g</strong></a></strong><br />
+ </dt>
+ <dd>
+ Print only symbols whose definitions are external; that is, accessible
+ from other bitcode files.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2d_2dundefined_2donly_2c__2du"><strong>--undefined-only</strong>, <strong>-u</strong></a></strong><br />
+ </dt>
+ <dd>
+ Print only symbols referenced but not defined in this bitcode file.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2d_2dformat_3dfmt_2c__2df"><strong>--format=</strong><em>fmt</em>, <strong>-f</strong></a></strong><br />
+ </dt>
+ <dd>
+ 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>.
+ </dd>
+ <p></p></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>, ar(1), <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>
Index: llvm-www/releases/2.1/docs/CommandGuide/html/llvm-prof.html
diff -c /dev/null llvm-www/releases/2.1/docs/CommandGuide/html/llvm-prof.html:1.1
*** /dev/null Thu Sep 27 00:43:39 2007
--- llvm-www/releases/2.1/docs/CommandGuide/html/llvm-prof.html Thu Sep 27 00:43:19 2007
***************
*** 0 ****
--- 1,93 ----
+ <!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" />
+ <link rev="made" href="mailto:root at localhost" />
+ </head>
+
+ <body>
+
+ <p><a name="__index__"></a></p>
+ <!-- INDEX BEGIN -->
+ <!--
+
+ <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>
+ -->
+ <!-- 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>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>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>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="item__2d_2dannotated_2dllvm_or__2da"><strong>--annotated-llvm</strong> or <strong>-A</strong></a></strong><br />
+ </dt>
+ <dd>
+ 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.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2d_2dprint_2dall_2dcode"><strong>--print-all-code</strong></a></strong><br />
+ </dt>
+ <dd>
+ Using this option enables the <strong>--annotated-llvm</strong> option, but it
+ prints the entire module, instead of just the most commonly executed
+ functions.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2d_2dtime_2dpasses"><strong>--time-passes</strong></a></strong><br />
+ </dt>
+ <dd>
+ Record the amount of time needed for each pass and print it to standard
+ error.
+ </dd>
+ <p></p></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>
Index: llvm-www/releases/2.1/docs/CommandGuide/html/llvm-ranlib.html
diff -c /dev/null llvm-www/releases/2.1/docs/CommandGuide/html/llvm-ranlib.html:1.1
*** /dev/null Thu Sep 27 00:43:39 2007
--- llvm-www/releases/2.1/docs/CommandGuide/html/llvm-ranlib.html Thu Sep 27 00:43:19 2007
***************
*** 0 ****
--- 1,91 ----
+ <!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" />
+ <link rev="made" href="mailto:root at localhost" />
+ </head>
+
+ <body>
+
+ <p><a name="__index__"></a></p>
+ <!-- INDEX BEGIN -->
+ <!--
+
+ <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>
+ -->
+ <!-- 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>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="item_archive_2dfile"><em>archive-file</em></a></strong><br />
+ </dt>
+ <dd>
+ Specifies the archive-file to which the symbol table is added or updated.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2d_2dversion"><em>--version</em></a></strong><br />
+ </dt>
+ <dd>
+ Print the version of <strong>llvm-ranlib</strong> and exit without building a symbol table.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2d_2dhelp"><em>--help</em></a></strong><br />
+ </dt>
+ <dd>
+ Print usage help for <strong>llvm-ranlib</strong> and exit without building a symbol table.
+ </dd>
+ <p></p></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>
Index: llvm-www/releases/2.1/docs/CommandGuide/html/llvm-upgrade.html
diff -c /dev/null llvm-www/releases/2.1/docs/CommandGuide/html/llvm-upgrade.html:1.1
*** /dev/null Thu Sep 27 00:43:39 2007
--- llvm-www/releases/2.1/docs/CommandGuide/html/llvm-upgrade.html Thu Sep 27 00:43:19 2007
***************
*** 0 ****
--- 1,97 ----
+ <!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-upgrade</title>
+ <link rel="stylesheet" href="manpage.css" type="text/css" />
+ <link rev="made" href="mailto:root at localhost" />
+ </head>
+
+ <body>
+
+ <p><a name="__index__"></a></p>
+ <!-- INDEX BEGIN -->
+ <!--
+
+ <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>
+ -->
+ <!-- INDEX END -->
+
+ <p>
+ </p>
+ <hr />
+ <h1><a name="name">NAME</a></h1>
+ <p>llvm-upgrade - LLVM assembly upgrade tool</p>
+ <p>
+ </p>
+ <hr />
+ <h1><a name="synopsis">SYNOPSIS</a></h1>
+ <p><strong>llvm-upgrade</strong> [<em>options</em>] [<em>filename</em>]</p>
+ <p>
+ </p>
+ <hr />
+ <h1><a name="description">DESCRIPTION</a></h1>
+ <p><strong>llvm-upgrade</strong> is the LLVM assembly upgrade tool. It reads a file containing
+ human-readable LLVM assembly language, and upgrades that assembly to the current
+ version of LLVM. If the input is in the form currently accepted by LLVM, then
+ no upgrades are performed.</p>
+ <p>The expected usage of this tool is as a filter, like this:</p>
+ <p><strong>llvm-1.9/bin/llvm-dis < 1.9.bc | llvm-upgrade | llvm-2.0/bin/llvm-as -o 2.0.bc</strong></p>
+ <p>If <em>filename</em> is omitted or is <code>-</code>, then <strong>llvm-upgrade</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-upgrade</strong> sends its output to standard output.</p>
+ <p>
+ </p>
+ <hr />
+ <h1><a name="options">OPTIONS</a></h1>
+ <dl>
+ <dt><strong><a name="item__2df"><strong>-f</strong></a></strong><br />
+ </dt>
+ <dd>
+ Force overwrite. Normally, <strong>llvm-upgrade</strong> will refuse to overwrite an
+ output file that already exists. With this option, <strong>llvm-upgrade</strong>
+ will overwrite the output file.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2d_2dhelp"><strong>--help</strong></a></strong><br />
+ </dt>
+ <dd>
+ Print a summary of command line options.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2do_filename"><strong>-o</strong> <em>filename</em></a></strong><br />
+ </dt>
+ <dd>
+ Specify the output file name. If <em>filename</em> is <code>-</code>, then <strong>llvm-upgrade</strong>
+ sends its output to standard output.
+ </dd>
+ <p></p></dl>
+ <p>
+ </p>
+ <hr />
+ <h1><a name="exit_status">EXIT STATUS</a></h1>
+ <p>If <strong>llvm-upgrade</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>, <a href="././llvm-dis.html">llvm-dis</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>
Index: llvm-www/releases/2.1/docs/CommandGuide/html/llvm2cpp.html
diff -c /dev/null llvm-www/releases/2.1/docs/CommandGuide/html/llvm2cpp.html:1.1
*** /dev/null Thu Sep 27 00:43:39 2007
--- llvm-www/releases/2.1/docs/CommandGuide/html/llvm2cpp.html Thu Sep 27 00:43:19 2007
***************
*** 0 ****
--- 1,282 ----
+ <!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>llvm2cpp</title>
+ <link rel="stylesheet" href="manpage.css" type="text/css" />
+ <link rev="made" href="mailto:root at localhost" />
+ </head>
+
+ <body>
+
+ <p><a name="__index__"></a></p>
+ <!-- INDEX BEGIN -->
+ <!--
+
+ <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="#notes">NOTES</a></li>
+ <li><a href="#authors">AUTHORS</a></li>
+ </ul>
+ -->
+ <!-- INDEX END -->
+
+ <p>
+ </p>
+ <hr />
+ <h1><a name="name">NAME</a></h1>
+ <p>llvm2xpp - LLVM bitcode to LLVM C++ IR translator</p>
+ <p>
+ </p>
+ <hr />
+ <h1><a name="synopsis">SYNOPSIS</a></h1>
+ <p><strong>llvm2cpp</strong> [<em>options</em>] [<em>filename</em>]</p>
+ <p>
+ </p>
+ <hr />
+ <h1><a name="description">DESCRIPTION</a></h1>
+ <p><strong>llvm2cpp</strong> translates from LLVM bitcode (.bc files) to a
+ corresponding C++ source file that will make calls against the LLVM C++ API to
+ build the same module as the input. By default, the C++ output is a complete
+ program that builds the module, verifies it and then emits the module as
+ LLVM assembly. This technique assists with testing because the input to
+ <strong>llvm2cpp</strong> and the output of the generated C++ program should be identical.</p>
+ <p>If <em>filename</em> is omitted or is <code>-</code>, then <strong>llvm2cpp</strong> reads its input from
+ standard input.</p>
+ <p>If an output file is not specified with the <strong>-o</strong> option, then
+ <strong>llvm2cpp</strong> sends its output to a file or standard output by following
+ these rules:</p>
+ <ul>
+ <li></li>
+ If the input is standard input, then the output is standard output.
+ <p></p>
+ <li></li>
+ If the input is a file that ends with <code>.bc</code>, then the output file is of
+ the same name, except that the suffix is changed to <code>.cpp</code>.
+ <p></p>
+ <li></li>
+ If the input is a file that does not end with the <code>.bc</code> suffix, then the
+ output file has the same name as the input file, except that the <code>.cpp</code>
+ suffix is appended.
+ <p></p></ul>
+ <p>
+ </p>
+ <hr />
+ <h1><a name="options">OPTIONS</a></h1>
+ <dl>
+ <dt><strong><a name="item__2df"><strong>-f</strong></a></strong><br />
+ </dt>
+ <dd>
+ Force overwrite. Normally, <strong>llvm2cpp</strong> will refuse to overwrite an
+ output file that already exists. With this option, <strong>llvm2cpp</strong>
+ will overwrite the output file and replace it with new C++ source code.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2d_2dhelp"><strong>--help</strong></a></strong><br />
+ </dt>
+ <dd>
+ Print a summary of command line options.
+ </dd>
+ <p></p>
+ <dt><strong><strong>-f</strong></strong><br />
+ </dt>
+ <dd>
+ Normally, <strong>llvm2cpp</strong> will not overwrite an existing output file. With this
+ option, that default behavior is changed and the program will overwrite existing
+ output files.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2do_filename"><strong>-o</strong> <em>filename</em></a></strong><br />
+ </dt>
+ <dd>
+ Specify the output file name. If <em>filename</em> is <code>-</code>, then <strong>llvm2cpp</strong>
+ sends its output to standard output.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2dfuncname_functionname"><strong>-funcname</strong> <em>functionName</em></a></strong><br />
+ </dt>
+ <dd>
+ Specify the name of the function to be generated. The generated code contains a
+ single function that produces the input module. By default its name is
+ <em>makeLLVMModule</em>. The <strong>-funcname</strong> option overrides this default and allows
+ you to control the name of the generated function. This is handy in conjunction
+ with the <strong>-fragment</strong> option when you only want <strong>llvm2cpp</strong> to generate a
+ single function that produces the module. With both options, such generated code
+ could be <em>#included</em> into another program.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2dfor"><strong>-for</strong></a></strong><br />
+ </dt>
+ <dd>
+ Specify the name of the thing for which C++ code should be generated. By default
+ the entire input module is re-generated. However, use of the various <strong>-gen-*</strong>
+ options can restrict what is produced. This option indicates what that
+ restriction is.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2dgen_2dprogram"><strong>-gen-program</strong></a></strong><br />
+ </dt>
+ <dd>
+ Specify that the output should be a complete program. Such program will recreate
+ <strong>llvm2cpp</strong>'s input as an LLVM module, verify that module, and then write out
+ the module in LLVM assembly format. This is useful for doing identity tests
+ where the output of the generated program is identical to the input to
+ <strong>llvm2cpp</strong>. The LLVM DejaGnu test suite can make use of this fact. This is the
+ default form of generated output.
+ </dd>
+ <dd>
+ <p>If the <strong>-for</strong> option is given with this option, it specifies the module
+ identifier to use for the module created.</p>
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2dgen_2dmodule"><strong>-gen-module</strong></a></strong><br />
+ </dt>
+ <dd>
+ Specify that the output should be a function that regenerates the module. It is
+ assumed that this output will be #included into another program that has already
+ arranged for the correct header files to be #included. The function generated
+ takes no arguments and returns a <em>Module*</em>.
+ </dd>
+ <dd>
+ <p>If the <strong>-for</strong> option is given with this option, it specifies the module
+ identifier to use in creating the module returned by the generated function.</p>
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2dgen_2dcontents"><strong>-gen-contents</strong></a></strong><br />
+ </dt>
+ <dd>
+ Specify that the output should be a function that adds the contents of the input
+ module to another module. It is assumed that the output will be #included into
+ another program that has already arranged for the correct header files to be
+ #included. The function generated takes a single argument of type <em>Module*</em> and
+ returns that argument. Note that Module level attributes such as endianess,
+ pointer size, target triple and inline asm are not passed on from the input
+ module to the destination module. Only the sub-elements of the module (types,
+ constants, functions, global variables) will be added to the input module.
+ </dd>
+ <dd>
+ <p>If the <strong>-for</strong> option is given with this option, it specifies the module
+ identifier to set in the input module by the generated function.</p>
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2dgen_2dfunction"><strong>-gen-function</strong></a></strong><br />
+ </dt>
+ <dd>
+ Specify that the output should be a function that produces the definitions
+ necessary for a specific function to be added to a module. It is assumed that
+ the output will be #included into another program that has already arranged
+ for the correct header files to be #included. The function generated takes a
+ single argument of type <em>Module*</em> and returns the <em>Function*</em> that it added to
+ the module. Note that only those things (types, constants, etc.) directly
+ needed in the definition of the function will be placed in the generated
+ function.
+ </dd>
+ <dd>
+ <p>The <strong>-for</strong> option must be given with this option or an error will be produced.
+ The value of the option must be the name of a function in the input module for
+ which code should be generated. If the named function does not exist an error
+ will be produced.</p>
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2dgen_2dinline"><strong>-gen-inline</strong></a></strong><br />
+ </dt>
+ <dd>
+ This option is very analagous to <strong>-gen-function</strong> except that the generated
+ function will not re-produce the target function's definition. Instead, the body
+ of the target function is inserted into some other function passed as an
+ argument to the generated function. Similarly any arguments to the function must
+ be passed to the generated function. The result of the generated function is the
+ first basic block of the target function.
+ </dd>
+ <dd>
+ <p>The <strong>-for</strong> option works the same way as it does for <strong>-gen-function</strong>.</p>
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2dgen_2dvariable"><strong>-gen-variable</strong></a></strong><br />
+ </dt>
+ <dd>
+ Specify that the output should be a function that produces the definitions
+ necessary for a specific global variable to be added to a module. It is assumed
+ that the output will be #included into another program that has already arranged
+ for the correct header files to be #included. The function generated takes a
+ single argument of type <em>Module*</em> and returns the <em>GlobalVariable*</em> that it
+ added to the module. Note that only those things (types, constants, etc.)
+ directly needed in the definition of the global variable will be placed in the
+ generated function.
+ </dd>
+ <dd>
+ <p>The <strong>-for</strong> option must be given with this option or an error will be produced.
+ THe value of the option must be the name of a global variable in the input
+ module for which code should be generated. If the named global variable does not
+ exist an error will be produced.</p>
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2dgen_2dtype"><strong>-gen-type</strong></a></strong><br />
+ </dt>
+ <dd>
+ Specify that the output should be a function that produces the definitions
+ necessary for specific type to be added to a module. It is assumed that the
+ otuput will be #included into another program that has already arranged for the
+ correct header files to be #included. The function generated take a single
+ argument of type <em>Module*</em> and returns the <em>Type*</em> that it added to the
+ module. Note that the generated function will only add the necessary type
+ definitions to (possibly recursively) define the requested type.
+ </dd>
+ <dd>
+ <p>The <strong>-for</strong> option must be given with this option or an error will be produced.
+ The value of the option must be the name of a global type in the input module
+ for which code should be generated. If the named type does not exist an error
+ will be produced.</p>
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2dstats"><strong>-stats</strong></a></strong><br />
+ </dt>
+ <dd>
+ Show pass statistics (not interesting in this program).
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2dtime_2dpasses"><strong>-time-passes</strong></a></strong><br />
+ </dt>
+ <dd>
+ Show pass timing statistics (not interesting in this program).
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2dversion"><strong>-version</strong></a></strong><br />
+ </dt>
+ <dd>
+ Show the version number of this program.
+ </dd>
+ <p></p></dl>
+ <p>
+ </p>
+ <hr />
+ <h1><a name="exit_status">EXIT STATUS</a></h1>
+ <p>If <strong>llvm2cpp</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> <a href="././tblgen.html">tblgen</a></p>
+ <p>
+ </p>
+ <hr />
+ <h1><a name="notes">NOTES</a></h1>
+ <p>This tool may be removed from a future version of LLVM. Instead, its
+ functionality may be incorporated into the llc tool. It would then act similarly
+ to other targets except its output would be C++ source that could be compiled to
+ construct the input program.</p>
+ <p>
+ </p>
+ <hr />
+ <h1><a name="authors">AUTHORS</a></h1>
+ <p>Written by Reid Spencer (<a href="http://hlvm.org">http://hlvm.org</a>).</p>
+
+ </body>
+
+ </html>
Index: llvm-www/releases/2.1/docs/CommandGuide/html/llvmc.html
diff -c /dev/null llvm-www/releases/2.1/docs/CommandGuide/html/llvmc.html:1.1
*** /dev/null Thu Sep 27 00:43:39 2007
--- llvm-www/releases/2.1/docs/CommandGuide/html/llvmc.html Thu Sep 27 00:43:19 2007
***************
*** 0 ****
--- 1,525 ----
+ <!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>llvmc</title>
+ <link rel="stylesheet" href="manpage.css" type="text/css" />
+ <link rev="made" href="mailto:root at localhost" />
+ </head>
+
+ <body>
+
+ <p><a name="__index__"></a></p>
+ <!-- INDEX BEGIN -->
+ <!--
+
+ <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="#basic_operation">Basic Operation</a></li>
+ </ul>
+
+ <li><a href="#options">OPTIONS</a></li>
+ <ul>
+
+ <li><a href="#control_options">Control Options</a></li>
+ <li><a href="#optimization_options">Optimization Options</a></li>
+ <li><a href="#input_options">Input Options</a></li>
+ <li><a href="#output_options">Output Options</a></li>
+ <li><a href="#information_options">Information Options</a></li>
+ <li><a href="#language_specific_options">Language Specific Options</a></li>
+ <li><a href="#c_c___specific_options">C/C++ Specific Options</a></li>
+ <li><a href="#miscellaneous_options">Miscellaneous Options</a></li>
+ <li><a href="#advanced_options">Advanced Options</a></li>
+ <li><a href="#unimplemented_options">Unimplemented Options</a></li>
+ </ul>
+
+ <li><a href="#exit_status">EXIT STATUS</a></li>
+ <li><a href="#deficiencies">DEFICIENCIES</a></li>
+ <li><a href="#see_also">SEE ALSO</a></li>
+ <li><a href="#authors">AUTHORS</a></li>
+ </ul>
+ -->
+ <!-- INDEX END -->
+
+ <p>
+ </p>
+ <hr />
+ <h1><a name="name">NAME</a></h1>
+ <p>llvmc - The LLVM Compiler Driver (experimental)</p>
+ <p>
+ </p>
+ <hr />
+ <h1><a name="synopsis">SYNOPSIS</a></h1>
+ <p><strong>llvmc</strong> [<em>options</em>] [<em>filenames</em>...]</p>
+ <p>
+ </p>
+ <hr />
+ <h1><a name="description">DESCRIPTION</a></h1>
+ <p><strong>llvmc</strong> is a configurable driver for invoking other LLVM (and non-LLVM) tools
+ in order to compile, optimize and link software for multiple languages. For
+ those familiar with FSF's <strong>gcc</strong> tool, it is very similar. Please note that
+ <strong>llvmc</strong> is considered an experimental tool. <strong>llvmc</strong> has the following goals:</p>
+ <ul>
+ <li><strong><a name="item_provide_a_single_point_of_access_to_the_llvm_tool_">provide a single point of access to the LLVM tool set,</a></strong><br />
+ </li>
+ <li><strong><a name="item_hide_the_complexities_of_the_llvm_tools_through_a_">hide the complexities of the LLVM tools through a single interface,</a></strong><br />
+ </li>
+ <li><strong><a name="item_make_integration_of_existing_non_2dllvm_tools_simp">make integration of existing non-LLVM tools simple,</a></strong><br />
+ </li>
+ <li><strong><a name="item_extend_the_capabilities_of_minimal_front_ends_2c_a">extend the capabilities of minimal front ends, and</a></strong><br />
+ </li>
+ <li><strong><a name="item_make_the_interface_for_compiling_consistent_for_al">make the interface for compiling consistent for all languages.</a></strong><br />
+ </li>
+ </ul>
+ <p>The tool itself does nothing with a user's program. It merely invokes other
+ tools to get the compilation tasks done.</p>
+ <p>The options supported by <strong>llvmc</strong> generalize the compilation process and
+ provide a consistent and simple interface for multiple programming languages.
+ This makes it easier for developers to get their software compiled with LLVM.
+ Without <strong>llvmc</strong>, developers would need to understand how to invoke the
+ front-end compiler, optimizer, assembler, and linker in order to compile their
+ programs. <strong>llvmc</strong>'s sole mission is to trivialize that process.</p>
+ <p>
+ </p>
+ <h2><a name="basic_operation">Basic Operation</a></h2>
+ <p><strong>llvmc</strong> always takes the following basic actions:</p>
+ <ul>
+ <li><strong><a name="item_command_line_options_and_filenames_are_collected_2">Command line options and filenames are collected.</a></strong><br />
+ </li>
+ The command line options provide the marching orders to <strong>llvmc</strong> on what actions
+ it should perform. This is the <em>request</em> the user is making of <strong>llvmc</strong> and it
+ is interpreted first.
+ <p></p>
+ <li><strong><a name="item_configuration_files_are_read_2e">Configuration files are read.</a></strong><br />
+ </li>
+ Based on the options and the suffixes of the filenames presented, a set of
+ configuration files are read to configure the actions <strong>llvmc</strong> will take.
+ Configuration files are provided by either LLVM or the front end compiler tools
+ that <strong>llvmc</strong> invokes. Users generally don't need to be concerned with the
+ contents of the configuration files.
+ <p></p>
+ <li><strong><a name="item_determine_actions_to_take_2e">Determine actions to take.</a></strong><br />
+ </li>
+ The tool chain needed to complete the task is determined. This is the primary
+ work of <strong>llvmc</strong>. It breaks the request specified by the command line options
+ into a set of basic actions to be done:
+ <ul>
+ <li><strong><a name="item_input">Pre-processing: gathering/filtering compiler input (optional).</a></strong><br />
+ </li>
+ <li><strong><a name="item_translation_3a_source_language_to_bitcode_conversi">Translation: source language to bitcode conversion.</a></strong><br />
+ </li>
+ <li><strong><a name="item_assembly_3a_bitcode_to_native_code_conversion_2e">Assembly: bitcode to native code conversion.</a></strong><br />
+ </li>
+ <li><strong><a name="item_optimization_3a_conversion_of_bitcode_to_something">Optimization: conversion of bitcode to something that runs faster.</a></strong><br />
+ </li>
+ <li><strong><a name="item_linking_3a_combining_multiple_bitcode_files_to_pro">Linking: combining multiple bitcode files to produce executable program.</a></strong><br />
+ </li>
+ </ul>
+ <li><strong><a name="item_execute_actions_2e">Execute actions.</a></strong><br />
+ </li>
+ The actions determined previously are executed sequentially and then
+ <strong>llvmc</strong> terminates.
+ <p></p></ul>
+ <p>
+ </p>
+ <hr />
+ <h1><a name="options">OPTIONS</a></h1>
+ <p>
+ </p>
+ <h2><a name="control_options">Control Options</a></h2>
+ <p>Control options tell <strong>llvmc</strong> what to do at a high level. The
+ following control options are defined:</p>
+ <dl>
+ <dt><strong><a name="item__2dc_or__2d_2dcompile"><strong>-c</strong> or <strong>--compile</strong></a></strong><br />
+ </dt>
+ <dd>
+ This option specifies that the linking phase is not to be run. All
+ previous phases, if applicable will run. This is generally how a given
+ bitcode file is compiled and optimized for a source language module.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2dk_or__2d_2dlink_or_default"><strong>-k</strong> or <strong>--link</strong> or default</a></strong><br />
+ </dt>
+ <dd>
+ This option (or the lack of any control option) specifies that all stages
+ of compilation, optimization, and linking should be attempted. Source files
+ specified on the command line will be compiled and linked with objects and
+ libraries also specified.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2ds"><strong>-S</strong></a></strong><br />
+ </dt>
+ <dd>
+ This option specifies that compilation should end in the creation of
+ an LLVM assembly file that can be later converted to an LLVM object
+ file.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2de"><strong>-E</strong></a></strong><br />
+ </dt>
+ <dd>
+ This option specifies that no compilation or linking should be
+ performed. Only pre-processing, if applicable to the language being
+ compiled, is performed. For languages that support it, this will
+ result in the output containing the raw input to the compiler.
+ </dd>
+ <p></p></dl>
+ <p>
+ </p>
+ <h2><a name="optimization_options">Optimization Options</a></h2>
+ <p>Optimization with <strong>llvmc</strong> is based on goals and specified with
+ the following -O options. The specific details of which
+ optimizations run is controlled by the configuration files because
+ each source language will have different needs.</p>
+ <dl>
+ <dt><strong><a name="item_o0"><strong>-O1</strong> or <strong>-O0</strong> (default, fast compilation)</a></strong><br />
+ </dt>
+ <dd>
+ Only those optimizations that will hasten the compilation (mostly by reducing
+ the output) are applied. In general these are extremely fast and simple
+ optimizations that reduce emitted code size. The goal here is not to make the
+ resulting program fast but to make the compilation fast. If not specified,
+ this is the default level of optimization.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item_o2"><strong>-O2</strong> (basic optimization)</a></strong><br />
+ </dt>
+ <dd>
+ This level of optimization specifies a balance between generating good code
+ that will execute reasonably quickly and not spending too much time optimizing
+ the code to get there. For example, this level of optimization may include
+ things like global common sub-expression elimination, aggressive dead code
+ elimination, and scalar replication.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item_o3"><strong>-O3</strong> (aggressive optimization)</a></strong><br />
+ </dt>
+ <dd>
+ This level of optimization aggressively optimizes each set of files compiled
+ together. However, no link-time inter-procedural optimization is performed.
+ This level implies all the optimizations of the <strong>-O1</strong> and <strong>-O2</strong> optimization
+ levels, and should also provide loop optimizations and compile time
+ inter-procedural optimizations. Essentially, this level tries to do as much
+ as it can with the input it is given but doesn't do any link time IPO.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item_o4"><strong>-O4</strong> (link time optimization)</a></strong><br />
+ </dt>
+ <dd>
+ In addition to the previous three levels of optimization, this level of
+ optimization aggressively optimizes each program at link time. It employs
+ basic analysis and basic link-time inter-procedural optimizations,
+ considering the program as a whole.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item_o5"><strong>-O5</strong> (aggressive link time optimization)</a></strong><br />
+ </dt>
+ <dd>
+ This is the same as <strong>-O4</strong> except it employs aggressive analyses and
+ aggressive inter-procedural optimization.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item_o6"><strong>-O6</strong> (profile guided optimization: not implemented)</a></strong><br />
+ </dt>
+ <dd>
+ This is the same as <strong>-O5</strong> except that it employs profile-guided
+ re-optimization of the program after it has executed. Note that this implies
+ a single level of re-optimization based on run time profile analysis. Once
+ the re-optimization has completed, the profiling instrumentation is
+ removed and final optimizations are employed.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item_o7"><strong>-O7</strong> (lifelong optimization: not implemented)</a></strong><br />
+ </dt>
+ <dd>
+ This is the same as <strong>-O5</strong> and similar to <strong>-O6</strong> except that re-optimization
+ is performed through the life of the program. That is, each run will update
+ the profile by which future re-optimizations are directed.
+ </dd>
+ <p></p></dl>
+ <p>
+ </p>
+ <h2><a name="input_options">Input Options</a></h2>
+ <dl>
+ <dt><strong><a name="item__2dl_library"><strong>-l</strong> <em>LIBRARY</em></a></strong><br />
+ </dt>
+ <dd>
+ This option instructs <strong>llvmc</strong> to locate a library named <em>LIBRARY</em> and search
+ it for unresolved symbols when linking the program.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2dl_path"><strong>-L</strong> <em>path</em></a></strong><br />
+ </dt>
+ <dd>
+ This option instructs <strong>llvmc</strong> to add <em>path</em> to the list of places in which
+ the linker will
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2dx_language"><strong>-x</strong> <em>LANGUAGE</em></a></strong><br />
+ </dt>
+ <dd>
+ This option instructs <strong>llvmc</strong> to regard the following input files as
+ containing programs in the language <em>LANGUAGE</em>. Normally, input file languages
+ are identified by their suffix but this option will override that default
+ behavior. The <strong>-x</strong> option stays in effect until the end of the options or
+ a new <strong>-x</strong> option is encountered.
+ </dd>
+ <p></p></dl>
+ <p>
+ </p>
+ <h2><a name="output_options">Output Options</a></h2>
+ <dl>
+ <dt><strong><a name="item__2dmarch"><strong>-m</strong><em>arch</em></a></strong><br />
+ </dt>
+ <dd>
+ This option selects the back end code generator to use. The <em>arch</em> portion
+ of the option names the back end to use.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2d_2dnative"><strong>--native</strong></a></strong><br />
+ </dt>
+ <dd>
+ Normally, <strong>llvmc</strong> produces bitcode files at most stages of compilation.
+ With this option, <strong>llvmc</strong> will arrange for native object files to be
+ generated with the <strong>-c</strong> option, native assembly files to be generated
+ with the <strong>-S</strong> option, and native executables to be generated with the
+ <strong>--link</strong> option. In the case of the <strong>-E</strong> option, the output will not
+ differ as there is no <em>native</em> version of pre-processed output.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2do_filename"><strong>-o</strong> <em>filename</em></a></strong><br />
+ </dt>
+ <dd>
+ Specify the output file name. The contents of the file depend on other
+ options.
+ </dd>
+ <p></p></dl>
+ <p>
+ </p>
+ <h2><a name="information_options">Information Options</a></h2>
+ <dl>
+ <dt><strong><a name="item__2dn_or__2d_2dno_2dop"><strong>-n</strong> or <strong>--no-op</strong></a></strong><br />
+ </dt>
+ <dd>
+ This option tells <strong>llvmc</strong> to do everything but actually execute the
+ resulting tools. In combination with the <strong>-v</strong> option, this causes <strong>llvmc</strong>
+ to merely print out what it would have done.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2dv_or__2d_2dverbose"><strong>-v</strong> or <strong>--verbose</strong></a></strong><br />
+ </dt>
+ <dd>
+ This option will cause <strong>llvmc</strong> to print out (on standard output) each of the
+ actions it takes to accomplish the objective. The output will immediately
+ precede the invocation of other tools.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2d_2dstats"><strong>--stats</strong></a></strong><br />
+ </dt>
+ <dd>
+ Print all statistics gathered during the compilation to the standard error.
+ Note that this option is merely passed through to the sub-tools to do with
+ as they please.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2d_2dtime_2dpasses"><strong>--time-passes</strong></a></strong><br />
+ </dt>
+ <dd>
+ Record the amount of time needed for each optimization pass and print it
+ to standard error. Like <strong>--stats</strong> this option is just passed through to
+ the sub-tools to do with as they please.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2d_2dtime_2dprograms"><strong>--time-programs</strong></a></strong><br />
+ </dt>
+ <dd>
+ Record the amount of time each program (compilation tool) takes and print
+ it to the standard error.
+ </dd>
+ <p></p></dl>
+ <p>
+ </p>
+ <h2><a name="language_specific_options">Language Specific Options</a></h2>
+ <dl>
+ <dt><strong><a name="item__2dt_2cpre_3doptions"><strong>-T,pre</strong>=<em>options</em></a></strong><br />
+ </dt>
+ <dd>
+ Pass an arbitrary option to the pre-processor.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2dt_2copt_3doptions"><strong>-T,opt</strong>=<em>options</em></a></strong><br />
+ </dt>
+ <dd>
+ Pass an arbitrary option to the optimizer.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2dt_2clnk_3doptions"><strong>-T,lnk</strong>=<em>options</em></a></strong><br />
+ </dt>
+ <dd>
+ Pass an arbitrary option to the linker.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2dt_2casm_3doptions"><strong>-T,asm</strong>=<em>options</em></a></strong><br />
+ </dt>
+ <dd>
+ Pass an arbitrary option to the code generator.
+ </dd>
+ <p></p></dl>
+ <p>
+ </p>
+ <h2><a name="c_c___specific_options">C/C++ Specific Options</a></h2>
+ <dl>
+ <dt><strong><a name="item__2dipath"><strong>-I</strong><em>path</em></a></strong><br />
+ </dt>
+ <dd>
+ This option is just passed through to a C or C++ front end compiler to tell it
+ where include files can be found.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2ddsymbol"><strong>-D</strong><em>symbol</em></a></strong><br />
+ </dt>
+ <dd>
+ This option is just passed through to a C or C++ front end compiler to tell it
+ to define a symbol.
+ </dd>
+ <p></p></dl>
+ <p>
+ </p>
+ <h2><a name="miscellaneous_options">Miscellaneous Options</a></h2>
+ <dl>
+ <dt><strong><a name="item__2d_2dhelp"><strong>--help</strong></a></strong><br />
+ </dt>
+ <dd>
+ Print a summary of command line options.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2d_2dversion"><strong>--version</strong></a></strong><br />
+ </dt>
+ <dd>
+ This option will cause <strong>llvmc</strong> to print out its version number and terminate.
+ </dd>
+ <p></p></dl>
+ <p>
+ </p>
+ <h2><a name="advanced_options">Advanced Options</a></h2>
+ <p>You better know what you're doing if you use these options. Improper use
+ of these options can produce drastically wrong results.</p>
+ <dl>
+ <dt><strong><a name="item__2d_2dconfig_2ddir_dirname"><strong>--config-dir</strong> <em>dirname</em></a></strong><br />
+ </dt>
+ <dd>
+ This option tells <strong>llvmc</strong> to read configuration data from the <em>directory</em>
+ named <em>dirname</em>. Data from such directories will be read in the order
+ specified on the command line after all other standard configuration files have
+ been read. This allows users or groups of users to conveniently create
+ their own configuration directories in addition to the standard ones to which
+ they may not have write access.
+ </dd>
+ <p></p></dl>
+ <p>
+ </p>
+ <h2><a name="unimplemented_options">Unimplemented Options</a></h2>
+ <p>The options below are not currently implemented in <strong>llvmc</strong> but will be
+ eventually. They are documented here as ``future design''.</p>
+ <dl>
+ <dt><strong><a name="item__2d_2dshow_2dconfig__5bsuffixes_2e_2e_2e_5d"><strong>--show-config</strong> <em>[suffixes...]</em></a></strong><br />
+ </dt>
+ <dd>
+ When this option is given, the only action taken by <strong>llvmc</strong> is to show its
+ final configuration state in the form of a configuration file. No compilation
+ tasks will be conducted when this option is given; processing will stop once
+ the configuration has been printed. The optional (comma separated) list of
+ suffixes controls what is printed. Without any suffixes, the configuration
+ for all languages is printed. With suffixes, only the languages pertaining
+ to those file suffixes will be printed. The configuration information is
+ printed after all command line options and configuration files have been
+ read and processed. This allows the user to verify that the correct
+ configuration data has been read by <strong>llvmc</strong>.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2d_2dconfig__3asection_3aname_3dvalue"><strong>--config</strong> :<em>section</em>:<em>name</em>=<em>value</em></a></strong><br />
+ </dt>
+ <dd>
+ This option instructs <strong>llvmc</strong> to accept <em>value</em> as the value for configuration
+ item <em>name</em> in the section named <em>section</em>. This is a quick way to override
+ a configuration item on the command line without resorting to changing the
+ configuration files.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2d_2dconfig_2donly_2dfrom_dirname"><strong>--config-only-from</strong> <em>dirname</em></a></strong><br />
+ </dt>
+ <dd>
+ This option tells <strong>llvmc</strong> to skip the normal processing of configuration
+ files and only configure from the contents of the <em>dirname</em> directory. Multiple
+ <strong>--config-only-from</strong> options may be given in which case the directories are
+ read in the order given on the command line.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2d_2demit_2draw_2dcode"><strong>--emit-raw-code</strong></a></strong><br />
+ </dt>
+ <dd>
+ No optimization is done whatsoever. The compilers invoked by <strong>llvmc</strong> with
+ this option given will be instructed to produce raw, unoptimized code. This
+ option is useful only to front end language developers and therefore does not
+ participate in the list of <strong>-O</strong> options. This is distinctly different from
+ the <strong>-O0</strong> option (a synonym for <strong>-O1</strong>) because those optimizations will
+ reduce code size to make compilation faster. With <strong>--emit-raw-code</strong>, only
+ the full raw code produced by the compiler will be generated.
+ </dd>
+ <p></p></dl>
+ <p>
+ </p>
+ <hr />
+ <h1><a name="exit_status">EXIT STATUS</a></h1>
+ <p>If <strong>llvmc</strong> succeeds, it will exit with 0. Otherwise, if an error
+ occurs, it will exit with a non-zero value and no compilation actions
+ will be taken. If one of the compilation tools returns a non-zero
+ status, pending actions will be discarded and <strong>llvmc</strong> will return the
+ same result code as the failing compilation tool.</p>
+ <p>
+ </p>
+ <hr />
+ <h1><a name="deficiencies">DEFICIENCIES</a></h1>
+ <p><strong>llvmc</strong> is considered an experimental LLVM tool because it has these
+ deficiencies:</p>
+ <dl>
+ <dt><strong><a name="item_insufficient_support_for_native_linking">Insufficient support for native linking</a></strong><br />
+ </dt>
+ <dd>
+ Because <strong>llvm-ld</strong> doesn't handle native linking, neither can <strong>llvmc</strong>
+ </dd>
+ <p></p>
+ <dt><strong><a name="item_poor_configuration_support">Poor configuration support</a></strong><br />
+ </dt>
+ <dd>
+ The support for configuring new languages, etc. is weak. There are many
+ command line configurations that cannot be achieved with the current
+ support. Furthermore the grammar is cumbersome for configuration files.
+ Please see <a href="http://llvm.org/PR686">http://llvm.org/PR686</a> for further details.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item_does_not_handle_target_specific_configurations">Does not handle target specific configurations</a></strong><br />
+ </dt>
+ <dd>
+ This is one of the major deficiencies, also addressed in
+ <a href="http://llvm.org/PR686">http://llvm.org/PR686</a>
+ </dd>
+ <p></p></dl>
+ <p>
+ </p>
+ <hr />
+ <h1><a name="see_also">SEE ALSO</a></h1>
+ <p><a href="././llvm-as.html">llvm-as</a>, <a href="././llvm-dis.html">llvm-dis</a>, <a href="././llc.html">llc</a>, <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>
Index: llvm-www/releases/2.1/docs/CommandGuide/html/llvmgcc.html
diff -c /dev/null llvm-www/releases/2.1/docs/CommandGuide/html/llvmgcc.html:1.1
*** /dev/null Thu Sep 27 00:43:39 2007
--- llvm-www/releases/2.1/docs/CommandGuide/html/llvmgcc.html Thu Sep 27 00:43:19 2007
***************
*** 0 ****
--- 1,131 ----
+ <!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>llvmgcc</title>
+ <link rel="stylesheet" href="manpage.css" type="text/css" />
+ <link rev="made" href="mailto:root at localhost" />
+ </head>
+
+ <body>
+
+ <p><a name="__index__"></a></p>
+ <!-- INDEX BEGIN -->
+ <!--
+
+ <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>
+ -->
+ <!-- INDEX END -->
+
+ <p>
+ </p>
+ <hr />
+ <h1><a name="name">NAME</a></h1>
+ <p>llvm-gcc - LLVM C front-end</p>
+ <p>
+ </p>
+ <hr />
+ <h1><a name="synopsis">SYNOPSIS</a></h1>
+ <p><strong>llvm-gcc</strong> [<em>options</em>] <em>filename</em></p>
+ <p>
+ </p>
+ <hr />
+ <h1><a name="description">DESCRIPTION</a></h1>
+ <p>The <strong>llvm-gcc</strong> command is the LLVM C front end. It is a modified
+ version of gcc that compiles C/ObjC programs into native objects, LLVM
+ bitcode or LLVM assembly language, depending upon the options.</p>
+ <p>By default, <strong>llvm-gcc</strong> compiles to native objects just like GCC does. If the
+ <strong>-emit-llvm</strong> option is given then it will generate LLVM bitcode files instead.
+ If <strong>-S</strong> (assembly) is also given, then it will generate LLVM assembly.</p>
+ <p>Being derived from the GNU Compiler Collection, <strong>llvm-gcc</strong> has many
+ of gcc's features and accepts most of gcc's options. It handles a
+ number of gcc's extensions to the C programming language.</p>
+ <p>
+ </p>
+ <hr />
+ <h1><a name="options">OPTIONS</a></h1>
+ <dl>
+ <dt><strong><a name="item__2d_2dhelp"><strong>--help</strong></a></strong><br />
+ </dt>
+ <dd>
+ Print a summary of command line options.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2ds"><strong>-S</strong></a></strong><br />
+ </dt>
+ <dd>
+ Do not generate an LLVM bitcode file. Rather, compile the source
+ file into an LLVM assembly language file.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2dc"><strong>-c</strong></a></strong><br />
+ </dt>
+ <dd>
+ Do not generate a linked executable. Rather, compile the source
+ file into an LLVM bitcode file. This bitcode file can then be
+ linked with other bitcode files later on to generate a full LLVM
+ executable.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2do_filename"><strong>-o</strong> <em>filename</em></a></strong><br />
+ </dt>
+ <dd>
+ Specify the output file to be <em>filename</em>.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2di_directory"><strong>-I</strong> <em>directory</em></a></strong><br />
+ </dt>
+ <dd>
+ Add a directory to the header file search path. This option can be
+ repeated.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2dl_directory"><strong>-L</strong> <em>directory</em></a></strong><br />
+ </dt>
+ <dd>
+ Add <em>directory</em> to the library search path. This option can be
+ repeated.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2dlname"><strong>-l</strong><em>name</em></a></strong><br />
+ </dt>
+ <dd>
+ Link in the library lib<em>name</em>.[bc | a | so]. This library should
+ be a bitcode library.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2demit_2dllvm"><strong>-emit-llvm</strong></a></strong><br />
+ </dt>
+ <dd>
+ Make the output be LLVM bitcode (or assembly) instead of native object (or
+ assembly).
+ </dd>
+ <p></p></dl>
+ <p>
+ </p>
+ <hr />
+ <h1><a name="exit_status">EXIT STATUS</a></h1>
+ <p>If <strong>llvm-gcc</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="././llvmgxx.html">llvm-g++</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>
Index: llvm-www/releases/2.1/docs/CommandGuide/html/llvmgxx.html
diff -c /dev/null llvm-www/releases/2.1/docs/CommandGuide/html/llvmgxx.html:1.1
*** /dev/null Thu Sep 27 00:43:39 2007
--- llvm-www/releases/2.1/docs/CommandGuide/html/llvmgxx.html Thu Sep 27 00:43:19 2007
***************
*** 0 ****
--- 1,131 ----
+ <!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>llvmgxx</title>
+ <link rel="stylesheet" href="manpage.css" type="text/css" />
+ <link rev="made" href="mailto:root at localhost" />
+ </head>
+
+ <body>
+
+ <p><a name="__index__"></a></p>
+ <!-- INDEX BEGIN -->
+ <!--
+
+ <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>
+ -->
+ <!-- INDEX END -->
+
+ <p>
+ </p>
+ <hr />
+ <h1><a name="name">NAME</a></h1>
+ <p>llvm-g++ - LLVM C++ front-end</p>
+ <p>
+ </p>
+ <hr />
+ <h1><a name="synopsis">SYNOPSIS</a></h1>
+ <p><strong>llvm-g++</strong> [<em>options</em>] <em>filename</em></p>
+ <p>
+ </p>
+ <hr />
+ <h1><a name="description">DESCRIPTION</a></h1>
+ <p>The <strong>llvm-g++</strong> command is the LLVM C++ front end. It is a modified
+ version of g++ that compiles C++/ObjC++ programs into native code,
+ LLVM bitcode or assembly language, depending upon the options.</p>
+ <p>By default, <strong>llvm-g++</strong> compiles to native objects just like GCC does. If the
+ <strong>-emit-llvm</strong> option is given then it will generate LLVM bitcode files instead.
+ If <strong>-S</strong> (assembly) is also given, then it will generate LLVM assembly.</p>
+ <p>Being derived from the GNU Compiler Collection, <strong>llvm-g++</strong> has many
+ of g++'s features and accepts most of g++'s options. It handles a
+ number of g++'s extensions to the C++ programming language.</p>
+ <p>
+ </p>
+ <hr />
+ <h1><a name="options">OPTIONS</a></h1>
+ <dl>
+ <dt><strong><a name="item__2d_2dhelp"><strong>--help</strong></a></strong><br />
+ </dt>
+ <dd>
+ Print a summary of command line options.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2ds"><strong>-S</strong></a></strong><br />
+ </dt>
+ <dd>
+ Do not generate an LLVM bitcode file. Rather, compile the source
+ file into an LLVM assembly language file.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2dc"><strong>-c</strong></a></strong><br />
+ </dt>
+ <dd>
+ Do not generate a linked executable. Rather, compile the source
+ file into an LLVM bitcode file. This bitcode file can then be
+ linked with other bitcode files later on to generate a full LLVM
+ executable.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2do_filename"><strong>-o</strong> <em>filename</em></a></strong><br />
+ </dt>
+ <dd>
+ Specify the output file to be <em>filename</em>.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2di_directory"><strong>-I</strong> <em>directory</em></a></strong><br />
+ </dt>
+ <dd>
+ Add a directory to the header file search path. This option can be
+ repeated.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2dl_directory"><strong>-L</strong> <em>directory</em></a></strong><br />
+ </dt>
+ <dd>
+ Add <em>directory</em> to the library search path. This option can be
+ repeated.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2dlname"><strong>-l</strong><em>name</em></a></strong><br />
+ </dt>
+ <dd>
+ Link in the library lib<em>name</em>.[bc | a | so]. This library should
+ be a bitcode library.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2demit_2dllvm"><strong>-emit-llvm</strong></a></strong><br />
+ </dt>
+ <dd>
+ Make the output be LLVM bitcode (or assembly) instead of native object (or
+ assembly).
+ </dd>
+ <p></p></dl>
+ <p>
+ </p>
+ <hr />
+ <h1><a name="exit_status">EXIT STATUS</a></h1>
+ <p>If <strong>llvm-g++</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="././llvmgcc.html">llvm-gcc</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>
Index: llvm-www/releases/2.1/docs/CommandGuide/html/manpage.css
diff -c /dev/null llvm-www/releases/2.1/docs/CommandGuide/html/manpage.css:1.1
*** /dev/null Thu Sep 27 00:43:39 2007
--- llvm-www/releases/2.1/docs/CommandGuide/html/manpage.css Thu Sep 27 00:43:19 2007
***************
*** 0 ****
--- 1,256 ----
+ /* Based on http://www.perldoc.com/css/perldoc.css */
+
+ @import url("../llvm.css");
+
+ body { font-family: Arial,Helvetica; }
+
+ blockquote { margin: 10pt; }
+
+ h1, a { color: #336699; }
+
+
+ /*** Top menu style ****/
+ .mmenuon {
+ font-family: Arial,Helvetica; font-weight: bold; text-decoration: none;
+ color: #ff6600; font-size: 10pt;
+ }
+ .mmenuoff {
+ font-family: Arial,Helvetica; font-weight: bold; text-decoration: none;
+ color: #ffffff; font-size: 10pt;
+ }
+ .cpyright {
+ font-family: Arial,Helvetica; font-weight: bold; text-decoration: none;
+ color: #ffffff; font-size: xx-small;
+ }
+ .cpyrightText {
+ font-family: Arial,Helvetica; font-weight: bold; text-decoration: none;
+ color: #ffffff; font-size: xx-small;
+ }
+ .sections {
+ font-family: Arial,Helvetica; font-weight: bold; text-decoration: none;
+ color: #336699; font-size: 11pt;
+ }
+ .dsections {
+ font-family: Arial,Helvetica; font-weight: bold; text-decoration: none;
+ color: #336699; font-size: 12pt;
+ }
+ .slink {
+ font-family: Arial,Helvetica; font-weight: normal; text-decoration: none;
+ color: #000000; font-size: 9pt;
+ }
+
+ .slink2 { font-family: Arial,Helvetica; text-decoration: none; color: #336699; }
+
+ .maintitle {
+ font-family: Arial,Helvetica; font-weight: bold; text-decoration: none;
+ color: #336699; font-size: 18pt;
+ }
+ .dblArrow {
+ font-family: Arial,Helvetica; font-weight: bold; text-decoration: none;
+ color: #336699; font-size: small;
+ }
+ .menuSec {
+ font-family: Arial,Helvetica; font-weight: bold; text-decoration: none;
+ color: #336699; font-size: small;
+ }
+
+ .newstext {
+ font-family: Arial,Helvetica; font-size: small;
+ }
+
+ .linkmenu {
+ font-family: Arial,Helvetica; color: #000000; font-weight: bold;
+ text-decoration: none;
+ }
+
+ P {
+ font-family: Arial,Helvetica;
+ }
+
+ PRE {
+ font-size: 10pt;
+ }
+ .quote {
+ font-family: Times; text-decoration: none;
+ color: #000000; font-size: 9pt; font-style: italic;
+ }
+ .smstd { font-family: Arial,Helvetica; color: #000000; font-size: x-small; }
+ .std { font-family: Arial,Helvetica; color: #000000; }
+ .meerkatTitle {
+ font-family: sans-serif; font-size: x-small; color: black; }
+
+ .meerkatDescription { font-family: sans-serif; font-size: 10pt; color: black }
+ .meerkatCategory {
+ font-family: sans-serif; font-size: 9pt; font-weight: bold; font-style: italic;
+ color: brown; }
+ .meerkatChannel {
+ font-family: sans-serif; font-size: 9pt; font-style: italic; color: brown; }
+ .meerkatDate { font-family: sans-serif; font-size: xx-small; color: #336699; }
+
+ .tocTitle {
+ font-family: Arial,Helvetica; font-weight: bold; text-decoration: none;
+ color: #333333; font-size: 10pt;
+ }
+
+ .toc-item {
+ font-family: Arial,Helvetica; font-weight: bold;
+ color: #336699; font-size: 10pt; text-decoration: underline;
+ }
+
+ .perlVersion {
+ font-family: Arial,Helvetica; font-weight: bold;
+ color: #336699; font-size: 10pt; text-decoration: none;
+ }
+
+ .podTitle {
+ font-family: Arial,Helvetica; font-weight: bold; text-decoration: none;
+ color: #000000;
+ }
+
+ .docTitle {
+ font-family: Arial,Helvetica; font-weight: bold; text-decoration: none;
+ color: #000000; font-size: 10pt;
+ }
+ .dotDot {
+ font-family: Arial,Helvetica; font-weight: bold;
+ color: #000000; font-size: 9pt;
+ }
+
+ .docSec {
+ font-family: Arial,Helvetica; font-weight: normal;
+ color: #333333; font-size: 9pt;
+ }
+ .docVersion {
+ font-family: Arial,Helvetica; font-weight: bold; text-decoration: none;
+ color: #336699; font-size: 10pt;
+ }
+
+ .docSecs-on {
+ font-family: Arial,Helvetica; font-weight: normal; text-decoration: none;
+ color: #ff0000; font-size: 10pt;
+ }
+ .docSecs-off {
+ font-family: Arial,Helvetica; font-weight: normal; text-decoration: none;
+ color: #333333; font-size: 10pt;
+ }
+
+ h2 {
+ font-family: Arial,Helvetica; font-weight: bold; text-decoration: none;
+ color: #336699; font-size: medium;
+ }
+ h1 {
+ font-family: Verdana,Arial,Helvetica; font-weight: bold; text-decoration: none;
+ color: #336699; font-size: large;
+ }
+
+ DL {
+ font-family: Arial,Helvetica; font-weight: normal; text-decoration: none;
+ color: #333333; font-size: 10pt;
+ }
+
+ UL > LI > A {
+ font-family: Arial,Helvetica; font-weight: bold;
+ color: #336699; font-size: 10pt;
+ }
+
+ .moduleInfo {
+ font-family: Arial,Helvetica; font-weight: bold; text-decoration: none;
+ color: #333333; font-size: 11pt;
+ }
+
+ .moduleInfoSec {
+ font-family: Arial,Helvetica; font-weight: bold; text-decoration: none;
+ color: #336699; font-size: 10pt;
+ }
+
+ .moduleInfoVal {
+ font-family: Arial,Helvetica; font-weight: normal; text-decoration: underline;
+ color: #000000; font-size: 10pt;
+ }
+
+ .cpanNavTitle {
+ font-family: Arial,Helvetica; font-weight: bold;
+ color: #ffffff; font-size: 10pt;
+ }
+ .cpanNavLetter {
+ font-family: Arial,Helvetica; font-weight: bold; text-decoration: none;
+ color: #333333; font-size: 9pt;
+ }
+ .cpanCat {
+ font-family: Arial,Helvetica; font-weight: bold; text-decoration: none;
+ color: #336699; font-size: 9pt;
+ }
+
+ .bttndrkblue-bkgd-top {
+ background-color: #225688;
+ background-image: url(/global/mvc_objects/images/bttndrkblue_bgtop.gif);
+ }
+ .bttndrkblue-bkgd-left {
+ background-color: #225688;
+ background-image: url(/global/mvc_objects/images/bttndrkblue_bgleft.gif);
+ }
+ .bttndrkblue-bkgd {
+ padding-top: 0px;
+ padding-bottom: 0px;
+ margin-bottom: 0px;
+ margin-top: 0px;
+ background-repeat: no-repeat;
+ background-color: #225688;
+ background-image: url(/global/mvc_objects/images/bttndrkblue_bgmiddle.gif);
+ vertical-align: top;
+ }
+ .bttndrkblue-bkgd-right {
+ background-color: #225688;
+ background-image: url(/global/mvc_objects/images/bttndrkblue_bgright.gif);
+ }
+ .bttndrkblue-bkgd-bottom {
+ background-color: #225688;
+ background-image: url(/global/mvc_objects/images/bttndrkblue_bgbottom.gif);
+ }
+ .bttndrkblue-text a {
+ color: #ffffff;
+ text-decoration: none;
+ }
+ a.bttndrkblue-text:hover {
+ color: #ffDD3C;
+ text-decoration: none;
+ }
+ .bg-ltblue {
+ background-color: #f0f5fa;
+ }
+
+ .border-left-b {
+ background: #f0f5fa url(/i/corner-leftline.gif) repeat-y;
+ }
+
+ .border-right-b {
+ background: #f0f5fa url(/i/corner-rightline.gif) repeat-y;
+ }
+
+ .border-top-b {
+ background: #f0f5fa url(/i/corner-topline.gif) repeat-x;
+ }
+
+ .border-bottom-b {
+ background: #f0f5fa url(/i/corner-botline.gif) repeat-x;
+ }
+
+ .border-right-w {
+ background: #ffffff url(/i/corner-rightline.gif) repeat-y;
+ }
+
+ .border-top-w {
+ background: #ffffff url(/i/corner-topline.gif) repeat-x;
+ }
+
+ .border-bottom-w {
+ background: #ffffff url(/i/corner-botline.gif) repeat-x;
+ }
+
+ .bg-white {
+ background-color: #ffffff;
+ }
+
+ .border-left-w {
+ background: #ffffff url(/i/corner-leftline.gif) repeat-y;
+ }
Index: llvm-www/releases/2.1/docs/CommandGuide/html/opt.html
diff -c /dev/null llvm-www/releases/2.1/docs/CommandGuide/html/opt.html:1.1
*** /dev/null Thu Sep 27 00:43:39 2007
--- llvm-www/releases/2.1/docs/CommandGuide/html/opt.html Thu Sep 27 00:43:19 2007
***************
*** 0 ****
--- 1,199 ----
+ <!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" />
+ <link rev="made" href="mailto:root at localhost" />
+ </head>
+
+ <body>
+
+ <p><a name="__index__"></a></p>
+ <!-- INDEX BEGIN -->
+ <!--
+
+ <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>
+ -->
+ <!-- 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
+ bitcode as input, runs the specified optimizations or analyses on it, and then
+ outputs the optimized LLVM bitcode 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 LLVM
+ bitcode. 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
+ bitcode 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. The input must be an LLVM bitcode file.</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="item__2df"><strong>-f</strong></a></strong><br />
+ </dt>
+ <dd>
+ Force overwrite. Normally, <strong>opt</strong> will refuse to overwrite an
+ output file that already exists. With this option, <strong>opt</strong> will
+ overwrite the output file and replace it with new bitcode.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2dhelp"><strong>-help</strong></a></strong><br />
+ </dt>
+ <dd>
+ Print a summary of command line options.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2do_filename"><strong>-o</strong> <em>filename</em></a></strong><br />
+ </dt>
+ <dd>
+ Specify the output filename.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2d_7bpassname_7d"><strong>-{passname}</strong></a></strong><br />
+ </dt>
+ <dd>
+ <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).
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2dstd_2dcompile_2dopts"><strong>-std-compile-opts</strong></a></strong><br />
+ </dt>
+ <dd>
+ 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:
+ </dd>
+ <dd>
+ <pre>
+ llvm-as < /dev/null | opt -std-compile-opts -disable-output -debug-pass=Arguments</pre>
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2ddisable_2dinlining"><strong>-disable-inlining</strong></a></strong><br />
+ </dt>
+ <dd>
+ This option is only meaningful when <strong>-std-compile-opts</strong> is given. It simply
+ removes the inlining pass from the standard list.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2ddisable_2dopt"><strong>-disable-opt</strong></a></strong><br />
+ </dt>
+ <dd>
+ 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>.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2dstrip_2ddebug"><strong>-strip-debug</strong></a></strong><br />
+ </dt>
+ <dd>
+ 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.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2dverify_2deach"><strong>-verify-each</strong></a></strong><br />
+ </dt>
+ <dd>
+ 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.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2dprofile_2dinfo_2dfile_filename"><strong>-profile-info-file</strong> <em>filename</em></a></strong><br />
+ </dt>
+ <dd>
+ Specify the name of the file loaded by the -profile-loader option.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2dstats"><strong>-stats</strong></a></strong><br />
+ </dt>
+ <dd>
+ Print statistics.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2dtime_2dpasses"><strong>-time-passes</strong></a></strong><br />
+ </dt>
+ <dd>
+ Record the amount of time needed for each pass and print it to standard
+ error.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2ddebug"><strong>-debug</strong></a></strong><br />
+ </dt>
+ <dd>
+ 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.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2dload_3dplugin"><strong>-load</strong>=<em>plugin</em></a></strong><br />
+ </dt>
+ <dd>
+ 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:
+ </dd>
+ <dd>
+ <pre>
+ opt -load=plugin.so -help</pre>
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2dp"><strong>-p</strong></a></strong><br />
+ </dt>
+ <dd>
+ Print module after each transformation.
+ </dd>
+ <p></p></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>
Index: llvm-www/releases/2.1/docs/CommandGuide/html/stkrc.html
diff -c /dev/null llvm-www/releases/2.1/docs/CommandGuide/html/stkrc.html:1.1
*** /dev/null Thu Sep 27 00:43:39 2007
--- llvm-www/releases/2.1/docs/CommandGuide/html/stkrc.html Thu Sep 27 00:43:19 2007
***************
*** 0 ****
--- 1,133 ----
+ <!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>stkrc</title>
+ <link rel="stylesheet" href="manpage.css" type="text/css" />
+ <link rev="made" href="mailto:root at localhost" />
+ </head>
+
+ <body>
+
+ <p><a name="__index__"></a></p>
+ <!-- INDEX BEGIN -->
+ <!--
+
+ <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>
+ -->
+ <!-- INDEX END -->
+
+ <p>
+ </p>
+ <hr />
+ <h1><a name="name">NAME</a></h1>
+ <p>stkrc - Stacker Compiler</p>
+ <p>
+ </p>
+ <hr />
+ <h1><a name="synopsis">SYNOPSIS</a></h1>
+ <p><strong>stkrc</strong> [<em>options</em>] [<em>filename</em>]</p>
+ <p>
+ </p>
+ <hr />
+ <h1><a name="description">DESCRIPTION</a></h1>
+ <p>The <strong>stkrc</strong> command is the compiler for the Stacker language. Stacker is a
+ simple stack based, Forth-like language that was written as a demonstration
+ language for LLVM. For details on the language, please see
+ <a href="http://llvm.org/docs/Stacker.html">http://llvm.org/docs/Stacker.html</a> . The <strong>stkrc</strong> compiler is fairly
+ minimal. It compiles to bitcode only and doesn't perform any optimizations.
+ The output of stkrc (a bitcode file) can be piped through other LLVM tools
+ for optimization and linking.</p>
+ <p>If <em>filename</em> is omitted or is <code>-</code>, then <strong>stkrc</strong> reads its input
+ from standard input. This is useful for combining the tool into a pipeline.</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></li>
+ If the input is standard input, then the output is standard output.
+ <p></p>
+ <li></li>
+ If the input is a file that ends with <code>.st</code>, then the output file is of
+ the same name, except that the suffix is changed to <code>.bc</code>.
+ <p></p>
+ <li></li>
+ If the input is a file that does not end with the <code>.st</code> suffix, then the
+ output file has the same name as the input file, except that the <code>.bc</code>
+ suffix is appended.
+ <p></p></ul>
+ <p>
+ </p>
+ <hr />
+ <h1><a name="options">OPTIONS</a></h1>
+ <dl>
+ <dt><strong><a name="item__2do_filename"><strong>-o</strong> <em>filename</em></a></strong><br />
+ </dt>
+ <dd>
+ Specify the output file name. If <em>filename</em> is <code>-</code>, then <strong>llvm-as</strong>
+ sends its output to standard output.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2dstats"><strong>-stats</strong></a></strong><br />
+ </dt>
+ <dd>
+ Print statistics acquired during compilation.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2dtime_2dpasses"><strong>-time-passes</strong></a></strong><br />
+ </dt>
+ <dd>
+ Record the amount of time needed for each pass and print it to standard
+ error.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2df"><strong>-f</strong></a></strong><br />
+ </dt>
+ <dd>
+ Force the output to be written. Normally, <strong>stkrc</strong> won't overwrite an existing
+ bitcode file. This option overrides that behavior.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2ds_stacksize"><strong>-s</strong> <em>stacksize</em></a></strong><br />
+ </dt>
+ <dd>
+ Specify the stack size for the program. The default stack size, 1024, should be
+ sufficient for most programs. For very large programs, especially those that
+ recurse a lot, you might want to provide a larger value. Each unit of this
+ value consumes 8 bytes of memory.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2dhelp"><strong>-help</strong></a></strong><br />
+ </dt>
+ <dd>
+ Print a summary of command line options.
+ </dd>
+ <p></p></dl>
+ <p>
+ </p>
+ <hr />
+ <h1><a name="exit_status">EXIT STATUS</a></h1>
+ <p>If <strong>stkrc</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="see_also">SEE ALSO</a></h1>
+ <p><a href="././llvm-as.html">the llvm-as manpage</a>, <a href="http://llvm.org/docs/Stacker.html">http://llvm.org/docs/Stacker.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>
Index: llvm-www/releases/2.1/docs/CommandGuide/html/tblgen.html
diff -c /dev/null llvm-www/releases/2.1/docs/CommandGuide/html/tblgen.html:1.1
*** /dev/null Thu Sep 27 00:43:39 2007
--- llvm-www/releases/2.1/docs/CommandGuide/html/tblgen.html Thu Sep 27 00:43:19 2007
***************
*** 0 ****
--- 1,179 ----
+ <!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" />
+ <link rev="made" href="mailto:root at localhost" />
+ </head>
+
+ <body>
+
+ <p><a name="__index__"></a></p>
+ <!-- INDEX BEGIN -->
+ <!--
+
+ <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>
+ -->
+ <!-- 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>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="item__2d_2dhelp"><strong>--help</strong></a></strong><br />
+ </dt>
+ <dd>
+ Print a summary of command line options.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2do_filename"><strong>-o</strong> <em>filename</em></a></strong><br />
+ </dt>
+ <dd>
+ Specify the output file name. If <em>filename</em> is <code>-</code>, then <strong>tblgen</strong>
+ sends its output to standard output.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2di_directory"><strong>-I</strong> <em>directory</em></a></strong><br />
+ </dt>
+ <dd>
+ Specify where to find other target description files for inclusion. The
+ <em>directory</em> value should be a full or partial path to a directory that contains
+ target description files.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2dasmwriternum_n"><strong>-asmwriternum</strong> <em>N</em></a></strong><br />
+ </dt>
+ <dd>
+ Make -gen-asm-writer emit assembly writer number <em>N</em>.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2dclass_class_name"><strong>-class</strong> <em>class Name</em></a></strong><br />
+ </dt>
+ <dd>
+ Print the enumeration list for this class.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2dprint_2drecords"><strong>-print-records</strong></a></strong><br />
+ </dt>
+ <dd>
+ Print all records to standard output (default).
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2dprint_2denums"><strong>-print-enums</strong></a></strong><br />
+ </dt>
+ <dd>
+ Print enumeration values for a class
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2dgen_2demitter"><strong>-gen-emitter</strong></a></strong><br />
+ </dt>
+ <dd>
+ Generate machine code emitter.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2dgen_2dregister_2denums"><strong>-gen-register-enums</strong></a></strong><br />
+ </dt>
+ <dd>
+ Generate the enumeration values for all registers.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2dgen_2dregister_2ddesc"><strong>-gen-register-desc</strong></a></strong><br />
+ </dt>
+ <dd>
+ Generate a register info description for each register.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2dgen_2dregister_2ddesc_2dheader"><strong>-gen-register-desc-header</strong></a></strong><br />
+ </dt>
+ <dd>
+ Generate a register info description header for each register.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2dgen_2dinstr_2denums"><strong>-gen-instr-enums</strong></a></strong><br />
+ </dt>
+ <dd>
+ Generate enumeration values for instructions.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2dgen_2dinstr_2ddesc"><strong>-gen-instr-desc</strong></a></strong><br />
+ </dt>
+ <dd>
+ Generate instruction descriptions.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2dgen_2dasm_2dwriter"><strong>-gen-asm-writer</strong></a></strong><br />
+ </dt>
+ <dd>
+ Generate the assembly writer.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2dgen_2ddag_2disel"><strong>-gen-dag-isel</strong></a></strong><br />
+ </dt>
+ <dd>
+ Generate a DAG (Directed Acycle Graph) instruction selector.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2dgen_2dsubtarget"><strong>-gen-subtarget</strong></a></strong><br />
+ </dt>
+ <dd>
+ Generate subtarget enumerations.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2dgen_2dintrinsic"><strong>-gen-intrinsic</strong></a></strong><br />
+ </dt>
+ <dd>
+ Generate intrinsic information.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2dversion"><strong>-version</strong></a></strong><br />
+ </dt>
+ <dd>
+ Show the version number of this program.
+ </dd>
+ <p></p></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