[llvm-commits] CVS: llvm-www/releases/1.6/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
Chris Lattner
lattner at cs.uiuc.edu
Tue Nov 8 12:07:53 PST 2005
Changes in directory llvm-www/releases/1.6/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:
check in 1.6 docs
---
Diffs of the changes: (+2396 -0)
analyze.html | 98 +++++++++++++++++++
bugpoint.html | 263 +++++++++++++++++++++++++++++++++++++++++++++++++++
extract.html | 95 ++++++++++++++++++
gccas.html | 100 +++++++++++++++++++
gccld.html | 199 ++++++++++++++++++++++++++++++++++++++
llc.html | 204 +++++++++++++++++++++++++++++++++++++++
lli.html | 99 +++++++++++++++++++
llvm-as.html | 103 +++++++++++++++++++
llvm-bcanalyzer.html | 89 +++++++++++++++++
llvm-db.html | 39 +++++++
llvm-dis.html | 88 +++++++++++++++++
llvm-link.html | 98 +++++++++++++++++++
llvm-nm.html | 142 +++++++++++++++++++++++++++
llvm-prof.html | 80 +++++++++++++++
llvmgcc.html | 109 +++++++++++++++++++++
llvmgxx.html | 109 +++++++++++++++++++++
manpage.css | 256 +++++++++++++++++++++++++++++++++++++++++++++++++
opt.html | 113 +++++++++++++++++++++
stkrc.html | 112 +++++++++++++++++++++
19 files changed, 2396 insertions(+)
Index: llvm-www/releases/1.6/docs/CommandGuide/html/analyze.html
diff -c /dev/null llvm-www/releases/1.6/docs/CommandGuide/html/analyze.html:1.1
*** /dev/null Tue Nov 8 14:07:51 2005
--- llvm-www/releases/1.6/docs/CommandGuide/html/analyze.html Tue Nov 8 14:07:41 2005
***************
*** 0 ****
--- 1,98 ----
+ <HTML>
+ <HEAD>
+ <TITLE>analyze - LLVM program analyzer</TITLE>
+ <LINK REL="stylesheet" HREF="manpage.css" TYPE="text/css">
+ <LINK REV="made" HREF="mailto:sds at cs.uiuc.edu">
+ </HEAD>
+
+ <BODY>
+
+ <A NAME="__index__"></A>
+ <!-- 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>
+ <HR>
+ <H1><A NAME="name">NAME</A></H1>
+ <P>analyze - LLVM program analyzer</P>
+ <P>
+ <HR>
+ <H1><A NAME="synopsis">SYNOPSIS</A></H1>
+ <P><STRONG>analyze</STRONG> [<EM>options</EM>] [<EM>filename</EM>]</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>
+ <HR>
+ <H1><A NAME="options">OPTIONS</A></H1>
+ <DL>
+ <DT><STRONG><A NAME="item_%2Dhelp"><STRONG>-help</STRONG></A></STRONG><BR>
+ <DD>
+ Print a summary of command line options.
+ <P></P>
+ <DT><STRONG><A NAME="item_%2Dq"><STRONG>-q</STRONG></A></STRONG><BR>
+ <DD>
+ Quiet mode. With this option, analysis pass names are not printed.
+ <P></P>
+ <DT><STRONG><A NAME="item_%2Dload_plugin"><STRONG>-load</STRONG> <EM>plugin</EM></A></STRONG><BR>
+ <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.
+ <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>
+ <P></P>
+ <DT><STRONG><A NAME="item_%2Dprofile%2Dinfo%2Dfile_filename"><STRONG>-profile-info-file</STRONG> <EM>filename</EM></A></STRONG><BR>
+ <DD>
+ Specify the name of the file loaded by the -profile-loader option.
+ <P></P>
+ <DT><STRONG><A NAME="item_%2Dstats"><STRONG>-stats</STRONG></A></STRONG><BR>
+ <DD>
+ Print statistics.
+ <P></P>
+ <DT><STRONG><A NAME="item_%2Dtime%2Dpasses"><STRONG>-time-passes</STRONG></A></STRONG><BR>
+ <DD>
+ Record the amount of time needed for each pass and print it to standard
+ error.
+ <P></P></DL>
+ <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>
+ <HR>
+ <H1><A NAME="see also">SEE ALSO</A></H1>
+ <P><A HREF="././opt.html">opt</A></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.6/docs/CommandGuide/html/bugpoint.html
diff -c /dev/null llvm-www/releases/1.6/docs/CommandGuide/html/bugpoint.html:1.1
*** /dev/null Tue Nov 8 14:07:52 2005
--- llvm-www/releases/1.6/docs/CommandGuide/html/bugpoint.html Tue Nov 8 14:07:41 2005
***************
*** 0 ****
--- 1,263 ----
+ <HTML>
+ <HEAD>
+ <TITLE>bugpoint - automatic test case reduction tool</TITLE>
+ <LINK REL="stylesheet" HREF="manpage.css" TYPE="text/css">
+ <LINK REV="made" HREF="mailto:sds at cs.uiuc.edu">
+ </HEAD>
+
+ <BODY>
+
+ <A NAME="__index__"></A>
+ <!-- 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>
+ <HR>
+ <H1><A NAME="name">NAME</A></H1>
+ <P>bugpoint - automatic test case reduction tool</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>
+ <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>
+ <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>
+ <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>
+ <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>
+ <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>
+ <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>
+ <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>
+ 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>
+ 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>
+ <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>
+ <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>
+ <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>
+ 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>
+ <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>
+ <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.
+ <P></P>
+ <DT><STRONG><A NAME="item_%2D%2Dargs_program_args"><STRONG>--args</STRONG> <EM>program args</EM></A></STRONG><BR>
+ <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:
+ <PRE>
+ bugpoint [bugpoint args] --args -- [program args]</PRE>
+ <P>The ``--'' right after the <STRONG>--args</STRONG> option tells <STRONG>bugpoint</STRONG> to consider any
+ options starting with <CODE>-</CODE> to be part of the <STRONG>--args</STRONG> option, not as options to
+ <STRONG>bugpoint</STRONG> itself.</P>
+ <P></P>
+ <DT><STRONG><A NAME="item_%2D%2Dtool%2Dargs_tool_args"><STRONG>--tool-args</STRONG> <EM>tool args</EM></A></STRONG><BR>
+ <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:
+ <PRE>
+ bugpoint [bugpoint args] --tool-args -- [tool args]</PRE>
+ <P>The ``--'' right after the <STRONG>--tool-args</STRONG> option tells <STRONG>bugpoint</STRONG> to consider any
+ options starting with <CODE>-</CODE> to be part of the <STRONG>--tool-args</STRONG> option, not as
+ options to <STRONG>bugpoint</STRONG> itself. (See <STRONG>--args</STRONG>, above.)</P>
+ <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>
+ <DD>
+ Assume a non-zero exit code or core dump from the test program is a failure.
+ Defaults to true.
+ <P></P>
+ <DT><STRONG><A NAME="item_%2D%2Ddisable%2D%7Bdce%2Csimplifycfg%7D"><STRONG>--disable-{dce,simplifycfg}</STRONG></A></STRONG><BR>
+ <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.
+ <P></P>
+ <DT><STRONG><A NAME="item_%2D%2Dhelp"><STRONG>--help</STRONG></A></STRONG><BR>
+ <DD>
+ Print a summary of command line options.
+ <P></P>
+ <DT><STRONG><A NAME="item_%2D%2Dinput_filename"><STRONG>--input</STRONG> <EM>filename</EM></A></STRONG><BR>
+ <DD>
+ Open <EM>filename</EM> and redirect the standard input of the test program, whenever
+ it runs, to come from that file.
+ <P></P>
+ <DT><STRONG><A NAME="item_%2D%2Dload_plugin"><STRONG>--load</STRONG> <EM>plugin</EM></A></STRONG><BR>
+ <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:
+ <PRE>
+ bugpoint --load myNewPass.so --help</PRE>
+ <P></P>
+ <DT><STRONG><A NAME="item_%2D%2Doutput_filename"><STRONG>--output</STRONG> <EM>filename</EM></A></STRONG><BR>
+ <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.
+ <P></P>
+ <DT><STRONG><A NAME="item_%2D%2Dprofile%2Dinfo%2Dfile_filename"><STRONG>--profile-info-file</STRONG> <EM>filename</EM></A></STRONG><BR>
+ <DD>
+ Profile file loaded by <STRONG>--profile-loader</STRONG>.
+ <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>
+ <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.
+ <P></P></DL>
+ <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>
+ <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>
+ <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.6/docs/CommandGuide/html/extract.html
diff -c /dev/null llvm-www/releases/1.6/docs/CommandGuide/html/extract.html:1.1
*** /dev/null Tue Nov 8 14:07:52 2005
--- llvm-www/releases/1.6/docs/CommandGuide/html/extract.html Tue Nov 8 14:07:41 2005
***************
*** 0 ****
--- 1,95 ----
+ <HTML>
+ <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:sds at cs.uiuc.edu">
+ </HEAD>
+
+ <BODY>
+
+ <A NAME="__index__"></A>
+ <!-- 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>
+ <HR>
+ <H1><A NAME="name">NAME</A></H1>
+ <P>extract - extract a function from an LLVM module</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>
+ <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>
+ <HR>
+ <H1><A NAME="options">OPTIONS</A></H1>
+ <DL>
+ <DT><STRONG><A NAME="item_%2Df"><STRONG>-f</STRONG></A></STRONG><BR>
+ <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.
+ <P></P>
+ <DT><STRONG><A NAME="item_%2D%2Dfunc_function%2Dname"><STRONG>--func</STRONG> <EM>function-name</EM></A></STRONG><BR>
+ <DD>
+ Extract the function named <EM>function-name</EM> from the LLVM bytecode.
+ <P></P>
+ <DT><STRONG><A NAME="item_%2D%2Dhelp"><STRONG>--help</STRONG></A></STRONG><BR>
+ <DD>
+ Print a summary of command line options.
+ <P></P>
+ <DT><STRONG><A NAME="item_%2Do_filename"><STRONG>-o</STRONG> <EM>filename</EM></A></STRONG><BR>
+ <DD>
+ Specify the output filename. If filename is ``-'' (the default), then
+ <STRONG>extract</STRONG> sends its output to standard output.
+ <P></P>
+ <DT><STRONG><A NAME="item_%2D%2Dstats"><STRONG>--stats</STRONG></A></STRONG><BR>
+ <DD>
+ Print statistics.
+ <P></P>
+ <DT><STRONG><A NAME="item_%2D%2Dtime%2Dpasses"><STRONG>--time-passes</STRONG></A></STRONG><BR>
+ <DD>
+ Record the amount of time needed for each pass and print it to standard
+ error.
+ <P></P></DL>
+ <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>
+ <HR>
+ <H1><A NAME="see also">SEE ALSO</A></H1>
+ <P><A HREF="././bugpoint.html">bugpoint</A></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.6/docs/CommandGuide/html/gccas.html
diff -c /dev/null llvm-www/releases/1.6/docs/CommandGuide/html/gccas.html:1.1
*** /dev/null Tue Nov 8 14:07:52 2005
--- llvm-www/releases/1.6/docs/CommandGuide/html/gccas.html Tue Nov 8 14:07:41 2005
***************
*** 0 ****
--- 1,100 ----
+ <HTML>
+ <HEAD>
+ <TITLE>gccas - optimizing LLVM assembler</TITLE>
+ <LINK REL="stylesheet" HREF="manpage.css" TYPE="text/css">
+ <LINK REV="made" HREF="mailto:sds at cs.uiuc.edu">
+ </HEAD>
+
+ <BODY>
+
+ <A NAME="__index__"></A>
+ <!-- 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>
+ <HR>
+ <H1><A NAME="name">NAME</A></H1>
+ <P>gccas - optimizing LLVM assembler</P>
+ <P>
+ <HR>
+ <H1><A NAME="synopsis">SYNOPSIS</A></H1>
+ <P><STRONG>gccas</STRONG> [<EM>options</EM>] <EM>filename</EM></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>
+ <HR>
+ <H1><A NAME="options">OPTIONS</A></H1>
+ <DL>
+ <DT><STRONG><A NAME="item_%2D%2Dhelp"><STRONG>--help</STRONG></A></STRONG><BR>
+ <DD>
+ Print a summary of command line options.
+ <P></P>
+ <DT><STRONG><A NAME="item_%2Do_filename"><STRONG>-o</STRONG> <EM>filename</EM></A></STRONG><BR>
+ <DD>
+ Specify the name of the output file which will hold the assembled bytecode.
+ <P></P>
+ <DT><STRONG><A NAME="item_%2D%2Ddisable%2Dinlining"><STRONG>--disable-inlining</STRONG></A></STRONG><BR>
+ <DD>
+ Disable the inlining pass. By default, it is enabled.
+ <P></P>
+ <DT><STRONG><A NAME="item_%2D%2Ddisable%2Dopt"><STRONG>--disable-opt</STRONG></A></STRONG><BR>
+ <DD>
+ Disable all assembler-time optimization passes.
+ <P></P>
+ <DT><STRONG><A NAME="item_%2D%2Dstats"><STRONG>--stats</STRONG></A></STRONG><BR>
+ <DD>
+ Print statistics.
+ <P></P>
+ <DT><STRONG><A NAME="item_%2D%2Dtime%2Dpasses"><STRONG>--time-passes</STRONG></A></STRONG><BR>
+ <DD>
+ Record the amount of time needed for each pass and print it to standard
+ error.
+ <P></P>
+ <DT><STRONG><A NAME="item_%2D%2Dverify"><STRONG>--verify</STRONG></A></STRONG><BR>
+ <DD>
+ Verify each pass result.
+ <P></P></DL>
+ <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>
+ <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>
+ <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.6/docs/CommandGuide/html/gccld.html
diff -c /dev/null llvm-www/releases/1.6/docs/CommandGuide/html/gccld.html:1.1
*** /dev/null Tue Nov 8 14:07:52 2005
--- llvm-www/releases/1.6/docs/CommandGuide/html/gccld.html Tue Nov 8 14:07:41 2005
***************
*** 0 ****
--- 1,199 ----
+ <HTML>
+ <HEAD>
+ <TITLE>gccld - optimizing LLVM linker</TITLE>
+ <LINK REL="stylesheet" HREF="manpage.css" TYPE="text/css">
+ <LINK REV="made" HREF="mailto:sds at cs.uiuc.edu">
+ </HEAD>
+
+ <BODY>
+
+ <A NAME="__index__"></A>
+ <!-- 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>
+ <HR>
+ <H1><A NAME="name">NAME</A></H1>
+ <P>gccld - optimizing LLVM linker</P>
+ <P>
+ <HR>
+ <H1><A NAME="synopsis">SYNOPSIS</A></H1>
+ <P><STRONG>gccld</STRONG> [<EM>options</EM>] <EM>filename ...</EM></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>
+ <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>
+ <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>
+ <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>
+ <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>
+ <HR>
+ <H1><A NAME="options">OPTIONS</A></H1>
+ <DL>
+ <DT><STRONG><A NAME="item_%2Dhelp"><STRONG>-help</STRONG></A></STRONG><BR>
+ <DD>
+ Print a summary of command line options.
+ <P></P>
+ <DT><STRONG><A NAME="item_%2Do_filename"><STRONG>-o</STRONG> <EM>filename</EM></A></STRONG><BR>
+ <DD>
+ Specify the output filename which will hold the linked bytecode.
+ <P></P>
+ <DT><STRONG><A NAME="item_%2Dstats"><STRONG>-stats</STRONG></A></STRONG><BR>
+ <DD>
+ Print statistics.
+ <P></P>
+ <DT><STRONG><A NAME="item_%2Dtime%2Dpasses"><STRONG>-time-passes</STRONG></A></STRONG><BR>
+ <DD>
+ Record the amount of time needed for each pass and print it to standard
+ error.
+ <P></P>
+ <DT><STRONG><A NAME="item_%2Dverify"><STRONG>-verify</STRONG></A></STRONG><BR>
+ <DD>
+ Verify each pass result.
+ <P></P>
+ <DT><STRONG><A NAME="item_%2Ddisable%2Dopt"><STRONG>-disable-opt</STRONG></A></STRONG><BR>
+ <DD>
+ Disable all link-time optimization passes.
+ <P></P>
+ <DT><STRONG><A NAME="item_%2Ddisable%2Dinlining"><STRONG>-disable-inlining</STRONG></A></STRONG><BR>
+ <DD>
+ Do not run the inliner pass.
+ <P></P>
+ <DT><STRONG><A NAME="item_%2DLdirectory"><STRONG>-L</STRONG><EM>directory</EM></A></STRONG><BR>
+ <DD>
+ Add directory to the list of directories to search when looking for
+ libraries.
+ <P></P>
+ <DT><STRONG><A NAME="item_%2Ddisable%2Dinternalize"><STRONG>-disable-internalize</STRONG></A></STRONG><BR>
+ <DD>
+ Do not mark all symbols as internal.
+ <P></P>
+ <DT><STRONG><A NAME="item_%2Dinternalize%2Dpublic%2Dapi%2Dfile_filename"><STRONG>-internalize-public-api-file</STRONG> <EM>filename</EM></A></STRONG><BR>
+ <DD>
+ Preserve the list of symbol names in the file filename.
+ <P></P>
+ <DT><STRONG><A NAME="item_%2Dinternalize%2Dpublic%2Dapi%2Dlist_%26lt%3Blist%"><STRONG>-internalize-public-api-list <list></STRONG></A></STRONG><BR>
+ <DD>
+ Preserve the symbol names in list.
+ <P></P>
+ <DT><STRONG><A NAME="item_%2Dllibrary"><STRONG>-l</STRONG><EM>library</EM></A></STRONG><BR>
+ <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.
+ <P></P>
+ <DT><STRONG><A NAME="item_%2Dlink%2Das%2Dlibrary"><STRONG>-link-as-library</STRONG></A></STRONG><BR>
+ <DD>
+ Link the .bc files together as a library, not an executable.
+ <P></P>
+ <DT><STRONG><A NAME="item_%2Dnative"><STRONG>-native</STRONG></A></STRONG><BR>
+ <DD>
+ Generate a native machine code executable.
+ <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>
+ <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>
+ <P></P>
+ <DT><STRONG><A NAME="item_%2Dnative%2Dcbe"><STRONG>-native-cbe</STRONG></A></STRONG><BR>
+ <DD>
+ Generate a native machine code executable with the LLVM C backend.
+
+ <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>
+ <P></P>
+ <DT><STRONG><A NAME="item_%2Ds"><STRONG>-s</STRONG></A></STRONG><BR>
+ <DD>
+ Strip symbol information from the generated executable.
+ <P></P>
+ <DT><STRONG><A NAME="item_%2Dv"><STRONG>-v</STRONG></A></STRONG><BR>
+ <DD>
+ Print information about actions taken.
+ <P></P></DL>
+ <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>
+ <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>
+ <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.6/docs/CommandGuide/html/llc.html
diff -c /dev/null llvm-www/releases/1.6/docs/CommandGuide/html/llc.html:1.1
*** /dev/null Tue Nov 8 14:07:52 2005
--- llvm-www/releases/1.6/docs/CommandGuide/html/llc.html Tue Nov 8 14:07:41 2005
***************
*** 0 ****
--- 1,204 ----
+ <HTML>
+ <HEAD>
+ <TITLE>llc - LLVM static compiler</TITLE>
+ <LINK REL="stylesheet" HREF="manpage.css" TYPE="text/css">
+ <LINK REV="made" HREF="mailto:sds at cs.uiuc.edu">
+ </HEAD>
+
+ <BODY>
+
+ <A NAME="__index__"></A>
+ <!-- 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>
+ <HR>
+ <H1><A NAME="name">NAME</A></H1>
+ <P>llc - LLVM static compiler</P>
+ <P>
+ <HR>
+ <H1><A NAME="synopsis">SYNOPSIS</A></H1>
+ <P><STRONG>llc</STRONG> [<EM>options</EM>] [<EM>filename</EM>]</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>
+ If the user has specified an architecture with the -m option, use that
+ architecture.
+ <P></P>
+ <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>
+ 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>
+ Exit with an error message telling the user to specify the output
+ architecture explicitly.
+ <P></P></UL>
+ <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>
+ <DD>
+ Overwrite output files. By default, <STRONG>llc</STRONG> will refuse to overwrite
+ an output file which already exists.
+ <P></P>
+ <DT><STRONG><A NAME="item_%2Dmarch%3Darch"><STRONG>-march</STRONG>=<EM>arch</EM></A></STRONG><BR>
+ <DD>
+ Specify the architecture for which to generate assembly. Valid
+ architectures are:
+ <DL>
+ <DT><STRONG><A NAME="item_x86"><EM>x86</EM></A></STRONG><BR>
+ <DD>
+ Intel IA-32 (Pentium and above)
+ <P></P>
+ <DT><STRONG><A NAME="item_sparcv9"><EM>sparcv9</EM></A></STRONG><BR>
+ <DD>
+ 64-bit SPARC V9
+ <P></P>
+ <DT><STRONG><A NAME="item_c"><EM>c</EM></A></STRONG><BR>
+ <DD>
+ Emit C code, not assembly
+ <P></P></DL>
+ <DT><STRONG><A NAME="item_%2Denable%2Dcorrect%2Deh%2Dsupport"><STRONG>-enable-correct-eh-support</STRONG></A></STRONG><BR>
+ <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.
+ <P></P>
+ <DT><STRONG><A NAME="item_%2Dhelp"><STRONG>-help</STRONG></A></STRONG><BR>
+ <DD>
+ Print a summary of command line options.
+ <P></P>
+ <DT><STRONG><A NAME="item_%2Dstats"><STRONG>-stats</STRONG></A></STRONG><BR>
+ <DD>
+ Print statistics recorded by code-generation passes.
+ <P></P>
+ <DT><STRONG><A NAME="item_%2Dtime%2Dpasses"><STRONG>-time-passes</STRONG></A></STRONG><BR>
+ <DD>
+ Record the amount of time needed for each pass and print a report to standard
+ error.
+ <P></P></DL>
+ <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>
+ <DD>
+ Disable frame pointer elimination optimization.
+ <P></P>
+ <DT><STRONG><A NAME="item_%2D%2Ddisable%2Dpattern%2Disel"><STRONG>--disable-pattern-isel</STRONG></A></STRONG><BR>
+ <DD>
+ Use the 'simple' X86 instruction selector (the default).
+ <P></P>
+ <DT><STRONG><A NAME="item_%2D%2Dprint%2Dmachineinstrs"><STRONG>--print-machineinstrs</STRONG></A></STRONG><BR>
+ <DD>
+ Print generated machine code.
+ <P></P>
+ <DT><STRONG><A NAME="item_%2D%2Dregalloc%3Dallocator"><STRONG>--regalloc</STRONG>=<EM>allocator</EM></A></STRONG><BR>
+ <DD>
+ Specify the register allocator to use. The default <EM>allocator</EM> is <EM>local</EM>.
+ Valid register allocators are:
+ <DL>
+ <DT><STRONG><A NAME="item_simple"><EM>simple</EM></A></STRONG><BR>
+ <DD>
+ Very simple ``always spill'' register allocator
+ <P></P>
+ <DT><STRONG><A NAME="item_local"><EM>local</EM></A></STRONG><BR>
+ <DD>
+ Local register allocator
+ <P></P>
+ <DT><STRONG><A NAME="item_linearscan"><EM>linearscan</EM></A></STRONG><BR>
+ <DD>
+ Linear scan global register allocator (experimental)
+ <P></P></DL>
+ <DT><STRONG><A NAME="item_%2D%2Dspiller%3Dspiller"><STRONG>--spiller</STRONG>=<EM>spiller</EM></A></STRONG><BR>
+ <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:
+ <DL>
+ <DT><STRONG><EM>simple</EM></STRONG><BR>
+ <DD>
+ Simple spiller
+ <P></P>
+ <DT><STRONG><EM>local</EM></STRONG><BR>
+ <DD>
+ Local spiller
+ <P></P></DL>
+ </DL>
+ <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>
+ <DD>
+ Disable peephole optimization pass.
+ <P></P>
+ <DT><STRONG><A NAME="item_%2D%2Ddisable%2Dsched"><STRONG>--disable-sched</STRONG></A></STRONG><BR>
+ <DD>
+ Disable local scheduling pass.
+ <P></P>
+ <DT><STRONG><A NAME="item_%2D%2Ddisable%2Dstrip"><STRONG>--disable-strip</STRONG></A></STRONG><BR>
+ <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.
+ <P></P>
+ <DT><STRONG><A NAME="item_%2D%2Denable%2Dmaps"><STRONG>--enable-maps</STRONG></A></STRONG><BR>
+ <DD>
+ Emit LLVM-to-machine code mapping information into the assembly output.
+ <P></P></DL>
+ <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>
+ <HR>
+ <H1><A NAME="see also">SEE ALSO</A></H1>
+ <P><A HREF="././lli.html">lli</A></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.6/docs/CommandGuide/html/lli.html
diff -c /dev/null llvm-www/releases/1.6/docs/CommandGuide/html/lli.html:1.1
*** /dev/null Tue Nov 8 14:07:52 2005
--- llvm-www/releases/1.6/docs/CommandGuide/html/lli.html Tue Nov 8 14:07:41 2005
***************
*** 0 ****
--- 1,99 ----
+ <HTML>
+ <HEAD>
+ <TITLE>lli - directly execute programs from LLVM bytecode</TITLE>
+ <LINK REL="stylesheet" HREF="manpage.css" TYPE="text/css">
+ <LINK REV="made" HREF="mailto:sds at cs.uiuc.edu">
+ </HEAD>
+
+ <BODY>
+
+ <A NAME="__index__"></A>
+ <!-- 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>
+ <HR>
+ <H1><A NAME="name">NAME</A></H1>
+ <P>lli - directly execute programs from LLVM bytecode</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>
+ <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>
+ <HR>
+ <H1><A NAME="options">OPTIONS</A></H1>
+ <DL>
+ <DT><STRONG><A NAME="item_%2Dhelp"><STRONG>-help</STRONG></A></STRONG><BR>
+ <DD>
+ Print a summary of command line options.
+ <P></P>
+ <DT><STRONG><A NAME="item_%2Dstats"><STRONG>-stats</STRONG></A></STRONG><BR>
+ <DD>
+ Print statistics from the code-generation passes. This is only meaningful for
+ the just-in-time compiler, at present.
+ <P></P>
+ <DT><STRONG><A NAME="item_%2Dtime%2Dpasses"><STRONG>-time-passes</STRONG></A></STRONG><BR>
+ <DD>
+ Record the amount of time needed for each code-generation pass and print it to
+ standard error.
+ <P></P>
+ <DT><STRONG><A NAME="item_%2Dmarch%3Darch"><STRONG>-march</STRONG>=<EM>arch</EM></A></STRONG><BR>
+ <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.
+ <P></P>
+ <DT><STRONG><A NAME="item_%2Dforce%2Dinterpreter%3D%7Bfalse%2Ctrue%7D"><STRONG>-force-interpreter</STRONG>=<EM>{false,true}</EM></A></STRONG><BR>
+ <DD>
+ If set to true, use the interpreter even if a just-in-time compiler is available
+ for this architecture. Defaults to false.
+ <P></P>
+ <DT><STRONG><A NAME="item_%2Df%3Dname"><STRONG>-f</STRONG>=<EM>name</EM></A></STRONG><BR>
+ <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>.
+ <P></P></DL>
+ <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>
+ <HR>
+ <H1><A NAME="see also">SEE ALSO</A></H1>
+ <P><A HREF="././llc.html">llc</A></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.6/docs/CommandGuide/html/llvm-as.html
diff -c /dev/null llvm-www/releases/1.6/docs/CommandGuide/html/llvm-as.html:1.1
*** /dev/null Tue Nov 8 14:07:52 2005
--- llvm-www/releases/1.6/docs/CommandGuide/html/llvm-as.html Tue Nov 8 14:07:41 2005
***************
*** 0 ****
--- 1,103 ----
+ <HTML>
+ <HEAD>
+ <TITLE>llvm-as - LLVM assembler</TITLE>
+ <LINK REL="stylesheet" HREF="manpage.css" TYPE="text/css">
+ <LINK REV="made" HREF="mailto:sds at cs.uiuc.edu">
+ </HEAD>
+
+ <BODY>
+
+ <A NAME="__index__"></A>
+ <!-- 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>
+ <HR>
+ <H1><A NAME="name">NAME</A></H1>
+ <P>llvm-as - LLVM assembler</P>
+ <P>
+ <HR>
+ <H1><A NAME="synopsis">SYNOPSIS</A></H1>
+ <P><STRONG>llvm-as</STRONG> [<EM>options</EM>] [<EM>filename</EM>]</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>
+ If the input is standard input, then the output is standard output.
+ <P></P>
+ <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>
+ 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>
+ <HR>
+ <H1><A NAME="options">OPTIONS</A></H1>
+ <DL>
+ <DT><STRONG><A NAME="item_%2Df"><STRONG>-f</STRONG></A></STRONG><BR>
+ <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.
+ <P></P>
+ <DT><STRONG><A NAME="item_%2D%2Dhelp"><STRONG>--help</STRONG></A></STRONG><BR>
+ <DD>
+ Print a summary of command line options.
+ <P></P>
+ <DT><STRONG><A NAME="item_%2Do_filename"><STRONG>-o</STRONG> <EM>filename</EM></A></STRONG><BR>
+ <DD>
+ Specify the output file name. If <EM>filename</EM> is <CODE>-</CODE>, then <STRONG>llvm-as</STRONG>
+ sends its output to standard output.
+ <P></P>
+ <DT><STRONG><A NAME="item_%2D%2Dstats"><STRONG>--stats</STRONG></A></STRONG><BR>
+ <DD>
+ Print statistics.
+ <P></P>
+ <DT><STRONG><A NAME="item_%2D%2Dtime%2Dpasses"><STRONG>--time-passes</STRONG></A></STRONG><BR>
+ <DD>
+ Record the amount of time needed for each pass and print it to standard
+ error.
+ <P></P></DL>
+ <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>
+ <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>
+ <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.6/docs/CommandGuide/html/llvm-bcanalyzer.html
diff -c /dev/null llvm-www/releases/1.6/docs/CommandGuide/html/llvm-bcanalyzer.html:1.1
*** /dev/null Tue Nov 8 14:07:52 2005
--- llvm-www/releases/1.6/docs/CommandGuide/html/llvm-bcanalyzer.html Tue Nov 8 14:07:41 2005
***************
*** 0 ****
--- 1,89 ----
+ <HTML>
+ <HEAD>
+ <TITLE>llvm-bcanalyzer - LLVM bytecode analyzer</TITLE>
+ <LINK REL="stylesheet" HREF="manpage.css" TYPE="text/css">
+ <LINK REV="made" HREF="mailto:sds at cs.uiuc.edu">
+ </HEAD>
+
+ <BODY>
+
+ <A NAME="__index__"></A>
+ <!-- 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>
+ <HR>
+ <H1><A NAME="name">NAME</A></H1>
+ <P>llvm-bcanalyzer - LLVM bytecode analyzer</P>
+ <P>
+ <HR>
+ <H1><A NAME="synopsis">SYNOPSIS</A></H1>
+ <P><STRONG>llvm-bcanalyzer</STRONG> [<EM>options</EM>] [<EM>filename</EM>]</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>
+ <HR>
+ <H1><A NAME="options">OPTIONS</A></H1>
+ <DL>
+ <DT><STRONG><A NAME="item_%2Dnodetails"><STRONG>-nodetails</STRONG></A></STRONG><BR>
+ <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.
+ <P></P>
+ <DT><STRONG><A NAME="item_%2Ddump"><STRONG>-dump</STRONG></A></STRONG><BR>
+ <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.
+ <P></P>
+ <DT><STRONG><A NAME="item_%2Dverify"><STRONG>-verify</STRONG></A></STRONG><BR>
+ <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.
+ <P></P>
+ <DT><STRONG><A NAME="item_%2D%2Dhelp"><STRONG>--help</STRONG></A></STRONG><BR>
+ <DD>
+ Print a summary of command line options.
+ <P></P></DL>
+ <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>
+ <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>
+ <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.6/docs/CommandGuide/html/llvm-db.html
diff -c /dev/null llvm-www/releases/1.6/docs/CommandGuide/html/llvm-db.html:1.1
*** /dev/null Tue Nov 8 14:07:52 2005
--- llvm-www/releases/1.6/docs/CommandGuide/html/llvm-db.html Tue Nov 8 14:07:41 2005
***************
*** 0 ****
--- 1,39 ----
+ <HTML>
+ <HEAD>
+ <TITLE>llvm-db - LLVM debugger</TITLE>
+ <LINK REL="stylesheet" HREF="manpage.css" TYPE="text/css">
+ <LINK REV="made" HREF="mailto:sds at cs.uiuc.edu">
+ </HEAD>
+
+ <BODY>
+
+ <A NAME="__index__"></A>
+ <!-- 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>
+ <HR>
+ <H1><A NAME="name">NAME</A></H1>
+ <P>llvm-db - LLVM debugger (alpha)</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>
+ <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.6/docs/CommandGuide/html/llvm-dis.html
diff -c /dev/null llvm-www/releases/1.6/docs/CommandGuide/html/llvm-dis.html:1.1
*** /dev/null Tue Nov 8 14:07:52 2005
--- llvm-www/releases/1.6/docs/CommandGuide/html/llvm-dis.html Tue Nov 8 14:07:41 2005
***************
*** 0 ****
--- 1,88 ----
+ <HTML>
+ <HEAD>
+ <TITLE>llvm-dis - LLVM disassembler</TITLE>
+ <LINK REL="stylesheet" HREF="manpage.css" TYPE="text/css">
+ <LINK REV="made" HREF="mailto:sds at cs.uiuc.edu">
+ </HEAD>
+
+ <BODY>
+
+ <A NAME="__index__"></A>
+ <!-- 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>
+ <HR>
+ <H1><A NAME="name">NAME</A></H1>
+ <P>llvm-dis - LLVM disassembler</P>
+ <P>
+ <HR>
+ <H1><A NAME="synopsis">SYNOPSIS</A></H1>
+ <P><STRONG>llvm-dis</STRONG> [<EM>options</EM>] [<EM>filename</EM>]</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>
+ <HR>
+ <H1><A NAME="options">OPTIONS</A></H1>
+ <DL>
+ <DT><STRONG><A NAME="item_%2Df"><STRONG>-f</STRONG></A></STRONG><BR>
+ <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.
+ <P></P>
+ <DT><STRONG><A NAME="item_%2D%2Dhelp"><STRONG>--help</STRONG></A></STRONG><BR>
+ <DD>
+ Print a summary of command line options.
+ <P></P>
+ <DT><STRONG><A NAME="item_%2Do_filename"><STRONG>-o</STRONG> <EM>filename</EM></A></STRONG><BR>
+ <DD>
+ Specify the output file name. If <EM>filename</EM> is -, then the output is sent
+ to standard output.
+ <P></P>
+ <DT><STRONG><A NAME="item_%2Dtime%2Dpasses"><STRONG>-time-passes</STRONG></A></STRONG><BR>
+ <DD>
+ Record the amount of time needed for each pass and print it to standard
+ error.
+ <P></P></DL>
+ <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>
+ <HR>
+ <H1><A NAME="see also">SEE ALSO</A></H1>
+ <P><A HREF="././llvm-as.html">llvm-as</A></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.6/docs/CommandGuide/html/llvm-link.html
diff -c /dev/null llvm-www/releases/1.6/docs/CommandGuide/html/llvm-link.html:1.1
*** /dev/null Tue Nov 8 14:07:52 2005
--- llvm-www/releases/1.6/docs/CommandGuide/html/llvm-link.html Tue Nov 8 14:07:41 2005
***************
*** 0 ****
--- 1,98 ----
+ <HTML>
+ <HEAD>
+ <TITLE>llvm-link - LLVM linker</TITLE>
+ <LINK REL="stylesheet" HREF="manpage.css" TYPE="text/css">
+ <LINK REV="made" HREF="mailto:sds at cs.uiuc.edu">
+ </HEAD>
+
+ <BODY>
+
+ <A NAME="__index__"></A>
+ <!-- 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>
+ <HR>
+ <H1><A NAME="name">NAME</A></H1>
+ <P>llvm-link - LLVM linker</P>
+ <P>
+ <HR>
+ <H1><A NAME="synopsis">SYNOPSIS</A></H1>
+ <P><STRONG>llvm-link</STRONG> [<EM>options</EM>] <EM>filename ...</EM></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>
+ <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>
+ <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.
+ <P></P>
+ <DT><STRONG><A NAME="item_%2Df"><STRONG>-f</STRONG></A></STRONG><BR>
+ <DD>
+ Overwrite output files. By default, <STRONG>llvm-link</STRONG> will not overwrite an output
+ file if it alreadys exists.
+ <P></P>
+ <DT><STRONG><A NAME="item_%2Do_filename"><STRONG>-o</STRONG> <EM>filename</EM></A></STRONG><BR>
+ <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.
+ <P></P>
+ <DT><STRONG><A NAME="item_%2Dd"><STRONG>-d</STRONG></A></STRONG><BR>
+ <DD>
+ If specified, <STRONG>llvm-link</STRONG> prints a human-readable version of the output
+ bytecode file to standard error.
+ <P></P>
+ <DT><STRONG><A NAME="item_%2D%2Dhelp"><STRONG>--help</STRONG></A></STRONG><BR>
+ <DD>
+ Print a summary of command line options.
+ <P></P>
+ <DT><STRONG><A NAME="item_%2Dv"><STRONG>-v</STRONG></A></STRONG><BR>
+ <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.
+ <P></P></DL>
+ <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>
+ <HR>
+ <H1><A NAME="see also">SEE ALSO</A></H1>
+ <P><A HREF="././gccld.html">the gccld manpage</A></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.6/docs/CommandGuide/html/llvm-nm.html
diff -c /dev/null llvm-www/releases/1.6/docs/CommandGuide/html/llvm-nm.html:1.1
*** /dev/null Tue Nov 8 14:07:52 2005
--- llvm-www/releases/1.6/docs/CommandGuide/html/llvm-nm.html Tue Nov 8 14:07:41 2005
***************
*** 0 ****
--- 1,142 ----
+ <HTML>
+ <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:sds at cs.uiuc.edu">
+ </HEAD>
+
+ <BODY>
+
+ <A NAME="__index__"></A>
+ <!-- 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>
+ <HR>
+ <H1><A NAME="name">NAME</A></H1>
+ <P>llvm-nm - list LLVM bytecode file's symbol table</P>
+ <P>
+ <HR>
+ <H1><A NAME="synopsis">SYNOPSIS</A></H1>
+ <P><STRONG>llvm-nm</STRONG> [<EM>options</EM>] [<EM>filenames...</EM>]</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>
+ <DD>
+ Named object is referenced but undefined in this bytecode file
+ <P></P>
+ <DT><STRONG><A NAME="item_C">C</A></STRONG><BR>
+ <DD>
+ Common (multiple defs link together into one def)
+ <P></P>
+ <DT><STRONG><A NAME="item_W">W</A></STRONG><BR>
+ <DD>
+ Weak reference (multiple defs link together into zero or one defs)
+ <P></P>
+ <DT><STRONG><A NAME="item_t">t</A></STRONG><BR>
+ <DD>
+ Local function (text) object
+ <P></P>
+ <DT><STRONG><A NAME="item_T">T</A></STRONG><BR>
+ <DD>
+ Global function (text) object
+ <P></P>
+ <DT><STRONG><A NAME="item_d">d</A></STRONG><BR>
+ <DD>
+ Local data object
+ <P></P>
+ <DT><STRONG><A NAME="item_D">D</A></STRONG><BR>
+ <DD>
+ Global data object
+ <P></P>
+ <DT><STRONG><A NAME="item_%3F">?</A></STRONG><BR>
+ <DD>
+ Something unrecognizable
+ <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>
+ <HR>
+ <H1><A NAME="options">OPTIONS</A></H1>
+ <DL>
+ <DT><STRONG><A NAME="item_%2DP"><STRONG>-P</STRONG></A></STRONG><BR>
+ <DD>
+ Use POSIX.2 output format. Alias for <STRONG>--format=posix</STRONG>.
+ <P></P>
+ <DT><STRONG><A NAME="item_B"><STRONG>-B</STRONG> (default)</A></STRONG><BR>
+ <DD>
+ Use BSD output format. Alias for <STRONG>--format=bsd</STRONG>.
+ <P></P>
+ <DT><STRONG><A NAME="item_%2D%2Dhelp"><STRONG>--help</STRONG></A></STRONG><BR>
+ <DD>
+ Print a summary of command-line options and their meanings.
+ <P></P>
+ <DT><STRONG><A NAME="item_%2D%2Ddefined%2Donly"><STRONG>--defined-only</STRONG></A></STRONG><BR>
+ <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.)
+ <P></P>
+ <DT><STRONG><A NAME="item_%2D%2Dextern%2Donly%2C_%2Dg"><STRONG>--extern-only</STRONG>, <STRONG>-g</STRONG></A></STRONG><BR>
+ <DD>
+ Print only symbols whose definitions are external; that is, accessible
+ from other bytecode files.
+ <P></P>
+ <DT><STRONG><A NAME="item_%2D%2Dundefined%2Donly%2C_%2Du"><STRONG>--undefined-only</STRONG>, <STRONG>-u</STRONG></A></STRONG><BR>
+ <DD>
+ Print only symbols referenced but not defined in this bytecode file.
+ <P></P>
+ <DT><STRONG><A NAME="item_%2D%2Dformat%3Dfmt%2C_%2Df"><STRONG>--format=</STRONG><EM>fmt</EM>, <STRONG>-f</STRONG></A></STRONG><BR>
+ <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>.
+ <P></P></DL>
+ <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>
+ <HR>
+ <H1><A NAME="exit status">EXIT STATUS</A></H1>
+ <P><STRONG>llvm-nm</STRONG> exits with an exit code of zero.</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>
+ <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.6/docs/CommandGuide/html/llvm-prof.html
diff -c /dev/null llvm-www/releases/1.6/docs/CommandGuide/html/llvm-prof.html:1.1
*** /dev/null Tue Nov 8 14:07:52 2005
--- llvm-www/releases/1.6/docs/CommandGuide/html/llvm-prof.html Tue Nov 8 14:07:41 2005
***************
*** 0 ****
--- 1,80 ----
+ <HTML>
+ <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:sds at cs.uiuc.edu">
+ </HEAD>
+
+ <BODY>
+
+ <A NAME="__index__"></A>
+ <!-- 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>
+ <HR>
+ <H1><A NAME="name">NAME</A></H1>
+ <P>llvm-prof - print execution profile of LLVM program</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>
+ <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>
+ <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>
+ <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.
+ <P></P>
+ <DT><STRONG><A NAME="item_%2D%2Dprint%2Dall%2Dcode"><STRONG>--print-all-code</STRONG></A></STRONG><BR>
+ <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.
+ <P></P>
+ <DT><STRONG><A NAME="item_%2D%2Dtime%2Dpasses"><STRONG>--time-passes</STRONG></A></STRONG><BR>
+ <DD>
+ Record the amount of time needed for each pass and print it to standard
+ error.
+ <P></P></DL>
+ <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>
+ <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.6/docs/CommandGuide/html/llvmgcc.html
diff -c /dev/null llvm-www/releases/1.6/docs/CommandGuide/html/llvmgcc.html:1.1
*** /dev/null Tue Nov 8 14:07:52 2005
--- llvm-www/releases/1.6/docs/CommandGuide/html/llvmgcc.html Tue Nov 8 14:07:41 2005
***************
*** 0 ****
--- 1,109 ----
+ <HTML>
+ <HEAD>
+ <TITLE>llvmgcc - LLVM C front-end</TITLE>
+ <LINK REL="stylesheet" HREF="manpage.css" TYPE="text/css">
+ <LINK REV="made" HREF="mailto:sds at cs.uiuc.edu">
+ </HEAD>
+
+ <BODY>
+
+ <A NAME="__index__"></A>
+ <!-- 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>
+ <HR>
+ <H1><A NAME="name">NAME</A></H1>
+ <P>llvmgcc - LLVM C front-end</P>
+ <P>
+ <HR>
+ <H1><A NAME="synopsis">SYNOPSIS</A></H1>
+ <P><STRONG>llvmgcc</STRONG> [<EM>options</EM>] <EM>filename</EM></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>
+ <HR>
+ <H1><A NAME="options">OPTIONS</A></H1>
+ <DL>
+ <DT><STRONG><A NAME="item_%2D%2Dhelp"><STRONG>--help</STRONG></A></STRONG><BR>
+ <DD>
+ Print a summary of command line options.
+ <P></P>
+ <DT><STRONG><A NAME="item_%2DS"><STRONG>-S</STRONG></A></STRONG><BR>
+ <DD>
+ Do not generate an LLVM bytecode file. Rather, compile the source
+ file into an LLVM assembly language file.
+ <P></P>
+ <DT><STRONG><A NAME="item_%2Dc"><STRONG>-c</STRONG></A></STRONG><BR>
+ <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.
+ <P></P>
+ <DT><STRONG><A NAME="item_%2Do_filename"><STRONG>-o</STRONG> <EM>filename</EM></A></STRONG><BR>
+ <DD>
+ Specify the output file to be <EM>filename</EM>.
+ <P></P>
+ <DT><STRONG><A NAME="item_%2DI_directory"><STRONG>-I</STRONG> <EM>directory</EM></A></STRONG><BR>
+ <DD>
+ Add a directory to the header file search path. This option can be
+ repeated.
+ <P></P>
+ <DT><STRONG><A NAME="item_%2DL_directory"><STRONG>-L</STRONG> <EM>directory</EM></A></STRONG><BR>
+ <DD>
+ Add <EM>directory</EM> to the library search path. This option can be
+ repeated.
+ <P></P>
+ <DT><STRONG><A NAME="item_%2Dlname"><STRONG>-l</STRONG><EM>name</EM></A></STRONG><BR>
+ <DD>
+ Link in the library lib<EM>name</EM>.[bc | a | so]. This library should
+ be a bytecode library.
+ <P></P>
+ <DT><STRONG><A NAME="item_%2DWl%2Coption"><STRONG>-Wl,</STRONG><EM>option</EM></A></STRONG><BR>
+ <DD>
+ Pass <EM>option</EM> to the linker (usually gccld).
+ <P></P></DL>
+ <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>
+ <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>
+ <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.6/docs/CommandGuide/html/llvmgxx.html
diff -c /dev/null llvm-www/releases/1.6/docs/CommandGuide/html/llvmgxx.html:1.1
*** /dev/null Tue Nov 8 14:07:53 2005
--- llvm-www/releases/1.6/docs/CommandGuide/html/llvmgxx.html Tue Nov 8 14:07:41 2005
***************
*** 0 ****
--- 1,109 ----
+ <HTML>
+ <HEAD>
+ <TITLE>llvmg++ - LLVM C++ front-end</TITLE>
+ <LINK REL="stylesheet" HREF="manpage.css" TYPE="text/css">
+ <LINK REV="made" HREF="mailto:sds at cs.uiuc.edu">
+ </HEAD>
+
+ <BODY>
+
+ <A NAME="__index__"></A>
+ <!-- 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>
+ <HR>
+ <H1><A NAME="name">NAME</A></H1>
+ <P>llvmg++ - LLVM C++ front-end</P>
+ <P>
+ <HR>
+ <H1><A NAME="synopsis">SYNOPSIS</A></H1>
+ <P><STRONG>llvmg++</STRONG> [<EM>options</EM>] <EM>filename</EM></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>
+ <HR>
+ <H1><A NAME="options">OPTIONS</A></H1>
+ <DL>
+ <DT><STRONG><A NAME="item_%2D%2Dhelp"><STRONG>--help</STRONG></A></STRONG><BR>
+ <DD>
+ Print a summary of command line options.
+ <P></P>
+ <DT><STRONG><A NAME="item_%2DS"><STRONG>-S</STRONG></A></STRONG><BR>
+ <DD>
+ Do not generate an LLVM bytecode file. Rather, compile the source
+ file into an LLVM assembly language file.
+ <P></P>
+ <DT><STRONG><A NAME="item_%2Dc"><STRONG>-c</STRONG></A></STRONG><BR>
+ <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.
+ <P></P>
+ <DT><STRONG><A NAME="item_%2Do_filename"><STRONG>-o</STRONG> <EM>filename</EM></A></STRONG><BR>
+ <DD>
+ Specify the output file to be <EM>filename</EM>.
+ <P></P>
+ <DT><STRONG><A NAME="item_%2DI_directory"><STRONG>-I</STRONG> <EM>directory</EM></A></STRONG><BR>
+ <DD>
+ Add a directory to the header file search path. This option can be
+ repeated.
+ <P></P>
+ <DT><STRONG><A NAME="item_%2DL_directory"><STRONG>-L</STRONG> <EM>directory</EM></A></STRONG><BR>
+ <DD>
+ Add <EM>directory</EM> to the library search path. This option can be
+ repeated.
+ <P></P>
+ <DT><STRONG><A NAME="item_%2Dlname"><STRONG>-l</STRONG><EM>name</EM></A></STRONG><BR>
+ <DD>
+ Link in the library lib<EM>name</EM>.[bc | a | so]. This library should
+ be a bytecode library.
+ <P></P>
+ <DT><STRONG><A NAME="item_%2DWl%2Coption"><STRONG>-Wl,</STRONG><EM>option</EM></A></STRONG><BR>
+ <DD>
+ Pass <EM>option</EM> to the linker (usually gccld).
+ <P></P></DL>
+ <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>
+ <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>
+ <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.6/docs/CommandGuide/html/manpage.css
diff -c /dev/null llvm-www/releases/1.6/docs/CommandGuide/html/manpage.css:1.1
*** /dev/null Tue Nov 8 14:07:53 2005
--- llvm-www/releases/1.6/docs/CommandGuide/html/manpage.css Tue Nov 8 14:07:41 2005
***************
*** 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.6/docs/CommandGuide/html/opt.html
diff -c /dev/null llvm-www/releases/1.6/docs/CommandGuide/html/opt.html:1.1
*** /dev/null Tue Nov 8 14:07:53 2005
--- llvm-www/releases/1.6/docs/CommandGuide/html/opt.html Tue Nov 8 14:07:41 2005
***************
*** 0 ****
--- 1,113 ----
+ <HTML>
+ <HEAD>
+ <TITLE>opt - LLVM optimizer</TITLE>
+ <LINK REL="stylesheet" HREF="manpage.css" TYPE="text/css">
+ <LINK REV="made" HREF="mailto:sds at cs.uiuc.edu">
+ </HEAD>
+
+ <BODY>
+
+ <A NAME="__index__"></A>
+ <!-- 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>
+ <HR>
+ <H1><A NAME="name">NAME</A></H1>
+ <P>opt - LLVM optimizer</P>
+ <P>
+ <HR>
+ <H1><A NAME="synopsis">SYNOPSIS</A></H1>
+ <P><STRONG>opt</STRONG> [<EM>options</EM>] [<EM>filename</EM>]</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>
+ <HR>
+ <H1><A NAME="options">OPTIONS</A></H1>
+ <DL>
+ <DT><STRONG><A NAME="item_%2Df"><STRONG>-f</STRONG></A></STRONG><BR>
+ <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.
+ <P></P>
+ <DT><STRONG><A NAME="item_%2Dhelp"><STRONG>-help</STRONG></A></STRONG><BR>
+ <DD>
+ Print a summary of command line options.
+ <P></P>
+ <DT><STRONG><A NAME="item_%2Do_filename"><STRONG>-o</STRONG> <EM>filename</EM></A></STRONG><BR>
+ <DD>
+ Specify the output filename.
+ <P></P>
+ <DT><STRONG><A NAME="item_%2Dprofile%2Dinfo%2Dfile_filename"><STRONG>-profile-info-file</STRONG> <EM>filename</EM></A></STRONG><BR>
+ <DD>
+ Specify the name of the file loaded by the -profile-loader option.
+ <P></P>
+ <DT><STRONG><A NAME="item_%2Dstats"><STRONG>-stats</STRONG></A></STRONG><BR>
+ <DD>
+ Print statistics.
+ <P></P>
+ <DT><STRONG><A NAME="item_%2Dtime%2Dpasses"><STRONG>-time-passes</STRONG></A></STRONG><BR>
+ <DD>
+ Record the amount of time needed for each pass and print it to standard
+ error.
+ <P></P>
+ <DT><STRONG><A NAME="item_%2Ddebug"><STRONG>-debug</STRONG></A></STRONG><BR>
+ <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.
+ <P></P>
+ <DT><STRONG><A NAME="item_%2Dload%3Dplugin"><STRONG>-load</STRONG>=<EM>plugin</EM></A></STRONG><BR>
+ <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:
+ <P><STRONG>opt -load</STRONG>=<EM>plugin</EM> <STRONG>-help</STRONG></P>
+ <DT><STRONG><A NAME="item_%2Dp"><STRONG>-p</STRONG></A></STRONG><BR>
+ <DD>
+ Print module after each transformation.
+ <P></P></DL>
+ <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>
+ <HR>
+ <H1><A NAME="see also">SEE ALSO</A></H1>
+ <P><A HREF="././analyze.html">analyze</A></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.6/docs/CommandGuide/html/stkrc.html
diff -c /dev/null llvm-www/releases/1.6/docs/CommandGuide/html/stkrc.html:1.1
*** /dev/null Tue Nov 8 14:07:53 2005
--- llvm-www/releases/1.6/docs/CommandGuide/html/stkrc.html Tue Nov 8 14:07:41 2005
***************
*** 0 ****
--- 1,112 ----
+ <HTML>
+ <HEAD>
+ <TITLE>stkrc - Stacker Compiler</TITLE>
+ <LINK REL="stylesheet" HREF="manpage.css" TYPE="text/css">
+ <LINK REV="made" HREF="mailto:sds at cs.uiuc.edu">
+ </HEAD>
+
+ <BODY>
+
+ <A NAME="__index__"></A>
+ <!-- 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>
+ <HR>
+ <H1><A NAME="name">NAME</A></H1>
+ <P>stkrc - Stacker Compiler</P>
+ <P>
+ <HR>
+ <H1><A NAME="synopsis">SYNOPSIS</A></H1>
+ <P><STRONG>stkrc</STRONG> [<EM>options</EM>] [<EM>filename</EM>]</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>
+ If the input is standard input, then the output is standard output.
+ <P></P>
+ <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>
+ 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>
+ <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>
+ <DD>
+ Specify the output file name. If <EM>filename</EM> is <CODE>-</CODE>, then <STRONG>llvm-as</STRONG>
+ sends its output to standard output.
+ <P></P>
+ <DT><STRONG><A NAME="item_%2Dstats"><STRONG>-stats</STRONG></A></STRONG><BR>
+ <DD>
+ Print statistics acquired during compilation.
+ <P></P>
+ <DT><STRONG><A NAME="item_%2Dtime%2Dpasses"><STRONG>-time-passes</STRONG></A></STRONG><BR>
+ <DD>
+ Record the amount of time needed for each pass and print it to standard
+ error.
+ <P></P>
+ <DT><STRONG><A NAME="item_%2Df"><STRONG>-f</STRONG></A></STRONG><BR>
+ <DD>
+ Force the output to be written. Normally, <STRONG>stkrc</STRONG> won't overwrite an existing
+ bytecode file. This option overrides that behavior.
+ <P></P>
+ <DT><STRONG><A NAME="item_%2Ds%3Dstacksize"><STRONG>-s=stacksize</STRONG></A></STRONG><BR>
+ <DD>
+ Specify the stack size for the program. The default stack size, 1024, should be
+ sufficient for most programs. For very large, programs, you might want to
+ provide a larger value.
+ <P></P>
+ <DT><STRONG><A NAME="item_%2Dhelp"><STRONG>-help</STRONG></A></STRONG><BR>
+ <DD>
+ Print a summary of command line options.
+ <P></P></DL>
+ <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>
+ <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>
+ <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