[llvm-commits] CVS: llvm-www/releases/1.3/docs/CommandGuide/html/analyze.html bugpoint.html extract.html gccas.html gccld.html llc.html lli.html llvm-as.html llvm-bcanalyzer.html llvm-db.html llvm-dis.html llvm-link.html llvm-nm.html llvm-prof.html llvmgcc.html llvmgxx.html manpage.css opt.html stkrc.html
John Criswell
criswell at cs.uiuc.edu
Fri Aug 13 15:11:35 PDT 2004
Changes in directory llvm-www/releases/1.3/docs/CommandGuide/html:
analyze.html added (r1.1)
bugpoint.html added (r1.1)
extract.html added (r1.1)
gccas.html added (r1.1)
gccld.html added (r1.1)
llc.html added (r1.1)
lli.html added (r1.1)
llvm-as.html added (r1.1)
llvm-bcanalyzer.html added (r1.1)
llvm-db.html added (r1.1)
llvm-dis.html added (r1.1)
llvm-link.html added (r1.1)
llvm-nm.html added (r1.1)
llvm-prof.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)
---
Log message:
Adding in Command Guide.
---
Diffs of the changes: (+2861 -0)
Index: llvm-www/releases/1.3/docs/CommandGuide/html/analyze.html
diff -c /dev/null llvm-www/releases/1.3/docs/CommandGuide/html/analyze.html:1.1
*** /dev/null Fri Aug 13 17:11:34 2004
--- llvm-www/releases/1.3/docs/CommandGuide/html/analyze.html Fri Aug 13 17:11:24 2004
***************
*** 0 ****
--- 1,120 ----
+ <!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>analyze - LLVM program analyzer</title>
+ <link rel="stylesheet" href="manpage.css" type="text/css" />
+ <link rev="made" href="mailto:criswell at choi.cs.uiuc.edu" />
+ </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>analyze - LLVM program analyzer</p>
+ <p>
+ </p>
+ <hr />
+ <h1><a name="synopsis">SYNOPSIS</a></h1>
+ <p><strong>analyze</strong> [<em>options</em>] [<em>filename</em>]</p>
+ <p>
+ </p>
+ <hr />
+ <h1><a name="description">DESCRIPTION</a></h1>
+ <p>The <strong>analyze</strong> command performs various analysis of LLVM assembly
+ code or bytecode. 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>If filename is omitted or is <em>-</em>, <strong>analyze</strong> reads its input from
+ standard input. It first attempts to interpret its input as LLVM
+ bytecode. If it encounters an error, it then attempts to parse the
+ input as LLVM assembly language.</p>
+ <p>
+ </p>
+ <hr />
+ <h1><a name="options">OPTIONS</a></h1>
+ <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__2dq"><strong>-q</strong></a></strong><br />
+ </dt>
+ <dd>
+ Quiet mode. With this option, analysis pass names are not printed.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2dload_plugin"><strong>-load</strong> <em>plugin</em></a></strong><br />
+ </dt>
+ <dd>
+ Load the specified dynamic object with name <em>plugin</em>. This file
+ should contain additional analysis passes that register themselves
+ with the <strong>analyze</strong> program after being loaded.
+ </dd>
+ <dd>
+ <p>After being loaded, additional command line options are made
+ available for running the passes made available by <em>plugin</em>. Use
+ <strong>analyze -load</strong> <em>plugin</em> <strong>-help</strong> to see the new list of available
+ analysis passes.</p>
+ </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></dl>
+ <p>
+ </p>
+ <hr />
+ <h1><a name="exit_status">EXIT STATUS</a></h1>
+ <p>If <strong>analyze</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="././opt.html">opt</a></p>
+ <p>
+ </p>
+ <hr />
+ <h1><a name="authors">AUTHORS</a></h1>
+ <p>Maintained by the LLVM Team (<a href="http://llvm.cs.uiuc.edu">http://llvm.cs.uiuc.edu</a>).</p>
+
+ </body>
+
+ </html>
Index: llvm-www/releases/1.3/docs/CommandGuide/html/bugpoint.html
diff -c /dev/null llvm-www/releases/1.3/docs/CommandGuide/html/bugpoint.html:1.1
*** /dev/null Fri Aug 13 17:11:34 2004
--- llvm-www/releases/1.3/docs/CommandGuide/html/bugpoint.html Fri Aug 13 17:11:24 2004
***************
*** 0 ****
--- 1,309 ----
+ <!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 - automatic test case reduction tool</title>
+ <link rel="stylesheet" href="manpage.css" type="text/css" />
+ <link rev="made" href="mailto:criswell at choi.cs.uiuc.edu" />
+ </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="#design_philosophy">Design Philosophy</a></li>
+ <li><a href="#automatic_debugger_selection">Automatic Debugger Selection</a></li>
+ <li><a href="#crash_debugger">Crash debugger</a></li>
+ <li><a href="#code_generator_debugger">Code generator debugger</a></li>
+ <li><a href="#miscompilation_debugger">Miscompilation debugger</a></li>
+ <li><a href="#advice_for_using_bugpoint">Advice for using bugpoint</a></li>
+ </ul>
+
+ <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 example, if <strong>gccas</strong> crashes while optimizing a file, it will identify the
+ optimization (or combination of optimizations) that causes the crash, and reduce
+ the file down to a small example which triggers the crash.</p>
+ <p>
+ </p>
+ <h2><a name="design_philosophy">Design Philosophy</a></h2>
+ <p><strong>bugpoint</strong> is designed to be a useful tool without requiring any hooks into the
+ LLVM infrastructure at all. It works with any and all LLVM passes and code
+ generators, and does not need to ``know'' how they work. Because of this, it may
+ appear to do stupid things or miss obvious simplifications. <strong>bugpoint</strong> is also
+ designed to trade off programmer time for computer time in the
+ compiler-debugging process; consequently, it may take a long period of
+ (unattended) time to reduce a test case, but we feel it is still worth it. Note
+ that <strong>bugpoint</strong> is generally very quick unless debugging a miscompilation where
+ each test of the program (which requires executing it) takes a long time.</p>
+ <p>
+ </p>
+ <h2><a name="automatic_debugger_selection">Automatic Debugger Selection</a></h2>
+ <p><strong>bugpoint</strong> reads each <em>.bc</em> or <em>.ll</em> file specified on the command line and
+ links them together into a single module, called the test program. If any LLVM
+ passes are specified on the command line, it runs these passes on the test
+ program. If any of the passes crash, or if they produce malformed output (which
+ causes the verifier to abort), <strong>bugpoint</strong> starts the crash debugger.</p>
+ <p>Otherwise, if the <strong>-output</strong> option was not specified, <strong>bugpoint</strong> runs the test
+ program with the C backend (which is assumed to generate good code) to generate
+ a reference output. Once <strong>bugpoint</strong> has a reference output for the test
+ program, it tries executing it with the selected code generator. If the
+ selected code generator crashes, <strong>bugpoint</strong> starts the <a href="#crash_debugger">Crash debugger</a> on
+ the code generator. Otherwise, if the resulting output differs from the
+ reference output, it assumes the difference resulted from a code generator
+ failure, and starts the <a href="#code_generator_debugger">Code generator debugger</a>.</p>
+ <p>Finally, if the output of the selected code generator matches the reference
+ output, <strong>bugpoint</strong> runs the test program after all of the LLVM passes have been
+ applied to it. If its output differs from the reference output, it assumes the
+ difference resulted from a failure in one of the LLVM passes, and enters the
+ miscompilation debugger. Otherwise, there is no problem <strong>bugpoint</strong> can debug.</p>
+ <p>
+ </p>
+ <h2><a name="crash_debugger">Crash debugger</a></h2>
+ <p>If an optimizer or code generator crashes, <strong>bugpoint</strong> will try as hard as it
+ can to reduce the list of passes (for optimizer crashes) and the size of the
+ test program. First, <strong>bugpoint</strong> figures out which combination of optimizer
+ passes triggers the bug. This is useful when debugging a problem exposed by
+ <strong>gccas</strong>, for example, because it runs over 38 passes.</p>
+ <p>Next, <strong>bugpoint</strong> tries removing functions from the test program, to reduce its
+ size. Usually it is able to reduce a test program to a single function, when
+ debugging intraprocedural optimizations. Once the number of functions has been
+ reduced, it attempts to delete various edges in the control flow graph, to
+ reduce the size of the function as much as possible. Finally, <strong>bugpoint</strong>
+ deletes any individual LLVM instructions whose absence does not eliminate the
+ failure. At the end, <strong>bugpoint</strong> should tell you what passes crash, give you a
+ bytecode file, and give you instructions on how to reproduce the failure with
+ <strong>opt</strong>, <strong>analyze</strong>, or <strong>llc</strong>.</p>
+ <p>
+ </p>
+ <h2><a name="code_generator_debugger">Code generator debugger</a></h2>
+ <p>The code generator debugger attempts to narrow down the amount of code that is
+ being miscompiled by the selected code generator. To do this, it takes the test
+ program and partitions it into two pieces: one piece which it compiles with the
+ C backend (into a shared object), and one piece which it runs with either the
+ JIT or the static compiler (<strong>llc</strong>). It uses several techniques to reduce the
+ amount of code pushed through the LLVM code generator, to reduce the potential
+ scope of the problem. After it is finished, it emits two bytecode files (called
+ ``test'' [to be compiled with the code generator] and ``safe'' [to be compiled with
+ the C backend], respectively), and instructions for reproducing the problem.
+ The code generator debugger assumes that the C backend produces good code.</p>
+ <p>
+ </p>
+ <h2><a name="miscompilation_debugger">Miscompilation debugger</a></h2>
+ <p>The miscompilation debugger works similarly to the code generator debugger. It
+ works by splitting the test program into two pieces, running the optimizations
+ specified on one piece, linking the two pieces back together, and then executing
+ the result. It attempts to narrow down the list of passes to the one (or few)
+ which are causing the miscompilation, then reduce the portion of the test
+ program which is being miscompiled. The miscompilation debugger assumes that
+ the selected code generator is working properly.</p>
+ <p>
+ </p>
+ <h2><a name="advice_for_using_bugpoint">Advice for using bugpoint</a></h2>
+ <p><strong>bugpoint</strong> can be a remarkably useful tool, but it sometimes works in
+ non-obvious ways. Here are some hints and tips:</p>
+ <ul>
+ <li></li>
+ In the code generator and miscompilation debuggers, <strong>bugpoint</strong> only
+ works with programs that have deterministic output. Thus, if the program
+ outputs <code>argv[0]</code>, the date, time, or any other ``random'' data, <strong>bugpoint</strong> may
+ misinterpret differences in these data, when output, as the result of a
+ miscompilation. Programs should be temporarily modified to disable outputs that
+ are likely to vary from run to run.
+ <p></p>
+ <li></li>
+ In the code generator and miscompilation debuggers, debugging will go faster if
+ you manually modify the program or its inputs to reduce the runtime, but still
+ exhibit the problem.
+ <p></p>
+ <li></li>
+ <strong>bugpoint</strong> is extremely useful when working on a new optimization: it helps
+ track down regressions quickly. To avoid having to relink <strong>bugpoint</strong> every
+ time you change your optimization, make <strong>bugpoint</strong> dynamically load
+ your optimization by using the <strong>-load</strong> option.
+ <p></p>
+ <li></li>
+ <strong>bugpoint</strong> can generate a lot of output and run for a long period of time. It
+ is often useful to capture the output of the program to file. For example, in
+ the C shell, you can type:
+ <pre>
+ bugpoint ... |& tee bugpoint.log</pre>
+ <p>to get a copy of <strong>bugpoint</strong>'s output in the file <em>bugpoint.log</em>, as well as on
+ your terminal.</p>
+ <p></p>
+ <li></li>
+ <strong>bugpoint</strong> cannot debug problems with the LLVM linker. If <strong>bugpoint</strong> crashes
+ before you see its <code>All input ok</code> message, you might try running <code>llvm-link
+ -v</code> on the same set of input files. If that also crashes, you may be
+ experiencing a linker bug.
+ <p></p>
+ <li></li>
+ If your program is supposed to crash, <strong>bugpoint</strong> will be confused. One way to
+ deal with this is to cause <strong>bugpoint</strong> to ignore the exit code from your
+ program, by giving it the <strong>-check-exit-code=false</strong> option.
+ <p></p></ul>
+ <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_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_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>, <a href="././analyze.html">analyze</a></p>
+ <p>
+ </p>
+ <hr />
+ <h1><a name="author">AUTHOR</a></h1>
+ <p>Maintained by the LLVM Team (<a href="http://llvm.cs.uiuc.edu">http://llvm.cs.uiuc.edu</a>).</p>
+
+ </body>
+
+ </html>
Index: llvm-www/releases/1.3/docs/CommandGuide/html/extract.html
diff -c /dev/null llvm-www/releases/1.3/docs/CommandGuide/html/extract.html:1.1
*** /dev/null Fri Aug 13 17:11:34 2004
--- llvm-www/releases/1.3/docs/CommandGuide/html/extract.html Fri Aug 13 17:11:24 2004
***************
*** 0 ****
--- 1,115 ----
+ <!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>extract - extract a function from an LLVM module</title>
+ <link rel="stylesheet" href="manpage.css" type="text/css" />
+ <link rev="made" href="mailto:criswell at choi.cs.uiuc.edu" />
+ </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>extract - extract a function from an LLVM module</p>
+ <p>
+ </p>
+ <hr />
+ <h1><a name="synopsis">SYNOPSIS</a></h1>
+ <p><strong>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>extract</strong> command takes the name of a function and extracts it from
+ the specified LLVM bytecode 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 bytecode of the specified function,
+ <strong>extract</strong> will also remove unreachable global variables, prototypes, and
+ unused types.</p>
+ <p>The <strong>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>extract</strong> will refuse to overwrite an
+ output file that already exists. With this option, <strong>extract</strong>
+ will overwrite the output file and replace it with new bytecode.
+ </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 bytecode.
+ </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>extract</strong> sends its output to standard output.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2d_2dstats"><strong>--stats</strong></a></strong><br />
+ </dt>
+ <dd>
+ Print statistics.
+ </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>If <strong>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.cs.uiuc.edu">http://llvm.cs.uiuc.edu</a>).</p>
+
+ </body>
+
+ </html>
Index: llvm-www/releases/1.3/docs/CommandGuide/html/gccas.html
diff -c /dev/null llvm-www/releases/1.3/docs/CommandGuide/html/gccas.html:1.1
*** /dev/null Fri Aug 13 17:11:34 2004
--- llvm-www/releases/1.3/docs/CommandGuide/html/gccas.html Fri Aug 13 17:11:24 2004
***************
*** 0 ****
--- 1,122 ----
+ <!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>gccas - optimizing LLVM assembler</title>
+ <link rel="stylesheet" href="manpage.css" type="text/css" />
+ <link rev="made" href="mailto:criswell at choi.cs.uiuc.edu" />
+ </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>gccas - optimizing LLVM assembler</p>
+ <p>
+ </p>
+ <hr />
+ <h1><a name="synopsis">SYNOPSIS</a></h1>
+ <p><strong>gccas</strong> [<em>options</em>] <em>filename</em></p>
+ <p>
+ </p>
+ <hr />
+ <h1><a name="description">DESCRIPTION</a></h1>
+ <p>The <strong>gccas</strong> utility takes an LLVM assembly file generated by the
+ <a href="././llvmgcc.html">llvmgcc</a> or <a href="././llvmgxx.html">llvmg++</a> front-ends and converts
+ it into an LLVM bytecode file. It is primarily used by the GCC
+ front end, and as such, attempts to mimic the interface provided
+ by the default system assembler so that it can act as a ``drop-in''
+ replacement.</p>
+ <p><strong>gccas</strong> performs a number of optimizations on the input program,
+ including but not limited to: promotion of stack values to SSA
+ registers; elimination of dead globals, function arguments, code,
+ and types; tail-call elimination; loop-invariant code motion; global
+ common-subexpression elimination; and sparse conditional constant
+ propagation.</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 name of the output file which will hold the assembled bytecode.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2d_2ddisable_2dinlining"><strong>--disable-inlining</strong></a></strong><br />
+ </dt>
+ <dd>
+ Disable the inlining pass. By default, it is enabled.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2d_2ddisable_2dopt"><strong>--disable-opt</strong></a></strong><br />
+ </dt>
+ <dd>
+ Disable all assembler-time optimization passes.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2d_2dstats"><strong>--stats</strong></a></strong><br />
+ </dt>
+ <dd>
+ Print statistics.
+ </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>
+ <dt><strong><a name="item__2d_2dverify"><strong>--verify</strong></a></strong><br />
+ </dt>
+ <dd>
+ Verify each pass result.
+ </dd>
+ <p></p></dl>
+ <p>
+ </p>
+ <hr />
+ <h1><a name="exit_status">EXIT STATUS</a></h1>
+ <p>If <strong>gccas</strong> succeeds, it will exit with an exit status of 0.
+ Otherwise, if an error occurs, it will exit with a non-zero exit
+ status.</p>
+ <p>
+ </p>
+ <hr />
+ <h1><a name="see_also">SEE ALSO</a></h1>
+ <p><a href="././llvm-as.html">llvm-as</a>, <a href="././gccld.html">gccld</a></p>
+ <p>
+ </p>
+ <hr />
+ <h1><a name="authors">AUTHORS</a></h1>
+ <p>Maintained by the LLVM Team (<a href="http://llvm.cs.uiuc.edu">http://llvm.cs.uiuc.edu</a>).</p>
+
+ </body>
+
+ </html>
Index: llvm-www/releases/1.3/docs/CommandGuide/html/gccld.html
diff -c /dev/null llvm-www/releases/1.3/docs/CommandGuide/html/gccld.html:1.1
*** /dev/null Fri Aug 13 17:11:34 2004
--- llvm-www/releases/1.3/docs/CommandGuide/html/gccld.html Fri Aug 13 17:11:24 2004
***************
*** 0 ****
--- 1,251 ----
+ <!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>gccld - optimizing LLVM linker</title>
+ <link rel="stylesheet" href="manpage.css" type="text/css" />
+ <link rev="made" href="mailto:criswell at choi.cs.uiuc.edu" />
+ </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>
+ <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>gccld - optimizing LLVM linker</p>
+ <p>
+ </p>
+ <hr />
+ <h1><a name="synopsis">SYNOPSIS</a></h1>
+ <p><strong>gccld</strong> [<em>options</em>] <em>filename ...</em></p>
+ <p>
+ </p>
+ <hr />
+ <h1><a name="description">DESCRIPTION</a></h1>
+ <p>The <strong>gccld</strong> utility takes a set of LLVM bytecode files and links them
+ together into a single LLVM bytecode file. The output bytecode file can be
+ another bytecode library or an executable bytecode program. Using additional
+ options, <strong>gccld</strong> is able to produce native code executables.</p>
+ <p>The <strong>gccld</strong> utility is primarily used by the <a href="././llvmgcc.html">the llvmgcc manpage</a> and
+ <a href="././llvmgxx.html">llvmg++</a> front-ends, and as such, attempts to mimic the interface
+ provided by the default system linker so that it can act as a ``drop-in''
+ replacement.</p>
+ <p>The <strong>gccld</strong> tool performs a small set of interprocedural, post-link
+ optimizations on the program.</p>
+ <p>
+ </p>
+ <h2><a name="search_order">Search Order</a></h2>
+ <p>When looking for objects specified on the command line, <strong>gccld</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>gccld</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
+ were specified. If the library cannot be located, then <strong>gccld</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 shared library extension 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 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 bytecode 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>gccld</strong> program has limited support for native code generation, when
+ using the <strong>-native</strong> or <strong>-native-cbe</strong> options.</p>
+ <p>
+ </p>
+ <hr />
+ <h1><a name="options">OPTIONS</a></h1>
+ <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__2do_filename"><strong>-o</strong> <em>filename</em></a></strong><br />
+ </dt>
+ <dd>
+ Specify the output filename which will hold the linked bytecode.
+ </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__2dverify"><strong>-verify</strong></a></strong><br />
+ </dt>
+ <dd>
+ Verify each pass result.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2ddisable_2dopt"><strong>-disable-opt</strong></a></strong><br />
+ </dt>
+ <dd>
+ Disable all link-time optimization passes.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2ddisable_2dinlining"><strong>-disable-inlining</strong></a></strong><br />
+ </dt>
+ <dd>
+ Do not run the inliner pass.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2dldirectory"><strong>-L</strong><em>directory</em></a></strong><br />
+ </dt>
+ <dd>
+ Add directory to the list of directories to search when looking for
+ libraries.
+ </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__2dinternalize_2dpublic_2dapi_2dfile_filename"><strong>-internalize-public-api-file</strong> <em>filename</em></a></strong><br />
+ </dt>
+ <dd>
+ Preserve the list of symbol names in the file filename.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2dinternalize_2dpublic_2dapi_2dlist__26lt_3blist_"><strong>-internalize-public-api-list <list></strong></a></strong><br />
+ </dt>
+ <dd>
+ Preserve the symbol names in list.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2dllibrary"><strong>-l</strong><em>library</em></a></strong><br />
+ </dt>
+ <dd>
+ Specify libraries to include when linking the output file. When linking,
+ <strong>gccld</strong> will first attempt to load a file with the pathname <strong>library</strong>. If
+ that fails, it will then attempt to load lib<em>library</em>.bc, lib<em>library</em>.a, and
+ lib<em>library</em>.<em>shared library extension</em>, in that order.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2dlink_2das_2dlibrary"><strong>-link-as-library</strong></a></strong><br />
+ </dt>
+ <dd>
+ Link the .bc files together as a library, not an executable.
+ </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>gccld</strong> first checks for a bytecode
+ version of the library and links it in, if necessary. If the library is
+ missing, <strong>gccld</strong> skips it. Then, <strong>gccld</strong> links in the same
+ libraries as native code.</p>
+ </dd>
+ <dd>
+ <p>In this way, <strong>gccld</strong> should be able to link in optimized bytecode
+ subsets of common libraries and then link in any part of the library that
+ hasn't been converted to bytecode.</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>
+ <dt><strong><a name="item__2ds"><strong>-s</strong></a></strong><br />
+ </dt>
+ <dd>
+ Strip symbol information from the generated executable.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2dv"><strong>-v</strong></a></strong><br />
+ </dt>
+ <dd>
+ Print information about actions taken.
+ </dd>
+ <p></p></dl>
+ <p>
+ </p>
+ <hr />
+ <h1><a name="exit_status">EXIT STATUS</a></h1>
+ <p>If <strong>gccld</strong> succeeds, it will exit with an exit status of 0.
+ Otherwise, if an error occurs, it will exit with a non-zero exit
+ status.</p>
+ <p>
+ </p>
+ <hr />
+ <h1><a name="see_also">SEE ALSO</a></h1>
+ <p><a href="././llvm-link.html">llvm-link</a>, <a href="././gccas.html">gccas</a></p>
+ <p>
+ </p>
+ <hr />
+ <h1><a name="authors">AUTHORS</a></h1>
+ <p>Maintained by the LLVM Team (<a href="http://llvm.cs.uiuc.edu">http://llvm.cs.uiuc.edu</a>).</p>
+
+ </body>
+
+ </html>
Index: llvm-www/releases/1.3/docs/CommandGuide/html/llc.html
diff -c /dev/null llvm-www/releases/1.3/docs/CommandGuide/html/llc.html:1.1
*** /dev/null Fri Aug 13 17:11:35 2004
--- llvm-www/releases/1.3/docs/CommandGuide/html/llc.html Fri Aug 13 17:11:24 2004
***************
*** 0 ****
--- 1,266 ----
+ <!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 - LLVM static compiler</title>
+ <link rel="stylesheet" href="manpage.css" type="text/css" />
+ <link rev="made" href="mailto:criswell at choi.cs.uiuc.edu" />
+ </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="#intel_ia32specific_options">Intel IA-32-specific Options</a></li>
+ <li><a href="#sparcv9specific_options">SPARCV9-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 bytecode into assembly language for a
+ specified architecture. The assembly language output can then be passed through
+ a native assembler and linker to generate native code.</p>
+ <p>The choice of architecture for the output assembly code is determined as
+ follows, by attempting to satisfy each of the following rules in turn (first
+ one wins):</p>
+ <ul>
+ <li></li>
+ If the user has specified an architecture with the -m option, use that
+ architecture.
+ <p></p>
+ <li></li>
+ Examine the input LLVM bytecode file: if it is little endian and has a
+ pointer size of 32 bits, select the Intel IA-32 architecture. If it is big
+ endian and has a pointer size of 64 bits, select the SparcV9 architecture.
+ <p></p>
+ <li></li>
+ If <strong>llc</strong> was compiled on an architecture for which it can generate code, select
+ the architecture upon which <strong>llc</strong> was compiled.
+ <p></p>
+ <li></li>
+ Exit with an error message telling the user to specify the output
+ architecture explicitly.
+ <p></p></ul>
+ <p>
+ </p>
+ <hr />
+ <h1><a name="options">OPTIONS</a></h1>
+ <p>If <em>filename</em> is - or omitted, <strong>llc</strong> reads LLVM bytecode from standard input.
+ Otherwise, it will read LLVM bytecode 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>
+ <dl>
+ <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__2dmarch_3darch"><strong>-march</strong>=<em>arch</em></a></strong><br />
+ </dt>
+ <dd>
+ Specify the architecture for which to generate assembly. Valid
+ architectures are:
+ </dd>
+ <dl>
+ <dt><strong><a name="item_x86"><em>x86</em></a></strong><br />
+ </dt>
+ <dd>
+ Intel IA-32 (Pentium and above)
+ </dd>
+ <p></p>
+ <dt><strong><a name="item_sparcv9"><em>sparcv9</em></a></strong><br />
+ </dt>
+ <dd>
+ 64-bit SPARC V9
+ </dd>
+ <p></p>
+ <dt><strong><a name="item_c"><em>c</em></a></strong><br />
+ </dt>
+ <dd>
+ Emit C code, not assembly
+ </dd>
+ <p></p></dl>
+ <dt><strong><a name="item__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__2dhelp"><strong>-help</strong></a></strong><br />
+ </dt>
+ <dd>
+ Print a summary of command line options.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2dstats"><strong>-stats</strong></a></strong><br />
+ </dt>
+ <dd>
+ Print statistics recorded by code-generation passes.
+ </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 a report to standard
+ error.
+ </dd>
+ <p></p></dl>
+ <p>
+ </p>
+ <h2><a name="intel_ia32specific_options">Intel IA-32-specific Options</a></h2>
+ <dl>
+ <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_2dpattern_2disel"><strong>--disable-pattern-isel</strong></a></strong><br />
+ </dt>
+ <dd>
+ Use the 'simple' X86 instruction selector (the default).
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2d_2dprint_2dmachineinstrs"><strong>--print-machineinstrs</strong></a></strong><br />
+ </dt>
+ <dd>
+ Print generated machine code.
+ </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="sparcv9specific_options">SPARCV9-specific Options</a></h2>
+ <dl>
+ <dt><strong><a name="item__2d_2ddisable_2dpeephole"><strong>--disable-peephole</strong></a></strong><br />
+ </dt>
+ <dd>
+ Disable peephole optimization pass.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2d_2ddisable_2dsched"><strong>--disable-sched</strong></a></strong><br />
+ </dt>
+ <dd>
+ Disable local scheduling pass.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2d_2ddisable_2dstrip"><strong>--disable-strip</strong></a></strong><br />
+ </dt>
+ <dd>
+ The Sparc backend embeds the LLVM bytecode into the assembly output. This
+ option requests that symbol names be retained; by default, they are stripped out.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2d_2denable_2dmaps"><strong>--enable-maps</strong></a></strong><br />
+ </dt>
+ <dd>
+ Emit LLVM-to-machine code mapping information into the assembly output.
+ </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.cs.uiuc.edu">http://llvm.cs.uiuc.edu</a>).</p>
+
+ </body>
+
+ </html>
Index: llvm-www/releases/1.3/docs/CommandGuide/html/lli.html
diff -c /dev/null llvm-www/releases/1.3/docs/CommandGuide/html/lli.html:1.1
*** /dev/null Fri Aug 13 17:11:35 2004
--- llvm-www/releases/1.3/docs/CommandGuide/html/lli.html Fri Aug 13 17:11:24 2004
***************
*** 0 ****
--- 1,119 ----
+ <!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 - directly execute programs from LLVM bytecode</title>
+ <link rel="stylesheet" href="manpage.css" type="text/css" />
+ <link rev="made" href="mailto:criswell at choi.cs.uiuc.edu" />
+ </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>lli - directly execute programs from LLVM bytecode</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 bytecode format. It takes a program
+ in LLVM bytecode 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 bytecode 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="options">OPTIONS</a></h1>
+ <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__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__2dmarch_3darch"><strong>-march</strong>=<em>arch</em></a></strong><br />
+ </dt>
+ <dd>
+ Use the specified non-default architecture arch when selecting a code generator
+ for the just-in-time compiler. This may result in a crash if you pick an
+ architecture which is not compatible with the hardware you are running <strong>lli</strong> on.
+ </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__2df_3dname"><strong>-f</strong>=<em>name</em></a></strong><br />
+ </dt>
+ <dd>
+ Call the function named <em>name</em> to start the program. Note: The
+ function is assumed to have the C signature <code>int</code> <em>name</em> <code>(int,
+ char **, char **)</code>. If you try to use this option to call a function of
+ incompatible type, undefined behavior may result. Defaults to <code>main</code>.
+ </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.cs.uiuc.edu">http://llvm.cs.uiuc.edu</a>).</p>
+
+ </body>
+
+ </html>
Index: llvm-www/releases/1.3/docs/CommandGuide/html/llvm-as.html
diff -c /dev/null llvm-www/releases/1.3/docs/CommandGuide/html/llvm-as.html:1.1
*** /dev/null Fri Aug 13 17:11:35 2004
--- llvm-www/releases/1.3/docs/CommandGuide/html/llvm-as.html Fri Aug 13 17:11:24 2004
***************
*** 0 ****
--- 1,121 ----
+ <!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 - LLVM assembler</title>
+ <link rel="stylesheet" href="manpage.css" type="text/css" />
+ <link rev="made" href="mailto:criswell at choi.cs.uiuc.edu" />
+ </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>The <strong>llvm-as</strong> command invokes the LLVM assembler. It reads a file containing
+ human-readable LLVM assembly language, translates it to LLVM bytecode, 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 bytecode.
+ </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>
+ <dt><strong><a name="item__2d_2dstats"><strong>--stats</strong></a></strong><br />
+ </dt>
+ <dd>
+ Print statistics.
+ </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>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>, <a href="././gccas.html">gccas</a></p>
+ <p>
+ </p>
+ <hr />
+ <h1><a name="authors">AUTHORS</a></h1>
+ <p>Maintained by the LLVM Team (<a href="http://llvm.cs.uiuc.edu">http://llvm.cs.uiuc.edu</a>).</p>
+
+ </body>
+
+ </html>
Index: llvm-www/releases/1.3/docs/CommandGuide/html/llvm-bcanalyzer.html
diff -c /dev/null llvm-www/releases/1.3/docs/CommandGuide/html/llvm-bcanalyzer.html:1.1
*** /dev/null Fri Aug 13 17:11:35 2004
--- llvm-www/releases/1.3/docs/CommandGuide/html/llvm-bcanalyzer.html Fri Aug 13 17:11:24 2004
***************
*** 0 ****
--- 1,105 ----
+ <!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 - LLVM bytecode analyzer</title>
+ <link rel="stylesheet" href="manpage.css" type="text/css" />
+ <link rev="made" href="mailto:criswell at choi.cs.uiuc.edu" />
+ </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-bcanalyzer - LLVM bytecode 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 bytecode files.
+ The tool reads a bytecode file (such as generated with the <strong>llvm-as</strong> tool) and
+ produces a statistical report on the contents of the byteocde file. The tool
+ will also dump a low level but human readable version of the bytecode file.
+ This tool is probably not of much interest or utility except for those working
+ directly with the bytecode 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.</p>
+ <p>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 bytecode in a human readable format. This
+ format is significantly different from LLVM assembly and provides details about
+ the encoding of the bytecode 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 by reading the
+ bytecode. 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="see_also">SEE ALSO</a></h1>
+ <p><a href="././llvm-dis.html">llvm-dis</a>, <a href="http://llvm.cs.uiuc.edu/docs/BytecodeFormat.html">http://llvm.cs.uiuc.edu/docs/BytecodeFormat.html</a></p>
+ <p>
+ </p>
+ <hr />
+ <h1><a name="authors">AUTHORS</a></h1>
+ <p>Maintained by the LLVM Team (<a href="http://llvm.cs.uiuc.edu">http://llvm.cs.uiuc.edu</a>).</p>
+
+ </body>
+
+ </html>
Index: llvm-www/releases/1.3/docs/CommandGuide/html/llvm-db.html
diff -c /dev/null llvm-www/releases/1.3/docs/CommandGuide/html/llvm-db.html:1.1
*** /dev/null Fri Aug 13 17:11:35 2004
--- llvm-www/releases/1.3/docs/CommandGuide/html/llvm-db.html Fri Aug 13 17:11:24 2004
***************
*** 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 - LLVM debugger</title>
+ <link rel="stylesheet" href="manpage.css" type="text/css" />
+ <link rev="made" href="mailto:criswell at choi.cs.uiuc.edu" />
+ </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.cs.uiuc.edu/docs/SourceLevelDebugging.html">http://llvm.cs.uiuc.edu/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.cs.uiuc.edu">http://llvm.cs.uiuc.edu</a>).</p>
+
+ </body>
+
+ </html>
Index: llvm-www/releases/1.3/docs/CommandGuide/html/llvm-dis.html
diff -c /dev/null llvm-www/releases/1.3/docs/CommandGuide/html/llvm-dis.html:1.1
*** /dev/null Fri Aug 13 17:11:35 2004
--- llvm-www/releases/1.3/docs/CommandGuide/html/llvm-dis.html Fri Aug 13 17:11:24 2004
***************
*** 0 ****
--- 1,104 ----
+ <!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 - LLVM disassembler</title>
+ <link rel="stylesheet" href="manpage.css" type="text/css" />
+ <link rev="made" href="mailto:criswell at choi.cs.uiuc.edu" />
+ </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
+ bytecode 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>
+ <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>
+ <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.cs.uiuc.edu">http://llvm.cs.uiuc.edu</a>).</p>
+
+ </body>
+
+ </html>
Index: llvm-www/releases/1.3/docs/CommandGuide/html/llvm-link.html
diff -c /dev/null llvm-www/releases/1.3/docs/CommandGuide/html/llvm-link.html:1.1
*** /dev/null Fri Aug 13 17:11:35 2004
--- llvm-www/releases/1.3/docs/CommandGuide/html/llvm-link.html Fri Aug 13 17:11:24 2004
***************
*** 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 - LLVM linker</title>
+ <link rel="stylesheet" href="manpage.css" type="text/css" />
+ <link rev="made" href="mailto:criswell at choi.cs.uiuc.edu" />
+ </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>The <strong>llvm-link</strong> command takes several LLVM bytecode files and links them
+ together into a single LLVM bytecode file. It writes the output file to
+ standard output, unless the <strong>-o</strong> option is used to specify a filename.</p>
+ <p>The <strong>llvm-link</strong> command 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 pathname 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 alreadys 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
+ bytecode 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 bytecode 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><a href="././gccld.html">the gccld manpage</a></p>
+ <p>
+ </p>
+ <hr />
+ <h1><a name="authors">AUTHORS</a></h1>
+ <p>Maintained by the LLVM Team (<a href="http://llvm.cs.uiuc.edu">http://llvm.cs.uiuc.edu</a>).</p>
+
+ </body>
+
+ </html>
Index: llvm-www/releases/1.3/docs/CommandGuide/html/llvm-nm.html
diff -c /dev/null llvm-www/releases/1.3/docs/CommandGuide/html/llvm-nm.html:1.1
*** /dev/null Fri Aug 13 17:11:35 2004
--- llvm-www/releases/1.3/docs/CommandGuide/html/llvm-nm.html Fri Aug 13 17:11:24 2004
***************
*** 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 - list LLVM bytecode file's symbol table</title>
+ <link rel="stylesheet" href="manpage.css" type="text/css" />
+ <link rev="made" href="mailto:criswell at choi.cs.uiuc.edu" />
+ </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 bytecode 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 bytecode files,
+ or <strong>ar</strong> archives containing LLVM bytecode files, named on the command line.
+ Each symbol is listed along with some simple information about its provenance.
+ If no filename is specified, or <em>-</em> is used as a filename, <strong>llvm-nm</strong> will
+ process a bytecode 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 bytecode file
+ </dd>
+ <p></p>
+ <dt><strong><a name="item_c">C</a></strong><br />
+ </dt>
+ <dd>
+ Common (multiple defs link together into one def)
+ </dd>
+ <p></p>
+ <dt><strong><a name="item_w">W</a></strong><br />
+ </dt>
+ <dd>
+ Weak reference (multiple defs link together into zero or one defs)
+ </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 bytecode 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 bytecode 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 bytecode 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 bytecode 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 bytecode 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>, <em>ar(1)</em>, <em>nm(1)</em></p>
+ <p>
+ </p>
+ <hr />
+ <h1><a name="author">AUTHOR</a></h1>
+ <p>Maintained by the LLVM Team (<a href="http://llvm.cs.uiuc.edu">http://llvm.cs.uiuc.edu</a>).</p>
+
+ </body>
+
+ </html>
Index: llvm-www/releases/1.3/docs/CommandGuide/html/llvm-prof.html
diff -c /dev/null llvm-www/releases/1.3/docs/CommandGuide/html/llvm-prof.html:1.1
*** /dev/null Fri Aug 13 17:11:35 2004
--- llvm-www/releases/1.3/docs/CommandGuide/html/llvm-prof.html Fri Aug 13 17:11:24 2004
***************
*** 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 - print execution profile of LLVM program</title>
+ <link rel="stylesheet" href="manpage.css" type="text/css" />
+ <link rev="made" href="mailto:criswell at choi.cs.uiuc.edu" />
+ </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>bytecode 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 bytecode 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|llvm-prof</strong> returns 1 if it cannot load the bytecode 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.cs.uiuc.edu">http://llvm.cs.uiuc.edu</a>).</p>
+
+ </body>
+
+ </html>
Index: llvm-www/releases/1.3/docs/CommandGuide/html/llvmgcc.html
diff -c /dev/null llvm-www/releases/1.3/docs/CommandGuide/html/llvmgcc.html:1.1
*** /dev/null Fri Aug 13 17:11:35 2004
--- llvm-www/releases/1.3/docs/CommandGuide/html/llvmgcc.html Fri Aug 13 17:11:24 2004
***************
*** 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>llvmgcc - LLVM C front-end</title>
+ <link rel="stylesheet" href="manpage.css" type="text/css" />
+ <link rev="made" href="mailto:criswell at choi.cs.uiuc.edu" />
+ </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>llvmgcc - LLVM C front-end</p>
+ <p>
+ </p>
+ <hr />
+ <h1><a name="synopsis">SYNOPSIS</a></h1>
+ <p><strong>llvmgcc</strong> [<em>options</em>] <em>filename</em></p>
+ <p>
+ </p>
+ <hr />
+ <h1><a name="description">DESCRIPTION</a></h1>
+ <p>The <strong>llvmgcc</strong> command is the LLVM C front end. It is a modified
+ version of gcc that takes C programs and compiles them into LLVM
+ bytecode or assembly language, depending upon the options.</p>
+ <p>Unless the <strong>-S</strong> option is specified, <strong>llvmgcc</strong> will use the
+ <a href="././gccas.html">gccas</a> program to perform some optimizations and create an
+ LLVM bytecode file. Unless the <strong>-c</strong> option is specified, <strong>llvmgcc</strong>
+ will also use the <a href="././gccld.html">gccld</a> program to perform further
+ optimizations and link the resulting bytecode <code>file(s)</code> with support
+ libraries to create an executable program.</p>
+ <p>Being derived from the GNU Compiler Collection, <strong>llvmgcc</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 bytecode 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 bytecode file. This bytecode file can then be
+ linked with other bytecode 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 bytecode library.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2dwl_2coption"><strong>-Wl,</strong><em>option</em></a></strong><br />
+ </dt>
+ <dd>
+ Pass <em>option</em> to the linker (usually gccld).
+ </dd>
+ <p></p></dl>
+ <p>
+ </p>
+ <hr />
+ <h1><a name="exit_status">EXIT STATUS</a></h1>
+ <p>If <strong>llvmgcc</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">llvmg++</a>, <a href="././gccas.html">gccas</a>, <a href="././gccld.html">gccld</a></p>
+ <p>
+ </p>
+ <hr />
+ <h1><a name="authors">AUTHORS</a></h1>
+ <p>Maintained by the LLVM Team (<a href="http://llvm.cs.uiuc.edu">http://llvm.cs.uiuc.edu</a>).</p>
+
+ </body>
+
+ </html>
Index: llvm-www/releases/1.3/docs/CommandGuide/html/llvmgxx.html
diff -c /dev/null llvm-www/releases/1.3/docs/CommandGuide/html/llvmgxx.html:1.1
*** /dev/null Fri Aug 13 17:11:35 2004
--- llvm-www/releases/1.3/docs/CommandGuide/html/llvmgxx.html Fri Aug 13 17:11:24 2004
***************
*** 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>llvmg++ - LLVM C++ front-end</title>
+ <link rel="stylesheet" href="manpage.css" type="text/css" />
+ <link rev="made" href="mailto:criswell at choi.cs.uiuc.edu" />
+ </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>llvmg++ - LLVM C++ front-end</p>
+ <p>
+ </p>
+ <hr />
+ <h1><a name="synopsis">SYNOPSIS</a></h1>
+ <p><strong>llvmg++</strong> [<em>options</em>] <em>filename</em></p>
+ <p>
+ </p>
+ <hr />
+ <h1><a name="description">DESCRIPTION</a></h1>
+ <p>The <strong>llvmg++</strong> command is the LLVM C++ front end. It is a modified
+ version of g++ that takes C++ programs and compiles them into LLVM
+ bytecode or assembly language, depending upon the options.</p>
+ <p>Unless the <strong>-S</strong> option is specified, <strong>llvmg++</strong> will use the
+ <a href="././gccas.html">gccas</a> program to perform some optimizations and create an
+ LLVM bytecode file. Unless the <strong>-c</strong> option is specified, <strong>llvmg++</strong>
+ will also use the <a href="././gccld.html">gccld</a> program to perform further
+ optimizations and link the resulting bytecode <code>file(s)</code> with support
+ libraries to create an executable program.</p>
+ <p>Being derived from the GNU Compiler Collection, <strong>llvmg++</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 bytecode 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 bytecode file. This bytecode file can then be
+ linked with other bytecode 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 bytecode library.
+ </dd>
+ <p></p>
+ <dt><strong><a name="item__2dwl_2coption"><strong>-Wl,</strong><em>option</em></a></strong><br />
+ </dt>
+ <dd>
+ Pass <em>option</em> to the linker (usually gccld).
+ </dd>
+ <p></p></dl>
+ <p>
+ </p>
+ <hr />
+ <h1><a name="exit_status">EXIT STATUS</a></h1>
+ <p>If <strong>llvmg++</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">the llvmgcc manpage</a>, <a href="././gccas.html">the gccas manpage</a>, <a href="././gccld.html">the gccld manpage</a></p>
+ <p>
+ </p>
+ <hr />
+ <h1><a name="authors">AUTHORS</a></h1>
+ <p>Maintained by the LLVM Team (<a href="http://llvm.cs.uiuc.edu">http://llvm.cs.uiuc.edu</a>).</p>
+
+ </body>
+
+ </html>
Index: llvm-www/releases/1.3/docs/CommandGuide/html/manpage.css
diff -c /dev/null llvm-www/releases/1.3/docs/CommandGuide/html/manpage.css:1.1
*** /dev/null Fri Aug 13 17:11:35 2004
--- llvm-www/releases/1.3/docs/CommandGuide/html/manpage.css Fri Aug 13 17:11:24 2004
***************
*** 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/1.3/docs/CommandGuide/html/opt.html
diff -c /dev/null llvm-www/releases/1.3/docs/CommandGuide/html/opt.html:1.1
*** /dev/null Fri Aug 13 17:11:35 2004
--- llvm-www/releases/1.3/docs/CommandGuide/html/opt.html Fri Aug 13 17:11:24 2004
***************
*** 0 ****
--- 1,139 ----
+ <!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 - LLVM optimizer</title>
+ <link rel="stylesheet" href="manpage.css" type="text/css" />
+ <link rev="made" href="mailto:criswell at choi.cs.uiuc.edu" />
+ </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>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. It takes LLVM
+ bytecode as input, runs the specified optimizations on it, and then
+ outputs the optimized LLVM bytecode.</p>
+ <p>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 no filename is specified on the command line, <strong>opt</strong> reads its
+ input from standard input.</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 bytecode.
+ </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__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 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:
+ </dd>
+ <p><strong>opt -load</strong>=<em>plugin</em> <strong>-help</strong></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="see_also">SEE ALSO</a></h1>
+ <p><a href="././analyze.html">analyze</a></p>
+ <p>
+ </p>
+ <hr />
+ <h1><a name="authors">AUTHORS</a></h1>
+ <p>Maintained by the LLVM Team (<a href="http://llvm.cs.uiuc.edu">http://llvm.cs.uiuc.edu</a>).</p>
+
+ </body>
+
+ </html>
Index: llvm-www/releases/1.3/docs/CommandGuide/html/stkrc.html
diff -c /dev/null llvm-www/releases/1.3/docs/CommandGuide/html/stkrc.html:1.1
*** /dev/null Fri Aug 13 17:11:35 2004
--- llvm-www/releases/1.3/docs/CommandGuide/html/stkrc.html Fri Aug 13 17:11:24 2004
***************
*** 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 - Stacker Compiler</title>
+ <link rel="stylesheet" href="manpage.css" type="text/css" />
+ <link rev="made" href="mailto:criswell at choi.cs.uiuc.edu" />
+ </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.cs.uiuc.edu/docs/Stacker.html">http://llvm.cs.uiuc.edu/docs/Stacker.html</a> . The <strong>stkrc</strong> compiler is fairly
+ minimal. It compiles to bytecode only and doesn't perform any optimizations.
+ The output of stkrc (a bytecode 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
+ bytecode 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.cs.uiuc.edu/docs/Stacker.html">http://llvm.cs.uiuc.edu/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.cs.uiuc.edu">http://llvm.cs.uiuc.edu</a>).</p>
+
+ </body>
+
+ </html>
More information about the llvm-commits
mailing list