X-Git-Url: http://plrg.eecs.uci.edu/git/?a=blobdiff_plain;f=docs%2FGettingStarted.html;h=e740a89b01d07baa8ec3607179595ebacb7697d9;hb=9ea9fcdf654b9a54a072a3e28cb2091b6c84cf1c;hp=0dd29d9bf3edc2199a8038fdf5bea33da1d13849;hpb=ccd029507e7d6edd93b22189c9276a8cf26ac8d8;p=oota-llvm.git diff --git a/docs/GettingStarted.html b/docs/GettingStarted.html index 0dd29d9bf3e..e740a89b01d 100644 --- a/docs/GettingStarted.html +++ b/docs/GettingStarted.html @@ -159,7 +159,8 @@ 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.
Enable the SPEC2000 benchmarks for testing. The SPEC2000 benchmarks should be available in @@ -214,11 +215,21 @@ software you will need.
LLVM has partial support for the following platforms:
@@ -307,11 +313,7 @@ upNote that you will need about 1-3 GB of space for a full LLVM build in Debug mode, depending on the system (it is so large because of all the debugging information and the fact that the libraries are statically linked into multiple -tools). If you do not need many of the tools and you are space-conscious, -you can disable them individually in llvm/tools/Makefile. The Release -build requires considerably less space.
+tools). If you do not need many of the tools and you are space-conscious, you +can pass ONLY_TOOLS="tools you need" to make. The Release build +requires considerably less space.The LLVM suite may compile on other platforms, but it is not guaranteed to do so. If compilation is successful, the LLVM utilities should be @@ -375,18 +382,6 @@ href="GCCFEBuildInstrs.html">try to compile it on your platform.
GCC 4.1.2 20071124 (Red Hat 4.1.2-42): Suffers from the same symptoms as the previous one. It appears to work with ENABLE_OPTIMIZED=0 (the default).
- +Cygwin GCC 4.3.2 20080827 (beta) 2: + Users reported various problems related + with link errors when using this GCC version.
+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.
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 @@ -572,6 +572,12 @@ href="http://sourceware.org/bugzilla/show_bug.cgi?id=3111">a bug which causes huge link times (minutes instead of seconds) when building LLVM. We recommend upgrading to a newer version (2.17.50.0.4 or later).
+GNU Binutils 2.19.1 Gold: This version of Gold contained +a bug +which causes intermittent failures when building LLVM with position independent +code. The symptom is an error about cyclic dependencies. We recommend +upgrading to a newer version of Gold.
+ @@ -696,7 +702,7 @@ compressed with the gzip program.If you have access to our Subversion repository, you can get a fresh copy of -the entire source code. All you need to do is check it out from Subvresion as +the entire source code. All you need to do is check it out from Subversion as follows:
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:
-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 +
It is possible to cross-compile LLVM itself. That is, you can create LLVM + executables and libraries to be hosted on a platform different from the + platform where they are build (a Canadian Cross build). To configure a + cross-compile, 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.
+ +The result of such a build is executables that are not runnable on + on the build host (--build option) but can be executed on the compile host (--host option).
-Notes:
-This section gives an example of using LLVM. llvm-gcc3 is now obsolete, -so we only include instructiosn for llvm-gcc4. +so we only include instructions for llvm-gcc4.
Note: The gcc4 frontend's invocation is considerably different