X-Git-Url: http://demsky.eecs.uci.edu/git/?a=blobdiff_plain;f=docs%2FGettingStarted.html;h=0e871336deb83ca2aa1345113c8439ded797076a;hb=1d33bb310865528f5b1a303e33891366457bc0ef;hp=9f6ef59b7fda3f08a9fd019012c511a76f9ffba6;hpb=6947e55aff7086d3ad654d4fa1ea9f51f4983424;p=oota-llvm.git diff --git a/docs/GettingStarted.html b/docs/GettingStarted.html index 9f6ef59b7fd..0e871336deb 100644 --- a/docs/GettingStarted.html +++ b/docs/GettingStarted.html @@ -31,6 +31,7 @@
  • Install the GCC Front End
  • Local LLVM Configuration
  • Compiling the LLVM Suite Source Code +
  • Cross-Compiling LLVM
  • The Location of LLVM Object Files
  • Optional Configuration Items
    • @@ -51,6 +52,9 @@
  • An Example Using the LLVM Tool Chain +
      +
    1. Example with llvm-gcc4
      2. +
  • Common Problems
  • Links @@ -80,12 +84,12 @@ basic information.

    First, LLVM comes in two pieces. The first piece is the LLVM suite. This contains all of the tools, libraries, and header files needed to use the low level virtual machine. It contains an assembler, disassembler, bytecode -analyzer, and bytecode optimizer. It also contains a test suite that can be +analyzer and bytecode optimizer. It also contains a test suite that can be used to test the LLVM tools and the GCC front end.

    The second piece is the GCC front end. This component provides a version of GCC that compiles C and C++ code into LLVM bytecode. Currently, the GCC front -end is a modified version of GCC 3.4 (we track the GCC 3.4 development). Once +end uses the GCC parser to convert code to LLVM. Once compiled into LLVM bytecode, a program can be manipulated with the LLVM tools from the LLVM suite.

    @@ -114,11 +118,11 @@ and performance.
  • Install the GCC front end if you intend to compile C or C++:
    1. cd where-you-want-the-C-front-end-to-live
      2. -
    2. gunzip --stdout cfrontend.platform.tar.gz | tar -xvf - +
    3. gunzip --stdout llvm-gcc.platform.tar.gz | tar -xvf -
      4. -
    4. cd cfrontend/platform
      +
    5. cd llvm-gcc3.4/platform (llvm-gcc3.4 only)
      ./fixheaders
      6. -
    6. Add the cfrontend's "bin" directory to your PATH variable.
      7. +
    7. Add llvm-gcc's "bin" directory to your PATH variable.
  • Get the LLVM Source Code @@ -169,7 +173,8 @@ and performance.
    1. gmake -k |& tee gnumake.out    # this is csh or tcsh syntax
      2. -
    2. If you get an "internal compiler error (ICE)" see below.
      3. +
    3. If you get an "internal compiler error (ICE)" or test failures, see + below.
    @@ -205,7 +210,7 @@ software you will need.

    LLVM is known to work on the following platforms:

    - +
    @@ -256,7 +261,7 @@ software you will need.

    LLVM has partial support for the following platforms:

    -
    OS Arch
    +
    @@ -304,17 +309,18 @@ up
  • No native code generation
  • Build is not complete: one or more tools don't link
  • The GCC-based C/C++ frontend does not build
    • -
  • The port is done using the MSYS shell. +
  • The port is done using the MSYS shell. Download and install bison (excl. M4.exe) and flex in that order. Build binutils-2.15 from source, -if necessary. Bison & flex can be also grabbed from GNUWin32 sf.net project
    • +if necessary. Bison & flex can be also grabbed from GNUWin32 sf.net +project.
  • Native code generation exists but is not complete.
    • -
  • Binutils up to post-2.17 has bug in bfd/cofflink.c +
  • Binutils up to post-2.17 has bug in bfd/cofflink.c preventing LLVM from building correctly. Several workarounds have been introduced into LLVM build system, but the bug can occur anytime in the - future. It's highly recommended to rebuild your current binutils with the + future. We highly recommend that you rebuild your current binutils with the patch from - Binutils bugzilla, if it's wasn't already applied.
    • + Binutils bugzilla, if it wasn't already applied. @@ -345,7 +351,7 @@ href="CFEBuildInstrs.html">try to compile it on your platform.

    is the usual name for the software package that LLVM depends on. The Version column provides "known to work" versions of the package. The Notes column describes how LLVM uses the package and provides other details.

    -
    OS Arch
    +
    @@ -437,7 +443,7 @@ href="CFEBuildInstrs.html">try to compile it on your platform.

    Notes:

      -
    1. Only the C and C++ languages are needed so there's no +
    2. Only the C and C++ languages are needed so there's no need to build the other languages for LLVM's purposes. See below for specific version info.
    3. You only need CVS if you intend to build from the @@ -519,11 +525,27 @@ the "convert_from_eh_region_ranges_1" GCC function.

      possibly others) does not compile LLVM correctly (it appears that exception handling is broken in some cases). Please download the FSF 3.3.3 or upgrade to a newer version of GCC.

      +

      GCC 3.4.x on X86-64/amd64: GCC + miscompiles portions of LLVM.

      IA-64 GCC 4.0.0: The IA-64 version of GCC 4.0.0 is known to miscompile LLVM.

      Apple Xcode 2.3: GCC crashes when compiling LLVM at -O3 (which is the default with ENABLE_OPTIMIZED=1. To work around this, build with "ENABLE_OPTIMIZED=1 OPTIMIZE_OPTION=-O2".

      +

      GCC 4.1.1: GCC fails to build LLVM with template concept check errors + compiling some files. At the time of this writing, GCC mainline (4.2) + did not share the problem.

      +

      GCC 4.1.1 on X86-64/amd64: GCC + miscompiles portions of LLVM when compiling llvm itself into 64-bit + code. LLVM will appear to mostly work but will be buggy, e.g. failing + portions of its testsuite.

      +

      GCC 4.1.2 on OpenSUSE: Seg faults during libstdc++ build and on x86_64 +platforms compiling md5.c gets a mangled constant.

      +

      GNU ld 2.16.X. Some 2.16.X versions of the ld linker will produce very +long warning messages complaining that some ".gnu.linkonce.t.*" symbol was +defined in a discarded section. You can safely ignore these messages as they are +erroneous and the linkage is correct. These messages disappear using ld +2.17.

    @@ -564,21 +586,21 @@ All these paths are absolute:

    SRC_ROOT
    This is the top level directory of the LLVM source tree. -

    +

    OBJ_ROOT
    This is the top level directory of the LLVM object tree (i.e. the tree where object files and compiled programs will be placed. It can be the same as SRC_ROOT). -

    +

    LLVMGCCDIR
    This is where the LLVM GCC Front End is installed.

    For the pre-built GCC front end binaries, the LLVMGCCDIR is - cfrontend/platform/llvm-gcc. + llvm-gcc/platform/llvm-gcc. @@ -629,26 +651,18 @@ compressed with the gzip program.

    llvm-test-x.y.tar.gz
    Source release for the LLVM test suite.
    -
    cfrontend-x.y.source.tar.gz
    -
    Source release of the GCC front end.
    - -
    cfrontend-x.y.i686-redhat-linux-gnu.tar.gz
    -
    Binary release of the GCC front end for Linux/x86.
    -
    llvm-gcc4-x.y.source.tar.gz
    Source release of the llvm-gcc4 front end. See README.LLVM in the root directory for build instructions.
    -
    llvm-gcc4-x.y.powerpc-apple-darwin8.6.0.tar.gz
    -
    Binary release of the llvm-gcc4 front end for MacOS X/PowerPC.
    +
    llvm-gcc4-x.y-platform.tar.gz
    +
    Binary release of the llvm-gcc4 front end for a specific platform.
    -
    llvm-gcc4-x.y.i686-apple-darwin8.6.1.tar.gz
    -
    Binary release of the llvm-gcc4 front end for MacOS X/X86.
    -

    It is also possible to download the sources of the llvm-gcc4 front end from -a read-only subversion mirror at svn://anonsvn.opensource.apple.com/svn/llvm. -

    +

    It is also possible to download the sources of the llvm-gcc4 front end from a +read-only subversion mirror at +svn://anonsvn.opensource.apple.com/svn/llvm/trunk.

    @@ -665,9 +679,9 @@ follows:

    @@ -680,6 +694,8 @@ revision), you can specify a label. The following releases have the following labels:

      +
    • Release 1.9: RELEASE_19
      • +
    • Release 1.8: RELEASE_18
    • Release 1.7: RELEASE_17
    • Release 1.6: RELEASE_16
    • Release 1.5: RELEASE_15
      • @@ -694,20 +710,15 @@ labels:

      you get it from the CVS repository:

         cd llvm/projects
-  cvs -z3 -d :pserver:anon@llvm-cvs.cs.uiuc.edu:/var/cvs/llvm co llvm-test
+  cvs -z3 -d :pserver:anon@llvm.org:/var/cvs/llvm co llvm-test

      By placing it in the llvm/projects, it will be automatically configured by the LLVM configure script as well as automatically updated when you run cvs update.

      -

      If you would like to get the GCC 3.4 front end source code, you can also get it from the CVS repository:

      - -
      -  cvs -z3 -d :pserver:anon@llvm-cvs.cs.uiuc.edu:/var/cvs/llvm co llvm-gcc
-
      - -

      Please note that you must follow these -instructions to successfully build the LLVM GCC front-end.

      +

      If you would like to get the GCC front end source code, you can also get it +and build it yourself. Please follow these +instructions to successfully get and build the LLVM GCC front-end.

      @@ -718,23 +729,27 @@ instructions to successfully build the LLVM GCC front-end.

      -

      Before configuring and compiling the LLVM suite, you need to extract the LLVM -GCC front end from the binary distribution. It is used for building the -bytecode libraries later used by the GCC front end for linking programs, and its -location must be specified when the LLVM suite is configured.

      +

      Before configuring and compiling the LLVM suite, you can optionally extract the +LLVM GCC front end from the binary distribution. It is used for running the +llvm-test testsuite and for compiling C/C++ programs. Note that you can optionally +build llvm-gcc yourself after building the +main LLVM repository.

      To install the GCC front end, do the following:

      1. cd where-you-want-the-front-end-to-live
        2. -
      2. gunzip --stdout cfrontend-version.platform.tar.gz | tar -xvf +
      3. gunzip --stdout llvmgcc-version.platform.tar.gz | tar -xvf -
      -

      Next, you will need to fix your system header files:

      - -

      cd cfrontend/platform
      - ./fixheaders

      +

      Once the binary is uncompressed, you should add a symlink for llvm-gcc and +llvm-g++ to some directory in your path. When you configure LLVM, it will +automatically detect llvm-gcc's presence (if it is in your path) enabling its +use in llvm-test. Note that you can always build or install llvm-gcc at any +pointer after building the main LLVM repository: just reconfigure llvm and +llvm-test will pick it up. +

      The binary versions of the GCC front end may not suit all of your needs. For example, the binary distribution may include an old version of a system header @@ -743,7 +758,7 @@ linked with libraries not available on your system.

      In cases like these, you may want to try building the GCC front end from source. This is -not for the faint of heart, so be forewarned.

      +much easier now than it was in the past.

      @@ -763,7 +778,7 @@ the Makefiles needed to begin building LLVM.

      The following environment variables are used by the configure script to configure the build system:

      -
    PackageVersionNotes
    +
    @@ -805,14 +820,14 @@ script to configure the build system:

    dejagnu based test suite in llvm/test. If you don't specify this option, the LLVM configure script will search for the tcl 8.4 and 8.3 releases. -

    +

    --enable-optimized
    Enables optimized compilation by default (debugging symbols are removed and GCC optimization flags are enabled). The default is to use an unoptimized build (also known as a debug build). -

    +

    --enable-debug-runtime
    @@ -825,7 +840,7 @@ script to configure the build system:

    available on all platforms. The default is dependent on platform, so it is best to explicitly enable it if you want it. -

    +

    --enable-targets=target-option
    Controls which targets will be built and linked into llc. The default @@ -836,12 +851,17 @@ script to configure the build system:

    separated list of target names that you want available in llc. The target names use all lower case. The current set of targets is:
    alpha, ia64, powerpc, skeleton, sparc, x86. -

    +

    --enable-doxygen
    Look for the doxygen program and enable construction of doxygen based documentation from the source code. This is disabled by default because generating the documentation can take a long time and producess 100s of megabytes of output.
    +
    --with-udis86
    +
    LLVM can use external disassembler library for various purposes (now it's + used only for examining code produced by JIT). This option will enable usage + of udis86 x86 (both 32 and 64 + bits) disassembler library.

    To configure LLVM, follow these steps:

    @@ -850,12 +870,12 @@ script to configure the build system:

  • Change directory into the object root directory:
    cd OBJ_ROOT -

    +

  • Run the configure script located in the LLVM source tree:
    SRC_ROOT/configure --prefix=/install/path [other options] -

    +

    @@ -877,7 +897,7 @@ builds:

    --enable-optimized option was used during configuration). The build system will compile the tools and libraries with debugging information. -

    +

    Release (Optimized) Builds
    @@ -886,7 +906,7 @@ builds:

    gmake command line. For these builds, the build system will compile the tools and libraries with GCC optimizations enabled and strip debugging information from the libraries and executables it generates. -

    +

    Profile Builds
    @@ -919,14 +939,14 @@ source code:

    Removes all files generated by the build. This includes object files, generated C/C++ files, libraries, and executables. -

    +

    gmake dist-clean
    Removes everything that gmake clean does, but also removes files generated by configure. It attempts to return the source tree to the original state in which it was shipped. -

    +

    gmake install
    @@ -934,15 +954,15 @@ source code:

    hierarchy under $PREFIX, specified with ./configure --prefix=[dir], which defaults to /usr/local. -

    - +

    +

    gmake -C runtime install-bytecode
    Assuming you built LLVM into $OBJDIR, when this command is run, it will install bytecode libraries into the GCC front end's bytecode library directory. If you need to update your bytecode libraries, this is the target to use once you've built them. -

    +

    Please see the Makefile Guide for further @@ -956,27 +976,27 @@ declaring variables on the command line. The following are some examples:

    gmake ENABLE_OPTIMIZED=1
    Perform a Release (Optimized) build. -

    +

    gmake ENABLE_OPTIMIZED=1 DISABLE_ASSERTIONS=1
    Perform a Release (Optimized) build without assertions enabled. -

    +

    gmake ENABLE_PROFILING=1
    Perform a Profiling build. -

    +

    gmake VERBOSE=1
    Print what gmake is doing on standard output. -

    +

    gmake TOOL_VERBOSE=1
    Ask each tool invoked by the makefiles to print out what it is doing on the standard output. This also implies VERBOSE=1. -

    +

    Every directory in the LLVM object tree includes a Makefile to build @@ -986,6 +1006,51 @@ that directory that is out of date.

    + +
    + Cross-Compiling LLVM +
    + +
    +

    It is possible to cross-compile LLVM. That is, you can create LLVM + executables and libraries for a platform different than the one one which you + are compiling. To do this, a few additional steps are + required. 1 To cross-compile LLVM, use + these instructions:

    +
      +
    1. Configure and build LLVM as a native compiler. You will need + just TableGen from that build. +
        +
      • If you have $LLVM_OBJ_ROOT=$LLVM_SRC_ROOT just execute + make -C utils/TableGen after configuring.
        • +
      • Otherwise you will need to monitor building process and terminate + it just after TableGen was built.
        • +
      +
      2. +
    2. Copy the TableGen binary to somewhere safe (out of your build tree). +
      3. +
    3. Configure LLVM to build with a cross-compiler. To do this, supply the + configure script with --build and --host options that + are different. The values of these options must be legal target triples + that your GCC compiler supports.
      4. +
    4. Put the saved TableGen executable into the + into $LLVM_OBJ_ROOT/{BUILD_TYPE}/bin directory (e.g. into + .../Release/bin for a Release build).
      5. +
    5. Build LLVM as usual.
      6. +
    +

    The result of such a build will produce executables that are not executable + on your build host (--build option) but can be executed on your compile host + (--host option).

    +

    Notes:

    +
    +
      +
    1. Cross-compiling was tested only with Linux as + build platform and Windows as host using mingw32 cross-compiler. Other + combinations have not been tested.
      2. +
    +
    +
    +
    The Location of LLVM Object Files @@ -1022,7 +1087,7 @@ named after the build type:

    Libraries
    OBJ_ROOT/Debug/lib -

    +

    Release Builds
    @@ -1032,7 +1097,7 @@ named after the build type:

    Libraries
    OBJ_ROOT/Release/lib -

    +

    Profile Builds
    @@ -1252,11 +1317,6 @@ following is a brief introduction to the most important tools. More detailed information is in the Command Guide.

    -
    analyze
    -
    analyze is used to run a specific - analysis on an input LLVM bytecode file and print out the results. It is - primarily useful for debugging analyses, or familiarizing yourself with - what an analysis does.
    bugpoint
    bugpoint is used to debug @@ -1290,11 +1350,10 @@ information is in the Command Guide.

    LLVM assembly.
    llvm-ld
    -
    llvm-ld is very similar to gccld and provides a general purpose - and extensible linker for LLVM. This is the linker invoked by llvmc. - It allows optimization modules to be loaded so that language specific - optimizations can be applied at link time. This tool is considered - experimental.
    +
    llvm-ld is a general purpose and extensible linker for LLVM. + This is the linker invoked by llvmc. It performsn standard link time + optimizations and allows optimization modules to be loaded and run so that + language specific optimizations can be applied at link time.
    llvm-link
    llvm-link, not surprisingly, links multiple LLVM modules into @@ -1316,43 +1375,22 @@ information is in the Command Guide.

    the -march=c option).
    llvm-gcc
    -
    llvm-gcc is a GCC-based C frontend - that has been retargeted to emit LLVM code as the machine code output. It - works just like any other GCC compiler, taking the typical -c, -S, -E, - -o options that are typically used. The source code for the - llvm-gcc tool is available as a separate CVS module. -
    -
    -
    gccas
    -
    This tool is invoked by the llvm-gcc frontend as the - "assembler" part of the compiler. This tool actually assembles LLVM - assembly to LLVM bytecode, performs a variety of optimizations, and - outputs LLVM bytecode. Thus when you invoke - llvm-gcc -c x.c -o x.o, you are causing gccas to be - run, which writes the x.o file (which is an LLVM bytecode file - that can be disassembled or manipulated just like any other bytecode - file). The command line interface to gccas is designed to be - as close as possible to the system `as' utility so that - the gcc frontend itself did not have to be modified to interface to - a "weird" assembler.
    - -
    gccld
    -
    gccld links together several LLVM bytecode files into one - bytecode file and does some optimization. It is the linker invoked by - the GCC frontend when multiple .o files need to be linked together. - Like gccas, the command line interface of gccld is - designed to match the system linker, to aid interfacing with the GCC - frontend.
    -
    -
    -
    +
    llvm-gcc is a GCC-based C frontend that has been retargeted to + use LLVM as its backend instead of GCC's RTL backend. It can also emit LLVM + byte code or assembly (with the -emit-llvm option) instead of the + usual machine code output. It works just like any other GCC compiler, + taking the typical -c, -S, -E, -o options that are typically used. + Additionally, the the source code for llvm-gcc is available as a + separate CVS module.
    opt
    -
    opt reads LLVM bytecode, applies a - series of LLVM to LLVM transformations (which are specified on the command - line), and then outputs the resultant bytecode. The 'opt --help' - command is a good way to get a list of the program transformations - available in LLVM.
    +
    opt reads LLVM bytecode, applies a series of LLVM to LLVM + transformations (which are specified on the command line), and then outputs + the resultant bytecode. The 'opt --help' command is a good way to + get a list of the program transformations available in LLVM.
    +
    opt can also be used to run a specific analysis on an input + LLVM bytecode file and print out the results. It is primarily useful for + debugging analyses, or familiarizing yourself with what an analysis does.
    @@ -1369,7 +1407,7 @@ are code generators for parts of LLVM infrastructure.

    that finds differences between code that LLC generates and code that LLI generates. This is a useful tool if you are debugging one of them, assuming that the other generates correct output. For the full user - manual, run `perldoc codegen-diff'.

    + manual, run `perldoc codegen-diff'.

    cvsupdate
    cvsupdate is a script that will update your CVS tree, but produce a much cleaner and more organized output @@ -1377,21 +1415,21 @@ are code generators for parts of LLVM infrastructure.

    together all the new and updated files and modified files in separate sections, so you can see at a glance what has changed. If you are at the top of your LLVM CVS tree, running utils/cvsupdate is the - preferred way of updating the tree.

    + preferred way of updating the tree.

    emacs/
    The emacs directory contains syntax-highlighting files which will work with Emacs and XEmacs editors, providing syntax highlighting support for LLVM assembly files and TableGen description files. For information on how to use the syntax files, consult - the README file in that directory.

    + the README file in that directory.

    getsrcs.sh
    The getsrcs.sh script finds and outputs all non-generated source files, which is useful if one wishes to do a lot of development across directories and does not want to individually find each file. One way to use it is to run, for example: xemacs `utils/getsources.sh` from the top of your LLVM source - tree.

    - + tree.

    +

    llvmgrep
    This little tool performs an "egrep -H -n" on each source file in LLVM and passes to it a regular expression provided on llvmgrep's command @@ -1404,24 +1442,24 @@ are code generators for parts of LLVM infrastructure.

    llvm/lib/Target/Sparc, if makellvm is in your path, simply running makellvm llc will make a build of the current directory, switch to directory llvm/tools/llc and build it, - causing a re-linking of LLC.

    + causing a re-linking of LLC.

    NightlyTest.pl and NightlyTestTemplate.html
    These files are used in a cron script to generate nightly status reports of the functionality of tools, and the results can be seen by following the appropriate link on - the LLVM homepage.

    + the LLVM homepage.

    TableGen/
    The TableGen directory contains the tool used to generate register descriptions, instruction set descriptions, and even assemblers from common TableGen description - files.

    + files.

    vim/
    The vim directory contains syntax-highlighting files which will work with the VIM editor, providing syntax highlighting support for LLVM assembly files and TableGen description files. For information on how to use the syntax files, consult - the README file in that directory.

    + the README file in that directory.

    @@ -1442,6 +1480,22 @@ are code generators for parts of LLVM infrastructure.

    +
    +

    This section gives an example of using LLVM. llvm-gcc3 is now obsolete, +so we only include instructiosn for llvm-gcc4. +

    + +

    Note: The gcc4 frontend's invocation is considerably different +from the previous gcc3 frontend. In particular, the gcc4 frontend does not +create bytecode by default: gcc4 produces native code. As the example below illustrates, +the '--emit-llvm' flag is needed to produce LLVM bytecode output. For makefiles and +configure scripts, the CFLAGS variable needs '--emit-llvm' to produce bytecode +output.

    +
    + + +
    Example with llvm-gcc4
    +
      @@ -1454,33 +1508,40 @@ are code generators for parts of LLVM infrastructure.

      } -

    1. Next, compile the C file into a LLVM bytecode file:

      +

    2. Next, compile the C file into a native executable:

      +

      % llvm-gcc hello.c -o hello

      -

      Note that you should have already built the tools and they have to be - in your path, at least gccas and gccld.

      +

      Note that llvm-gcc works just like GCC by default. The standard -S and + -c arguments work as usual (producing a native .s or .o file, + respectively).

      -

      This will create two result files: hello and - hello.bc. The hello.bc is the LLVM bytecode that - corresponds the the compiled program and the library facilities that it - required. hello is a simple shell script that runs the bytecode - file with lli, making the result directly executable. Note that - all LLVM optimizations are enabled by default, so there is no need for a - "-O3" switch.

      3. +

    3. Next, compile the C file into a LLVM bytecode file:

      +

      % llvm-gcc -O3 -emit-llvm hello.c -c -o hello.bc

      + +

      The -emit-llvm option can be used with the -S or -c options to emit an + LLVM ".ll" or ".bc" file (respectively) for the code. This allows you + to use the standard LLVM tools on + the bytecode file.

      + +

      Unlike llvm-gcc3, llvm-gcc4 correctly responds to -O[0123] arguments. +

      4. -

    4. Run the program. To make sure the program ran, execute one of the - following commands:

      +

    5. Run the program in both forms. To run the program, use:

      % ./hello

      -

      or

      +

      and

      -

      % lli hello.bc

      6. +

      % lli hello.bc

      + +

      The second examples shows how to invoke the LLVM JIT, lli.

    6. Use the llvm-dis utility to take a look at the LLVM assembly code:

      -

      % llvm-dis < hello.bc | less

      7. +

      % llvm-dis < hello.bc | less

    7. Compile the program to native assembly using the LLC code generator:

      @@ -1494,12 +1555,17 @@ are code generators for parts of LLVM infrastructure.

    8. Execute the native code program:

      -

      % ./hello.native

      9. +

      % ./hello.native

      + +

      Note that using llvm-gcc to compile directly to native code (i.e. when + the -emit-llvm option is not present) does steps 6/7/8 for you.

      +
    +
    Common Problems
    • VariablePurpose
    CC