diff --git a/docs/GettingStarted.html b/docs/GettingStarted.html index 904b3900d50..0abf28180f8 100644 --- a/docs/GettingStarted.html +++ b/docs/GettingStarted.html @@ -119,8 +119,7 @@ and performance.
  • cd where-you-want-the-C-front-end-to-live
  • gunzip --stdout llvm-gcc.platform.tar.gz | tar -xvf -
    • - +
  • Note: If the binary extension is ".bz" use bunzip2 instead of gunzip.
  • Add llvm-gcc's "bin" directory to your PATH variable.
    • @@ -320,10 +319,10 @@ project. future. We highly recommend that you rebuild your current binutils with the patch from Binutils bugzilla, if it wasn't already applied. -
  • XCode 2.5 and gcc 4.0.1 (Apple Build 5370) will trip +
  • 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). - Add OPTIMIZE_OPTION="-O0" to the build command line + levels greater than 0 (i.e., "-O1" and higher). + Add OPTIMIZE_OPTION="-O0" to the build command line if compiling for LLVM Release or bootstrapping the LLVM toolchain.
    • @@ -556,6 +555,10 @@ the "convert_from_eh_region_ranges_1" GCC function.

    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.

    +

    GCC 4.1.2 (20061115 (prerelease) (Debian 4.1.1-21)) on Debian: Appears +to miscompile parts of LLVM 2.4. One symptom is ValueSymbolTable complaining +about symbols remaining in the table on destruction.

    +

    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 @@ -712,6 +715,7 @@ revision), you can checkout it from the 'tags' directory (instead of subdirectories of the 'tags' directory: