X-Git-Url: http://demsky.eecs.uci.edu/git/?a=blobdiff_plain;f=docs%2FGettingStarted.html;h=69510e85be6c434986a7727a03db23219426c323;hb=a75ce9f5d2236d93c117e861e60e6f3f748c9555;hp=c27101e27b7ca25562dc30c58f8c99e349eac1df;hpb=18df1d4eb400581dcb504975473efb7cbba1ead4;p=oota-llvm.git diff --git a/docs/GettingStarted.html b/docs/GettingStarted.html index c27101e27b7..69510e85be6 100644 --- a/docs/GettingStarted.html +++ b/docs/GettingStarted.html @@ -44,10 +44,9 @@
  • llvm/projects
  • llvm/runtime
  • llvm/test
    • -
  • llvm-test
    • +
  • test-suite
  • llvm/tools
  • llvm/utils
    • -
  • llvm/win32
  • An Example Using the LLVM Tool Chain @@ -80,11 +79,12 @@

    Welcome to LLVM! In order to get started, you first need to know some 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, bitcode -analyzer and bitcode optimizer. It also contains a test suite that can be -used to test the LLVM tools and the GCC front end.

    +

    First, LLVM comes in three 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, bitcode analyzer and bitcode optimizer. It +also contains basic regression tests 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 bitcode. Currently, the GCC front @@ -93,7 +93,7 @@ compiled into LLVM bitcode, a program can be manipulated with the LLVM tools from the LLVM suite.

    -There is a third, optional piece called llvm-test. It is a suite of programs +There is a third, optional piece called Test Suite. It is a suite of programs with a testing harness that can be used to further test LLVM's functionality and performance.

    @@ -142,6 +142,7 @@ and performance.
  • cd where-you-want-llvm-to-live
  • cd llvm/projects
  • gunzip --stdout llvm-test-version.tar.gz | tar -xvf - +
  • mv llvm-test-version test-suite
    • @@ -162,7 +163,7 @@ and performance.

    Optionally, specify for directory the full pathname of the C/C++ front end installation to use with this LLVM configuration. If not specified, the PATH will be searched. This is only needed if you - want to run the testsuite or do some special kinds of LLVM builds.

    + want to run test-suite or do some special kinds of LLVM builds.

  • --enable-spec2000=directory

    Enable the SPEC2000 benchmarks for testing. The SPEC2000 benchmarks should be available in @@ -242,6 +243,11 @@ software you will need.

    x861 GCC + + FreeBSD + amd64 + GCC + MacOS X2 PowerPC @@ -256,13 +262,13 @@ software you will need.

    Cygwin/Win32 x861,8, 11 - GCC 3.4.X, binutils 2.15 + GCC 3.4.X, binutils 2.20 MinGW/Win32 x861,6, 8, 10 - GCC 3.4.X, binutils 2.15 + GCC 3.4.X, binutils 2.20 @@ -318,12 +324,8 @@ up
  • The GCC-based C/C++ frontend does not build
  • The port is done using the MSYS shell.
  • Native code generation exists but is not complete.
    • -
  • 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. We highly recommend that you rebuild your current binutils with the - patch from - Binutils bugzilla, if it wasn't already applied.
    • +
  • Binutils 2.20 or later is required to build the assembler + generated by LLVM properly.
  • XCode 2.5 and gcc 4.0.1 (Apple Build 5370) will trip internal LLVM assert messages when compiled for Release at optimization levels greater than 0 (i.e., "-O1" and higher). @@ -456,8 +458,8 @@ href="GCCFEBuildInstrs.html">try to compile it on your platform.

  • Only needed if you want to run the automated test suite in the llvm/test directory.
  • If you want to make changes to the configure scripts, - you will need GNU autoconf (2.59), and consequently, GNU M4 (version 1.4 - or higher). You will also need automake (1.9.2). We only use aclocal + you will need GNU autoconf (2.60), and consequently, GNU M4 (version 1.4 + or higher). You will also need automake (1.9.6). We only use aclocal from that package.
    • @@ -568,6 +570,9 @@ as the previous one. It appears to work with ENABLE_OPTIMIZED=0 (the default).GCC 4.3.3 (Debian 4.3.3-10) on ARM: Miscompiles parts of LLVM 2.6 when optimizations are turned on. The symptom is an infinite loop in FoldingSetImpl::RemoveNode while running the code generator.

    +

    GCC 4.3.5 and GCC 4.4.5 on ARM: These can miscompile value >> +1 even at -O0. A test failure in test/Assembler/alignstack.ll is +one symptom of the problem.

    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 @@ -688,7 +693,7 @@ compressed with the gzip program.

    Source release for the LLVM libraries and tools.
    llvm-test-x.y.tar.gz
    -
    Source release for the LLVM test suite.
    +
    Source release for the LLVM test-suite.
    llvm-gcc-4.2-x.y.source.tar.gz
    Source release of the llvm-gcc-4.2 front end. See README.LLVM in the root @@ -730,6 +735,8 @@ revision), you can checkout it from the 'tags' directory (instead of subdirectories of the 'tags' directory: