diff options
| -rw-r--r-- | docs/CommandGuide/analyze.html | 86 | ||||
| -rw-r--r-- | docs/CommandGuide/bugpoint.html | 249 | ||||
| -rw-r--r-- | docs/CommandGuide/extract.html | 93 | ||||
| -rw-r--r-- | docs/CommandGuide/gccas.html | 84 | ||||
| -rw-r--r-- | docs/CommandGuide/gccld.html | 210 | ||||
| -rw-r--r-- | docs/CommandGuide/llc.html | 220 | ||||
| -rw-r--r-- | docs/CommandGuide/lli.html | 107 | ||||
| -rw-r--r-- | docs/CommandGuide/llvm-as.html | 97 | ||||
| -rw-r--r-- | docs/CommandGuide/llvm-db.html | 26 | ||||
| -rw-r--r-- | docs/CommandGuide/llvm-dis.html | 94 | ||||
| -rw-r--r-- | docs/CommandGuide/llvm-link.html | 88 | ||||
| -rw-r--r-- | docs/CommandGuide/llvm-nm.html | 118 | ||||
| -rw-r--r-- | docs/CommandGuide/llvm-prof.html | 58 | ||||
| -rw-r--r-- | docs/CommandGuide/llvmgcc.html | 113 | ||||
| -rw-r--r-- | docs/CommandGuide/llvmgxx.html | 107 | ||||
| -rw-r--r-- | docs/CommandGuide/opt.html | 109 |
16 files changed, 0 insertions, 1859 deletions
diff --git a/docs/CommandGuide/analyze.html b/docs/CommandGuide/analyze.html deleted file mode 100644 index ff61808f2b..0000000000 --- a/docs/CommandGuide/analyze.html +++ /dev/null @@ -1,86 +0,0 @@ -<html> -<title> -LLVM: analyze tool -</title> - -<body bgcolor=white> - -<center><h1>LLVM: <tt>analyze</tt> tool</h1></center> -<HR> - -<h3>NAME</h3> -<tt>analyze</tt> - -<h3>SYNOPSIS</h3> -<tt>analyze [options] [filename]</tt> - -<h3>DESCRIPTION</h3> - -The <tt>analyze</tt> 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> -If filename is omitted or is -, <tt>analyze</tt> 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. - -<h3>OPTIONS</h3> - -<ul> - <li> -help - <br> - Print a summary of command line options. - <p> - - <li> -q - <br> - Quiet mode. With this option, analysis pass names are not printed. - <p> - - <li> -load <plugin> - <br> - Load the specified dynamic object with name <tt>plugin</tt>. This file - should contain additional analysis passes that register themselves with - the <tt>analyze</tt> program after being loaded. - <p> - - After being loaded, additional command line options are made available - for running the passes made available by <tt>plugin</tt>. Use - '<tt><tt>analyze</tt> -load <plugin> -help</tt>' to see the new - list of available analysis passes. - <p> - - <li> -profile-info-file <filename> - <br> - Specify the name of the file loaded by the -profile-loader option. - <p> - - <li> -stats - <br> - Print statistics. - <p> - - <li> -time-passes - <br> - Record the amount of time needed for each pass and print it to standard - error. - <p> -</ul> - -<h3>EXIT STATUS</h3> - -If <tt>analyze</tt> succeeds, it will exit with 0. Otherwise, if an error -occurs, it will exit with a non-zero value. - -<h3>SEE ALSO</h3> - -<a href="opt.html"><tt>opt</tt></a> - -<HR> -Maintained by the <a href="http://llvm.cs.uiuc.edu">LLVM Team</a>. -</body> -</html> - diff --git a/docs/CommandGuide/bugpoint.html b/docs/CommandGuide/bugpoint.html deleted file mode 100644 index 519e02d527..0000000000 --- a/docs/CommandGuide/bugpoint.html +++ /dev/null @@ -1,249 +0,0 @@ -<html> -<title>LLVM: bugpoint tool</title> - -<body bgcolor=white> - -<center><h1>LLVM: <tt>bugpoint</tt> tool</h1></center> -<HR> - -<h3>NAME</h3> -<tt>bugpoint</tt> - -<h3>SYNOPSIS</h3> -<tt>bugpoint [options] [input LLVM ll/bc files] [LLVM passes] --args <program arguments>...</tt> - -<img src="../img/Debugging.gif" width=444 height=314 align=right> -<h3>DESCRIPTION</h3> - -The <tt>bugpoint</tt> tool 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 <tt><a href="gccas.html">gccas</a></tt> 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> - -<a name="designphilosophy"> -<h4>Design Philosophy</h4> - -<tt>bugpoint</tt> 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. <tt>bugpoint</tt> 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 <tt>bugpoint</tt> is generally very quick unless -debugging a miscompilation where each test of the program (which requires -executing it) takes a long time.<p> - -<a name="automaticdebuggerselection"> -<h4>Automatic Debugger Selection</h4> - -<tt>bugpoint</tt> reads each <tt>.bc</tt> or <tt>.ll</tt> 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), -<tt>bugpoint</tt> starts the <a href="#crashdebug">crash debugger</a>.<p> - -Otherwise, if the <a href="#opt_output"><tt>-output</tt></a> option was not -specified, <tt>bugpoint</tt> runs the test program with the C backend (which is -assumed to generate good code) to generate a reference output. Once -<tt>bugpoint</tt> has a reference output for the test program, it tries -executing it with the <a href="#opt_run-">selected</a> code generator. If the -selected code generator crashes, <tt>bugpoint</tt> starts the <a -href="#crashdebug">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="#codegendebug">code generator debugger</a>.<p> - -Finally, if the output of the selected code generator matches the reference -output, <tt>bugpoint</tt> 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 <a href="#miscompilationdebug">miscompilation -debugger</a>. Otherwise, there is no problem <tt>bugpoint</tt> can debug.<p> - -<a name="crashdebug"> -<h4>Crash debugger</h4> - -If an optimizer or code generator crashes, <tt>bugpoint</tt> will try as hard as -it can to reduce the list of passes (for optimizer crashes) and the size of the -test program. First, <tt>bugpoint</tt> figures out which combination of -optimizer passes triggers the bug. This is useful when debugging a problem -exposed by <tt>gccas</tt>, for example, because it runs over 38 passes.<p> - -Next, <tt>bugpoint</tt> 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, -<tt>bugpoint</tt> deletes any individual LLVM instructions whose absence does -not eliminate the failure. At the end, <tt>bugpoint</tt> should tell you what -passes crash, give you a bytecode file, and give you instructions on how to -reproduce the failure with <tt><a href="opt.html">opt</a></tt>, <tt><a -href="analyze.html">analyze</a></tt>, or <tt><a href="llc.html">llc</a></tt>.<p> - -<a name="codegendebug"> -<h4>Code generator debugger</h4> - -<p>The code generator debugger attempts to narrow down the amount of code that -is being miscompiled by the <a href="#opt_run-">selected</a> 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 LLC compiler. 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> - -<a name="miscompilationdebug"> -<h4>Miscompilation debugger</h4> - -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> - -<a name="bugpoint notes"> -<h4>Advice for using <tt>bugpoint</tt></h4> - -<tt>bugpoint</tt> can be a remarkably useful tool, but it sometimes works in -non-obvious ways. Here are some hints and tips:<p> - -<ol> -<li>In the code generator and miscompilation debuggers, <tt>bugpoint</tt> only - works with programs that have deterministic output. Thus, if the program - outputs <tt>argv[0]</tt>, the date, time, or any other "random" data, <tt>bugpoint</tt> 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. - -<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. - -<li><tt>bugpoint</tt> is extremely useful when working on a new optimization: - it helps track down regressions quickly. To avoid having to relink - <tt>bugpoint</tt> every time you change your optimization however, have - <tt>bugpoint</tt> dynamically load your optimization with the <a - href="#opt_load"><tt>-load</tt></a> option. - -<li><tt>bugpoint</tt> 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:<br> - <tt>bugpoint ..... |& tee bugpoint.log</tt> - <br>to get a copy of <tt>bugpoint</tt>'s output in the file - <tt>bugpoint.log</tt>, as well as on your terminal. - -<li><tt>bugpoint</tt> cannot debug problems with the LLVM linker. If - <tt>bugpoint</tt> crashes before you see its "All input ok" message, - you might try <tt>llvm-link -v</tt> on the same set of input files. If - that also crashes, you may be experiencing a linker bug. - -<li>If your program is <b>supposed</b> to crash, <tt>bugpoint</tt> will be - confused. One way to deal with this is to cause bugpoint to ignore the exit - code from your program, by giving it the <tt>-check-exit-code=false</tt> - option. - -</ol> - -<h3>OPTIONS</h3> - -<ul> - <li><tt>-additional-so <library></tt><br> - Load <tt><library></tt> 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> - - <li><tt>-args <program args></tt><br> - Pass all arguments specified after <tt>-args</tt> to the - test program whenever it runs. Note that if any of - the <tt><program args></tt> start with a '-', you should use: - <p> - <tt>bugpoint <bugpoint args> -args -- <program args></tt> - <p> - The "<tt>--</tt>" right after the <tt>-args</tt> option tells - <tt>bugpoint</tt> to consider any options starting with <tt>-</tt> to be - part of the <tt>-args</tt> option, not as options to <tt>bugpoint</tt> - itself.<p> - - <li><tt>-tool-args <tool args></tt><br> - Pass all arguments specified after <tt>-tool-args</tt> to the - LLVM tool under test (llc, lli, etc.) whenever it runs. - You should use this option in the following way: - <p> - <tt>bugpoint <bugpoint args> -tool-args -- <tool args></tt> - <p> - The "<tt>--</tt>" right after the <tt>-tool-args</tt> option tells - <tt>bugpoint</tt> to consider any options starting with <tt>-</tt> to be - part of the <tt>-tool-args</tt> option, not as options to - <tt>bugpoint</tt> itself. (See <tt>-args</tt>, above.)<p> - - <li><tt>-check-exit-code={true,false}</tt><br> - Assume a non-zero exit code or core dump from the test program is - a failure. Defaults to true.<p> - - <li><tt>-disable-{dce,simplifycfg}</tt><br> - Do not run the specified passes to clean up and reduce the size of the - test program. By default, <tt>bugpoint</tt> uses these passes internally - when attempting to reduce test programs. If you're trying to find - a bug in one of these passes, <tt>bugpoint</tt> may crash.<p> - - <li> <tt>-help</tt><br> - Print a summary of command line options.<p> - - <a name="opt_input"><li><tt>-input <filename></tt><br> - Open <tt><filename></tt> and redirect the standard input of the - test program, whenever it runs, to come from that file. - <p> - - <a name="opt_load"><li> <tt>-load <plugin></tt><br> - Load the dynamic object <tt><plugin></tt> into <tt>bugpoint</tt> - 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 -help and -load options together: - <p> - <tt>bugpoint -load <plugin> -help</tt> - <p> - - <a name="opt_output"><li><tt>-output <filename></tt><br> - Whenever the test program produces output on its standard output - stream, it should match the contents of <tt><filename></tt> - (the "reference output"). If you do not use this option, - <tt>bugpoint</tt> will attempt to generate a reference output by - compiling the program with the C backend and running it.<p> - - <li><tt>-profile-info-file <filename></tt><br> - Profile file loaded by -profile-loader.<p> - - <a name="opt_run-"><li><tt>-run-{int,jit,llc,cbe}</tt><br> - Whenever the test program is compiled, <tt>bugpoint</tt> 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> -</ul> - -<h3>EXIT STATUS</h3> - -If <tt>bugpoint</tt> succeeds in finding a problem, it will exit with 0. -Otherwise, if an error occurs, it will exit with a non-zero value. - -<h3>SEE ALSO</h3> -<a href="opt.html"><tt>opt</tt></a>, -<a href="analyze.html"><tt>analyze</tt></a> - -<HR> -Maintained by the <a href="http://llvm.cs.uiuc.edu">LLVM Team</a>. -</body> -</html> diff --git a/docs/CommandGuide/extract.html b/docs/CommandGuide/extract.html deleted file mode 100644 index 72112e8b2d..0000000000 --- a/docs/CommandGuide/extract.html +++ /dev/null @@ -1,93 +0,0 @@ -<html> -<title> -LLVM: extract tool -</title> - -<body bgcolor=white> - -<center> -<h1>LLVM: <tt>extract</tt> tool</h1> -</center> -<HR> - -<h3>NAME</h3> -<tt>extract</tt> - -<h3> -SYNOPSIS -</h3> - -<tt>extract [options] [filename]</tt> -<h3> -DESCRIPTION -</h3> - -The <tt>extract</tt> 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> - -In addition to extracting the bytecode of the specified function, -<tt>extract</tt> will also remove unreachable global variables, prototypes, and -unused types. -<p> - -The <tt>extract</tt> command reads its input from standard input if filename is -omitted or if filename is -. The output is always written to standard output. - -<h3>OPTIONS</h3> - -<ul> -<ul> - <li> -f - <br> - Force overwrite. Normally, <tt>extract</tt> will refuse to overwrite an - output file that already exists. With this option, <tt>extract</tt> - will overwrite the output file and replace it with new bytecode. - <p> - - <li>-func <function> - <br> - Extract the specified function from the LLVM bytecode. - <p> - - <li> -help - <br> - Print a summary of command line options. - <p> - - <li> -o <filename> - <br> - Specify the output filename. If filename is "-" (the default), then - <tt>extract</tt> sends its output to standard output. - <p> - - <li> -stats - <br> - Print statistics. - <p> - - <li> -time-passes - <br> - Record the amount of time needed for each pass and print it to standard - error. - <p> -</ul> - -<h3> -EXIT STATUS -</h3> - -If <tt>extract</tt> succeeds, it will exit with 0. Otherwise, if an error -occurs, it will exit with a non-zero value. - -<h3> -SEE ALSO -</h3> -<a href="bugpoint.html"><tt>bugpoint</tt></a> - -<HR> -Maintained by the <a href="http://llvm.cs.uiuc.edu">LLVM Team</a>. -</body> -</html> - diff --git a/docs/CommandGuide/gccas.html b/docs/CommandGuide/gccas.html deleted file mode 100644 index 4c22a9934a..0000000000 --- a/docs/CommandGuide/gccas.html +++ /dev/null @@ -1,84 +0,0 @@ -<html> -<title>LLVM: gccas tool</title> - -<body bgcolor=white> - -<center> -<h1>LLVM: <tt>gccas</tt> tool</h1> -</center> -<HR> - -<h3>NAME</h3> -<tt>gccas</tt> - -<h3>SYNOPSIS</h3> -<tt>gccas [options] < filename></tt> - -<h3>DESCRIPTION</h3> - -The <tt>gccas</tt> utility takes an LLVM assembly file generated by the <a -href="llvmgcc.html">C</a> or <a href="llvmgxx.html">C++</a> frontends 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> - -<tt>gccas</tt> performs a number of optimizations on the input program.<p> - -<h3> -OPTIONS -</h3> - -<ul> - <li> -help - <br> - Print a summary of command line options. - <p> - - <li> -o <filename> - <br> - Specify the output filename which will hold the assembled bytecode. - <p> - - <li>-disable-inlining - <br> - Disable the inlining pass. By default, it is enabled. - <p> - - <li> -disable-opt - <br> - Disable all assemble-time optimization passes. - <p> - - <li> -stats - <br> - Print statistics. - <p> - - <li> -time-passes - <br> - Record the amount of time needed for each pass and print it to standard - error. - <p> - - <li> -verify - <br> - Verify each pass result. - <p> -</ul> - -<h3> -EXIT STATUS -</h3> - -If <tt>gccas</tt> succeeds, it will exit with 0. Otherwise, if an error occurs, -it will exit with a non-zero value. - -<h3>SEE ALSO</h3> -<a href="llvm-as.html"><tt>llvm-as</tt></a> -<a href="gccld.html"><tt>gccld</tt></a> - -<HR> -Maintained by the <a href="http://llvm.cs.uiuc.edu">LLVM Team</a>. -</body> -</html> - diff --git a/docs/CommandGuide/gccld.html b/docs/CommandGuide/gccld.html deleted file mode 100644 index 6ba4946515..0000000000 --- a/docs/CommandGuide/gccld.html +++ /dev/null @@ -1,210 +0,0 @@ -<html> -<title>LLVM: gccld tool</title> - -<body bgcolor=white> - -<center><h1>LLVM: <tt>gccld</tt> tool</h1></center> -<HR> - -<h3>NAME</h3> -<tt>gccld</tt> - -<h3>SYNOPSIS</h3> -<tt>gccld [options] < filename> [ filename ...]</tt> - -<h3>DESCRIPTION</h3> - -The <tt>gccld</tt> 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, <tt>gccld</tt> is able to produce native code executables. -<p> - -The <tt>gccld</tt> utility is primarily used by the <a href="llvmgcc.html">C</a> -and <a href="llvmgxx.html">C++</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> - -The <tt>gccld</tt> tool performs a small set of interprocedural, post-link, -optimizations on the program. - - -<h4>Search Order</h4> - -<p> -When looking for objects specified on the command line, <tt>gccld</tt> will -search for the object first in the current directory and then in the directory -specified by the <tt>LLVM_LIB_SEARCH_PATH</tt> environment variable. If it -cannot find the object, it fails. -</p> - -<p> -When looking for a library specified with the -l option, <tt>gccld</tt> first -attempts to load a file with that name from the current directory. If that -fails, it looks for lib<library>.bc, lib<library>.a, or -lib<library>.<shared library extension>, in that order, in each -directory added to the library search path with the -L option. These -directories are searched in the order they -were specified. If the library cannot be located, then <tt>gccld</tt> looks in -the directory specified by the <tt>LLVM_LIB_SEARCH_PATH</tt> environment -variable. If it does not find a library there, it fails. -</p> - -<p> -The shared library extension is usually <tt>.so</tt>, but it may differ -depending upon the system. -</p> - -<p> -The -L 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> - -<h4>Link order</h4> - -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. - -<h4>Library Linkage</h4> - -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. - -<h4>Native code generation</h4> - -The <tt>gccld</tt> program has limited support for native code generation, when -using the <tt>-native</tt> or <tt>-native-cbe</tt> options. - - -<h3>OPTIONS</h3> - -<ul> - <li> -help - <br> - Print a summary of command line options. - <p> - - <li> -o <filename> - <br> - Specify the output filename which will hold the linked bytecode. - <p> - - <li> -stats - <br> - Print statistics. - <p> - - <li> -time-passes - <br> - Record the amount of time needed for each pass and print it to standard - error. - <p> - - <li> -verify - <br> - Verify each pass result. - <p> - - <li> -disable-opt - <br> - Disable all link-time optimization passes. - <p> - - <li> -disable-inlining - <br> - Do not run the inliner pass. - <p> - - <li> -L=<directory> - <br> - Add directory to the list of directories to search when looking for - libraries. - <p> - - <li> -disable-internalize - <br> - Do not mark all symbols as internal. - <p> - - <li> -internalize-public-api-file <filename> - <br> - Preserve the list of symbol names in the file filename. - <p> - - <li> -internalize-public-api-list <list> - <br> - Preserve the symbol names in list. - <p> - - <li> -l=<library> - <br> - Specify libraries to include when linking the output file. When - linking, <tt>gccld</tt> will first attempt to load a file with the - pathname <tt>library</tt>. If that fails, it will then attempt to load - lib<library>.bc, lib<library>.a, and - lib<library>.<shared library extension>, in that order. - <p> - - <li> -link-as-library - <br> - Link the .bc files together as a library, not an executable. - <p> - - <li> -native - <br> - Generate a native, machine code executable. - <p> - When generating native executables, <tt>gccld</tt> first checks for a bytecode - version of the library and links it in, if necessary. If the library is - missing, <tt>gccld</tt> skips it. Then, <tt>gccld</tt> links in the same - libraries as native code. - <p> - In this way, <tt>gccld</tt> 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> - - <li> -native-cbe - <br> - Generate a native, machine code executable with the LLVM C backend. - <p> - This option is identical to the <tt>-native</tt> option, but uses the - C backend to generate code for the program instead of an LLVM native - code generator. - </p> - - <li> -s - <br> - Strip symbol information from the generated executable. - <p> - - <li> -v - <br> - Print information about actions taken. -</ul> - -<h3>EXIT STATUS</h3> - -If <tt>gccld</tt> succeeds, it will exit with 0. Otherwise, if an error occurs, -it will exit with a non-zero value. - -<h3>SEE ALSO</h3> -<a href="llvm-link.html"><tt>llvm-link</tt></a> -<a href="gccas.html"><tt>gccas</tt></a> - -<h3>BUGS</h3> -The -L option cannot be used for find native code libraries when using the --native option. - -<HR> -Maintained by the <a href="http://llvm.cs.uiuc.edu">LLVM Team</a>. -</body> -</html> - diff --git a/docs/CommandGuide/llc.html b/docs/CommandGuide/llc.html deleted file mode 100644 index 3a1efd1df1..0000000000 --- a/docs/CommandGuide/llc.html +++ /dev/null @@ -1,220 +0,0 @@ -<html> -<title>LLVM: llc tool</title> - -<body bgcolor=white> - -<center><h1>LLVM: <tt>llc</tt> tool</h1></center> -<HR> - -<h3>NAME</h3> -<tt>llc</tt> - -<h3>SYNOPSIS</h3> -<tt>llc [options] [filename]</tt> - -<h3>DESCRIPTION</h3> - -The <tt>llc</tt> 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> -The choice of architecture for the output assembly code is determined as -follows: - -<ul> - <li> - If the user has specified an architecture with the -m option, use that - architecture. - <p> - - <li> - Examine the input LLVM bytecode file: - <ul> - <li> - If it specifies little endian and a pointer size of 32 bits, select the - x86 architecture. - <p> - - <li> - If it specifies big endian and a pointer size of 64 bit pointers, - select the SparcV9 architecture. - </ul> - <p> - - <li> - If <tt>llc</tt> was compiled on an architecture for which it can - generate code, select the architecture upon which <tt>llc</tt> was - compiled. - <p> - - <li> - Print a message to the user asking him or her to specify the output - architecture explicitly. -</ul> - -<p> - -If filename is not specified, or if filename is -, <tt>llc</tt> reads its input -from standard input. Otherwise, it will read its input from filename. -<p> - -If the -o option is left unspecified, then <tt>llc</tt> will send its output to standard -output if the input is from standard input. If the -o option specifies -, then -the output will also be sent to standard output. -<p> - -If no -o option is specified and an input file other than - is specified, then -<tt>llc</tt> creates the output filename as follows: - -<ul> - <li> - If the file ends in .bc, then the .bc suffix is removed, and the .s suffix - is appended. - <p> - <li> - Otherwise, the .s suffix is appended to the input filename. -</ul> - -<h3> -OPTIONS -</h3> -<ul> - <li>-f - <br> - Overwrite output files - <p> - - <li>-m<arch> - <br> - Specify the architecture for which to generate assembly. Valid - architectures are: - - <dl compact> - <dt> x86 </dt> - <dd>IA-32 (Pentium and above)</dd> - - <dt> sparcv9 </dt> - <dd>SPARC V9</dd> - - <dt> c </dt> - <dd>Emit C code</dd> - </dl> - <p> - - <li>-o <filename> - <br> - Specify the output filename. - <p> - - <li>-enable-correct-eh-support - <br> - Instruct the -lowerinvoke pass to insert code for correct exception handling - support. This is expensive and is by default omitted for efficiency. - <p> - - <li> -help - <br> - Print a summary of command line options. - <p> - - <li> -stats - <br> - Print statistics. - <p> - - <li> -time-passes - <br> - Record the amount of time needed for each pass and print it to standard - error. - <p> - -</ul> -<h4>X86 Specific Options</h4> -<ul> - <li>-disable-fp-elim - <br> - Disable frame pointer elimination optimization. - <p> - - <li>-disable-pattern-isel - <br></ |