From 537a02c582517a80506c3c4eea3fc42ef3cc43a6 Mon Sep 17 00:00:00 2001 From: Chris Lattner Date: Tue, 7 Oct 2003 20:01:09 +0000 Subject: [PATCH] More changes and updates git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@8935 91177308-0d34-0410-b5e6-96231b3b80d8 --- docs/CommandGuide/gccas.html | 43 +++++----- docs/CommandGuide/gccld.html | 138 ++++++++++++++++----------------- docs/CommandGuide/llvmgxx.html | 58 ++++++-------- 3 files changed, 108 insertions(+), 131 deletions(-) diff --git a/docs/CommandGuide/gccas.html b/docs/CommandGuide/gccas.html index 39d764c2c7a..c0a5a7462d2 100644 --- a/docs/CommandGuide/gccas.html +++ b/docs/CommandGuide/gccas.html @@ -1,34 +1,28 @@ - -LLVM: gccas tool - +LLVM: gccas tool
-

LLVM: gccas tool

+

LLVM: gccas tool

-

-NAME -

+

NAME

+gccas -gccas +

SYNOPSIS

+gccas [options] < filename> -

-SYNOPSIS -

+

DESCRIPTION

-gccas [options] < filename> -

-DESCRIPTION -

+The gccas utility takes an LLVM assembly file generated by the C or C++ 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.

-The gccas utility takes an LLVM assembly file generated by GCC 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. +gccas performs a number of optimizations on the input program.

OPTIONS @@ -66,13 +60,12 @@ OPTIONS EXIT STATUS

-If gccas succeeds, it will exit with 0. Otherwise, if an error occurs, it -will exit with a non-zero value. +If gccas succeeds, it will exit with 0. Otherwise, if an error occurs, +it will exit with a non-zero value. -

-SEE ALSO -

-llvm-dis +

SEE ALSO

+llvm-as +gccld
LLVM Team diff --git a/docs/CommandGuide/gccld.html b/docs/CommandGuide/gccld.html index 6eef165db69..27ed3fe7d73 100644 --- a/docs/CommandGuide/gccld.html +++ b/docs/CommandGuide/gccld.html @@ -1,69 +1,64 @@ - -LLVM: gccld tool - +LLVM: gccld tool - + -
-

LLVM: gccld tool

-
+

LLVM: gccld tool

-

-NAME -

+

NAME

+gccld -gccld +

SYNOPSIS

+gccld [options] < filename> [ filename ...] -

-SYNOPSIS -

+

DESCRIPTION

-gccld [options] < filename> [ filename ...] -

-DESCRIPTION -

- -The gccld 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, -gccld is able to produce native code executables. +The gccld 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, gccld is able to produce native code executables.

-The gccld utility is primarily used by the GCC front end, and as such, attempts -to mimic the interface provided by the default system linker so that it can act -as a "drop-in" replacement. -

-Search Order -

-When looking for objects specified on the command line, gccld will search for -the object first in the current directory and then in the directory specified -by LLVM_LIB_SEARCH_PATH. If it cannot find the object, it fails. +The gccld utility is primarily used by the C +and C++ 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.

-When looking for a library specified with the -l option, gccld 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 + +The gccld tool performs a small set of interprocedural, post-link, +optimizations on the program. + + +

Search Order

+ +When looking for objects specified on the command line, gccld will +search for the object first in the current directory and then in the directory +specified by the LLVM_LIB_SEARCH_PATH environment variable. If it +cannot find the object, it fails. +

+ +When looking for a library specified with the -l option, gccld 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>.so, in that order, in each directory added to the library search path with the -L option. These directories are searched in order they -were specified. If the library cannot be located, then gccld looks in the -directory specified by the LLVM_LIB_SEARCH_PATH environment variable. If it -does not find lib<library>.[bc | a | so] there, it fails. +were specified. If the library cannot be located, then gccld looks in +the directory specified by the LLVM_LIB_SEARCH_PATH environment +variable. If it does not find lib<library>.[bc | a | so] there, it fails. 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. -

-Link order -

+

Link order

+ 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. -

-Library Linkage -

+

Library Linkage

+ 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 @@ -71,13 +66,13 @@ 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. -

-Native code generation -

-The gccld program has limited support for native code generation. -

-OPTIONS -

+

Native code generation

+ +The gccld program has limited support for native code generation, when +using the -native option. + + +

OPTIONS

-

-EXIT STATUS -

+

EXIT STATUS

-If gccld succeeds, it will exit with 0. Otherwise, if an error occurs, it -will exit with a non-zero value. +If gccld succeeds, it will exit with 0. Otherwise, if an error occurs, +it will exit with a non-zero value. -

-SEE ALSO -

-gccas +

SEE ALSO

+llvm-link +gccas -

-BUGS -

+

BUGS

The -L option cannot be used for find native code libraries when using the -native option. diff --git a/docs/CommandGuide/llvmgxx.html b/docs/CommandGuide/llvmgxx.html index bc71411a1ce..90eb9d293e0 100644 --- a/docs/CommandGuide/llvmgxx.html +++ b/docs/CommandGuide/llvmgxx.html @@ -6,37 +6,30 @@ LLVM: llvmg++ tool
-

LLVM: llvmg++ tool

+

LLVM: llvmg++ tool

-

-NAME -

+

NAME

+llvmg++ -llvmg++ +

SYNOPSIS

+llvmg++ [options] filename -

-SYNOPSIS -

+

DESCRIPTION

-llvmg++ [options] filename -

-DESCRIPTION -

- -The llvmg++ 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. +The llvmg++ 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.

-The llvmg++ program uses the LLVM assembler gccas and the LLVM linker gccld to -do the work of creating complete programs. +The llvmg++ program uses the gccas and gccld to +assist with the creation of complete programs.

-Being derived from the GNU Compiler Collection, llvmg++ 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. +Being derived from the GNU Compiler Collection, +llvmg++ 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.

Below you will find several commonly used options: @@ -54,15 +47,14 @@ OPTIONS

  • -c
    - 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. + 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.

  • -o filename
    - Specify the output file to be filename. If filename is -, - then llvmgcc sends its output to standard output. + Specify the output file to be filename.

  • -I directory @@ -79,8 +71,8 @@ OPTIONS
  • -lname
    - Link in the library libname.[bc | a | so]. This library should be - a bytecode library. + Link in the library libname.[bc | a | so]. This library should + be a bytecode library.

  • -Wl,option @@ -94,15 +86,15 @@ OPTIONS EXIT STATUS -If llvmg++ succeeds, it will exit with 0. Otherwise, if an error occurs, it -will exit with a non-zero value. +If llvmg++ succeeds, it will exit with 0. Otherwise, if an error +occurs, it will exit with a non-zero value.

    SEE ALSO

    -llvmg++, -gccas, -gccld +llvmg++, +gccas, +gccld
    LLVM Team