Retrieve the appropriate llvm-gcc4-x.y.source.tar.gz archive from the + llvm web site.
- -It is also possible to download the sources of the llvm-gcc4 front end + from a read-only mirror using subversion. To check out the code the + first time use:
--
-
-
-
-
Retrieve the appropriate llvm-gcc4-x.y.source.tar.gz archive from the llvm -web site.
-It is also possible to download the sources of the llvm-gcc4 front end from -a read-only mirror using subversion. To check out the code the first time use; -
- -svn co svn://anonsvn.opensource.apple.com/svn/llvm dst-directory - -After that, the code can be be updated in the destination directory using; -
- -svn update - -The mirror is brought up to date every evening.
-
- Configure and build the LLVM libraries and tools. There are two ways to -do this: either with objdir == srcdir or -objdir != srcdir. It is recommended -that srcdir be the same as objdir for your LLVM tree (but note -that you should always use srcdir != objdir for llvm-gcc):
--
-
- With objdir != srcdir:
- % cd objdir - % srcdir/configure --prefix=/some/path/you/can/install/to [options...] - % gmake tools-only -
- - With objdir == srcdir:
- % cd llvm - % ./configure --prefix=/some/path/you/can/install/to [options...] - % gmake tools-only -
-
This will build all of the LLVM tools and libraries. The --prefix -option defaults to /usr/local (per configure standards) but unless you are a -system administrator, you probably won't be able to install LLVM there because -of permissions. Specify a path into which LLVM can be installed (e.g. ---prefix=/home/user/llvm).
-
-
-- With objdir != srcdir:
Add the directory containing the tools to your PATH.
-- % set path = ( `cd llvm/Debug/bin && pwd` $path ) -
-
-Unpack the C/C++ front-end source into cfrontend/src, either by - untar'ing a cfrontend.source.tar.gz file or checking out CVS into this - directory.
-
-Make "build" and "install" directories as siblings of the "src" tree:
+-- % pwd - /usr/local/example/cfrontend/src - % cd .. - % mkdir build install - % set CFEINSTALL = `pwd`/install -
- - -Configure, build, and install the GCC front-end:
- --Linux/x86:
- -
-Linux/IA-64:
-MacOS X/PowerPC (requires dlcompat library):
-AIX/PowerPC: -- % cd build - % ../src/configure --prefix=$CFEINSTALL --disable-threads --disable-nls \ - --disable-shared --enable-languages=c,c++ --program-prefix=llvm- - % gmake all; gmake install +svn co svn://anonsvn.opensource.apple.com/svn/llvm/trunk dst-directory
+Cygwin/x86:
- -- % cd build - % ../src/configure --prefix=$CFEINSTALL --disable-threads --disable-nls \ - --disable-shared --enable-languages=c,c++ --disable-c-mbchar \ - --program-prefix=llvm- - % gmake all; gmake install -
- -Solaris/SPARC:
- --The GCC front-end can be configured for either SPARC V8 (32 bit) or SPARC V9 (64 -bit). This changes, among other things, the sizes of integer types and the -macros defined for conditional compilation. -
- --The SPARC V8 ABI support is more robust than the V9 ABI support and can generate -SPARC V9 code. It is highly recommended that you use the V8 ABI with LLVM, as -shown below. Also, -note that Solaris has trouble with various wide (multibyte) character -functions from C as referenced from C++, so we typically configure with ---disable-c-mbchar (cf. Bug 206). -
- -- % cd build - % ../src/configure --prefix=$CFEINSTALL --disable-threads --disable-nls \ - --disable-shared --enable-languages=c,c++ --host=sparc-sun-solaris2.8 \ - --disable-c-mbchar --program-prefix=llvm- - % gmake all; gmake install -
- -Common Problem: You may get error messages regarding the fact - that LLVM does not support inline assembly. Here are two common - fixes:
- --
-
Fix 1: If you have system header files that include - inline assembly, you may have to modify them to remove the inline - assembly and install the modified versions in -
$CFEINSTALL/lib/gcc/target-triplet/3.4-llvm/include.
-
- - Fix 2: If you are building the C++ front-end on a CPU we
- haven't tried yet, you will probably have to edit the appropriate
- version of atomicity.h under
-
src/libstdc++-v3/config/cpu/name-of-cpu/atomicity.h- and apply a patch so that it does not use inline assembly.
-
Porting to a new architecture: If you are porting the front-end - to a new architecture or compiling in a configuration that we have - not tried previously, there are probably several changes you will have to make - to the GCC target to get it to work correctly. These include:
- -
-
-
- Often targets include special assembler or linker flags which - gccas/gccld does not understand. In general, these can - just be removed. -
- LLVM currently does not support any floating point values other than - 32-bit and 64-bit IEEE floating point. The primary effect of this is - that you may have to map "long double" onto "double". -
- The profiling hooks in GCC do not apply at all to the LLVM front-end. - These may need to be disabled. -
- No inline assembly for position independent code. At the LLVM level, - everything is position independent. -
- We handle .init and .fini differently. -
- You may have to disable multilib support in your target. Using multilib - support causes the GCC compiler driver to add a lot of "-L" - options to the link line, which do not relate to LLVM and confuse - gccld. To disable multilibs, delete any - MULTILIB_OPTIONS lines from your target files. -
- Did we mention that we don't support inline assembly? You'll probably - have to add some fixinclude hacks to disable it in the system - headers. -
-
-Put $CFEINSTALL/bin into your PATH environment -variable.
--
-
- sh: export PATH=$CFEINSTALL/bin:$PATH -
- csh: setenv PATH $CFEINSTALL/bin:$PATH -
-
-Go back into the LLVM source tree proper. Rerun configure, using -the same options as the last time. This will cause the configuration to now find -the newly built llvm-gcc and llvm-g++ executables.
+ Rebuild your CVS tree. This shouldn't cause the whole thing to be - rebuilt, but it should build the runtime libraries. After the tree is - built, install the runtime libraries into your GCC front-end build tree. - These are the commands you need:
-- % gmake - % gmake -C runtime install-bytecode -
+Optionally, build a symbol table for the newly installed runtime -libraries. Although this step is optional, you are strongly encouraged to -do this as the symbol tables will make a significant difference in your -link times. Use the llvm-ranlib tool to do this, as follows:
-- % cd $CFEINSTALL/lib - % llvm-ranlib libiberty.a - % llvm-ranlib libstdc++.a - % llvm-ranlib libsupc++.a - % cd $CFEINSTALL/lib/gcc/target-triplet/3.4-llvm - % llvm-ranlib libgcc.a - % llvm-ranlib libgcov.a -
+The mirror is brought up to date every evening.
-Test the newly-installed C frontend by one or more of the -following means:
--
-
- running the feature & regression tests via make check -
- compiling and running a "hello, LLVM" program in C and C++. -
- running the tests found in the llvm-test CVS module -
+ - Follow the directions in the top-level README.LLVM file for + up-to-date instructions on how to build llvm-gcc4.
After that, the code can be be updated in the destination directory + using:
-svn update+
-The software also has the following additional copyrights: +More information is available in the FAQ.
- -- -Copyright (c) 2003, 2004, 2005 University of Illinois at Urbana-Champaign. -All rights reserved. - -Developed by: - - LLVM Team - - University of Illinois at Urbana-Champaign - - http://llvm.org - -THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR -IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS -FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE -CONTRIBUTORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER -LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, -OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS WITH THE -SOFTWARE. - -Copyright (c) 1994 -Hewlett-Packard Company - -Permission to use, copy, modify, distribute and sell this software -and its documentation for any purpose is hereby granted without fee, -provided that the above copyright notice appear in all copies and -that both that copyright notice and this permission notice appear -in supporting documentation. Hewlett-Packard Company makes no -representations about the suitability of this software for any -purpose. It is provided "as is" without express or implied warranty. - -Copyright (c) 1996, 1997, 1998, 1999 -Silicon Graphics Computer Systems, Inc. - -Permission to use, copy, modify, distribute and sell this software -and its documentation for any purpose is hereby granted without fee, -provided that the above copyright notice appear in all copies and -that both that copyright notice and this permission notice appear -in supporting documentation. Silicon Graphics makes no -representations about the suitability of this software for any -purpose. It is provided "as is" without express or implied warranty. -
LLVM Compiler Infrastructure
Last modified: $Date$