1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
4 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
5 <link rel="stylesheet" href="llvm.css" type="text/css" media="screen" />
6 <title>Bootstrapping the C/C++ Front-End</title>
10 <div class="doc_title">
11 Bootstrapping the C/C++ Front-End
14 <p>This document is intended to explain the process of building the LLVM
15 C/C++ front-end, based on GCC 3.4, from source.</p>
17 <p><b>NOTE:</b> This is currently a somewhat fragile, error-prone
18 process, and you should only try to do it if
20 <li>(A) you really, really, really can't use the binaries we distribute
21 <li>(B) you need GCC to fix some of the header files on your system
22 <li>(C) you are an elite GCC hacker.</p>
25 <p>We welcome patches to help make this process simpler.</p>
27 <!-- *********************************************************************** -->
28 <div class="doc_section">
29 <a name="instructions">Instructions</a>
31 <!-- *********************************************************************** -->
33 <div class="doc_text">
36 <li><p>Configure and build the LLVM libraries and tools using:</p>
39 % ./configure [options...]
42 <p>The use of the non-default target "tools-only" means that the
43 LLVM tools and libraries will build, and the binaries will be
44 deposited in llvm/tools/Debug, but the runtime (bytecode)
45 libraries will not build.</p></li>
47 <li><p>Add the directory containing the tools to your PATH.</p>
49 % set path = ( `cd llvm/tools/Debug && pwd` $path )
52 <li><p>Unpack the C/C++ front-end source into cfrontend/src.</p></li>
54 <li><p>Edit src/configure. Change the first line (starting w/ #!) to
55 contain the correct full pathname of sh.</p></li>
57 <li><p>Make "build" and "install" directories as siblings of the "src"
61 /usr/local/example/cfrontend/src
64 % set CFEINSTALL = `pwd`/install
67 <li><p>Configure, build and install the C front-end:</p>
70 % ../src/configure --prefix=$CFEINSTALL --disable-nls --disable-shared \
71 --enable-languages=c,c++
73 % setenv LLVM_LIB_SEARCH_PATH `pwd`/gcc
74 % gmake all; gmake install
77 <p><b>Common Problem:</b> You may get error messages regarding the fact
78 that LLVM does not support inline assembly. Here are two common
82 <li><p><b>Fix 1:</b> If you have system header files that include
83 inline assembly, you may have to modify them to remove the inline
84 assembly, and install the modified versions in
85 <code>$CFEINSTALL/<i>target-triplet</i>/sys-include</code>.</p></li>
87 <li><b>Fix 2:</b> If you are building the C++ front-end on a CPU we
88 haven't tried yet, you will probably have to edit the appropriate
89 version of atomicity.h under
90 <code>src/libstdc++-v3/config/cpu/<i>name-of-cpu</i>/atomicity.h</code>
91 and apply a patch so that it does not use inline assembly.</p></li>
94 <p><b>Porting to a new architecture:</b> If you are porting the new front-end
95 to a new architecture, or compiling in a different configuration that we have
96 previously, there are probably several changes you will have to make to the GCC
97 target to get it to work correctly. These include:<p>
100 <li>Often targets include special or assembler linker flags which
101 <tt>gccas</tt>/<tt>gccld</tt> does not understand. In general, these can
102 just be removed.</li>
103 <li>LLVM currently does not support any floating point values other than
104 32-bit and 64-bit IEEE floating point. The primary effect of this is
105 that you may have to map "long double" onto "double".</li>
106 <li>The profiling hooks in GCC do not apply at all to the LLVM front-end.
107 These may need to be disabled.</li>
108 <li>No inline assembly for position independent code. At the LLVM level,
109 everything is position independent.</li>
110 <li>We handle <tt>.init</tt> and <tt>.fini</tt> differently.</li>
111 <li>You may have to disable multilib support in your target. Using multilib
112 support causes the GCC compiler driver to add a lot of "<tt>-L</tt>"
113 options to the link line, which do not relate to LLVM and confuse
114 <tt>gccld</tt>. To disable multilibs, delete any
115 <tt>MULTILIB_OPTIONS</tt> lines from your target files.</li>
116 <li>Did we mention that we don't support inline assembly? You'll probably
117 have to add some fixinclude hacks to disable it in the system
122 <li><p>Go back into the LLVM source tree proper. Edit Makefile.config
123 to redefine <code>LLVMGCCDIR</code> to the full pathname of the
124 <code>$CFEINSTALL</code> directory, which is the directory you just
125 installed the C front-end into. (The ./configure script is likely to
126 have set this to a directory which does not exist on your system.)</p></li>
128 <li><p>If you edited header files during the C/C++ front-end build as
129 described in "Fix 1" above, you must now copy those header files from
130 <code>$CFEINSTALL/<i>target-triplet</i>/sys-include</code> to
131 <code>$CFEINSTALL/lib/gcc/<i>target-triplet</i>/3.4-llvm/include</code>.
132 (This should be the "include" directory in the same directory as the
133 libgcc.a library, which you can find by running
134 <code>$CFEINSTALL/bin/gcc --print-libgcc-file-name</code>.)</p></li>
136 <li><p>Build and install the runtime (bytecode) libraries by running:</p>
139 % mkdir $CFEINSTALL/bytecode-libs
140 % gmake -C runtime install
141 % setenv LLVM_LIB_SEARCH_PATH $CFEINSTALL/bytecode-libs
144 <li><p>Test the newly-installed C frontend by one or more of the
147 <li> compiling and running a "hello, LLVM" program in C and C++.</li>
148 <li> running the tests under <tt>test/Programs</tt> using <code>gmake -C
149 test/Programs</code></li>
156 <!-- *********************************************************************** -->
159 <address><a href="mailto:gaeke -at- uiuc.edu">Brian Gaeke</a></address>
160 <a href="http://llvm.cs.uiuc.edu">The LLVM Compiler Infrastructure</a>
162 Last modified: $Date$