Gitiles
Code Review Sign In
gerrit-public.fairphone.software / fp2-dev / platform / external / llvm / f4ea921cc70ce3c8c75cce90af4b672c7f81c7b2 / . / docs / CFEBuildInstrs.html
blob: c71d68b5358d7e73359c692b6591c998d507c705 [file] [log] [blame]
Misha Brukman6a2b3102004-05-12 18:49:47 +0000[diff] [blame]1<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
2 "http://www.w3.org/TR/html4/strict.dtd">
Misha Brukman83bd33a2003-10-23 01:48:33 +0000[diff] [blame]3<html>
4<head>
Misha Brukman6a2b3102004-05-12 18:49:47 +0000[diff] [blame]5 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
6 <link rel="stylesheet" href="llvm.css" type="text/css" media="screen">
Misha Brukmanb9e57892003-10-28 21:09:29 +0000[diff] [blame]7 <title>Bootstrapping the LLVM C/C++ Front-End</title>
Misha Brukman83bd33a2003-10-23 01:48:33 +0000[diff] [blame]8</head>
9<body>
Brian Gaeke46079d22003-10-21 21:58:38 +0000[diff] [blame]10
Misha Brukman83bd33a2003-10-23 01:48:33 +0000[diff] [blame]11<div class="doc_title">
Misha Brukmanb9e57892003-10-28 21:09:29 +0000[diff] [blame]12 Bootstrapping the LLVM C/C++ Front-End
Misha Brukman83bd33a2003-10-23 01:48:33 +0000[diff] [blame]13</div>
Brian Gaeke46079d22003-10-21 21:58:38 +0000[diff] [blame]14
Brian Gaeke7af03e92003-11-12 20:47:30 +0000[diff] [blame]15<ol>
16 <li><a href="#cautionarynote">A Cautionary Note</a>
Chris Lattner6a615ad2004-06-01 18:13:05 +0000[diff] [blame]17 <ul>
Misha Brukman62a93432004-06-18 15:54:54 +0000[diff] [blame]18 <li><a href="#cygwin">Building under Cygwin</a></li>
Misha Brukman03ea9d42004-08-23 17:54:45 +0000[diff] [blame]19 <li><a href="#aix">Building under AIX</a></li>
Chris Lattner6a615ad2004-06-01 18:13:05 +0000[diff] [blame]20 </ul>
21 </li>
22 <li><a href="#instructions">Instructions</a></li>
23 <li><a href="#license">License Information</a></li>
Brian Gaeke7af03e92003-11-12 20:47:30 +0000[diff] [blame]24</ol>
25
Chris Lattner7911ce22004-05-23 21:07:27 +0000[diff] [blame]26<div class="doc_author">
Chris Lattner6a615ad2004-06-01 18:13:05 +0000[diff] [blame]27 <p>Written by Brian R. Gaeke and
28 <a href="http://nondot.org/sabre">Chris Lattner</a></p>
Brian Gaeke7af03e92003-11-12 20:47:30 +0000[diff] [blame]29</div>
30
31<!-- *********************************************************************** -->
32<div class="doc_section">
33 <a name="cautionarynote">A Cautionary Note</a>
34</div>
35<!-- *********************************************************************** -->
36
37<div class="doc_text">
38<p>This document is intended to explain the process of building the
39LLVM C/C++ front-end, based on GCC 3.4, from its source code. You
40would have to do this, for example, if you are porting LLVM to a new
41architecture or operating system.</p>
Brian Gaeke46079d22003-10-21 21:58:38 +0000[diff] [blame]42
43<p><b>NOTE:</b> This is currently a somewhat fragile, error-prone
Misha Brukmanb9e57892003-10-28 21:09:29 +0000[diff] [blame]44process, and you should <b>only</b> try to do it if:</p>
45
46<ol>
47 <li>you really, really, really can't use the binaries we distribute</li>
Misha Brukmanb9e57892003-10-28 21:09:29 +0000[diff] [blame]48 <li>you are an elite GCC hacker.</li>
Chris Lattnerc8118e12005-02-21 16:35:31 +0000[diff] [blame]49 <li>you want to use the latest bits from CVS.</li>
Misha Brukmanb9e57892003-10-28 21:09:29 +0000[diff] [blame]50</ol>
Brian Gaeke46079d22003-10-21 21:58:38 +0000[diff] [blame]51
52<p>We welcome patches to help make this process simpler.</p>
Brian Gaeke7af03e92003-11-12 20:47:30 +0000[diff] [blame]53</div>
Brian Gaeke46079d22003-10-21 21:58:38 +0000[diff] [blame]54
Chris Lattner6a615ad2004-06-01 18:13:05 +0000[diff] [blame]55<!--=========================================================================-->
56<div class="doc_subsection">
Misha Brukman62a93432004-06-18 15:54:54 +0000[diff] [blame]57 <a name="cygwin">Building under Cygwin</a>
Chris Lattner6a615ad2004-06-01 18:13:05 +0000[diff] [blame]58</div>
59<!--=========================================================================-->
60
61<div class="doc_text">
John Criswell9e2485c2004-12-10 15:51:16 +0000[diff] [blame]62<p>If you are building LLVM and the GCC front-end under Cygwin, please note that
Chris Lattner6a615ad2004-06-01 18:13:05 +0000[diff] [blame]63the LLVM and GCC makefiles do not correctly handle spaces in paths. To deal
64with this issue, make sure that your LLVM and GCC source and build trees are
65located in a top-level directory (like <tt>/cygdrive/c/llvm</tt> and
66<tt>/cygdrive/c/llvm-cfrontend</tt>), not in a directory that contains a space
67(which includes your "home directory", because it lives under the "Documents
68and Settings" directory). We welcome patches to fix this issue.
69</p>
Reid Spencer24042362004-12-22 09:52:30 +0000[diff] [blame]70<p>It has been found that the GCC 3.3.3 compiler provided with recent Cygwin
John Criswelld6c6ee02005-10-24 16:37:24 +0000[diff] [blame]71versions is incapable of compiling the LLVM GCC front-end correctly. If your
72Cygwin
John Criswelld0c4a762005-05-13 20:38:44 +0000[diff] [blame]73installation includes GCC 3.3.3, we <i>strongly</i> recommend that you download
John Criswelld6c6ee02005-10-24 16:37:24 +0000[diff] [blame]74GCC 3.4.3, build it separately, and use it for compiling the LLVM GCC front-end. This has been
Reid Spencer24042362004-12-22 09:52:30 +0000[diff] [blame]75shown to work correctly.</p>
Reid Spencer72a59002004-12-23 19:49:54 +0000[diff] [blame]76<p>Some versions of Cygwin utilize an experimental version of GNU binutils that
77will cause the GNU <tt>ld</tt> linker to fail an assertion when linking
78components of the libstdc++. It is recommended that you replace the entire
79binutils package with version 2.15 such that "<tt>ld --version</tt>" responds
Misha Brukman00b95c32005-03-01 17:19:21 +0000[diff] [blame]80with</p>
Reid Spencer72a59002004-12-23 19:49:54 +0000[diff] [blame]81<pre>GNU ld version 2.15</pre>
82not with:<br/>
83<pre>GNU ld version 2.15.91 20040725</pre>
Misha Brukman00b95c32005-03-01 17:19:21 +0000[diff] [blame]84</div>
Chris Lattner6a615ad2004-06-01 18:13:05 +0000[diff] [blame]85
Misha Brukman03ea9d42004-08-23 17:54:45 +0000[diff] [blame]86<!--=========================================================================-->
Reid Spencere0a7ddd2004-12-31 19:48:59 +0000[diff] [blame]87<div class="doc_subsection"><a name="aix">Building under AIX</a></div>
Misha Brukman03ea9d42004-08-23 17:54:45 +0000[diff] [blame]88<div class="doc_text">
John Criswell9e2485c2004-12-10 15:51:16 +0000[diff] [blame]89<p>If you are building LLVM and the GCC front-end under AIX, do NOT use GNU
Misha Brukman03ea9d42004-08-23 17:54:45 +0000[diff] [blame]90Binutils. They are not stable under AIX and may produce incorrect and/or
91invalid code. Instead, use the system assembler and linker.
92</p>
93</div>
94
Misha Brukman83bd33a2003-10-23 01:48:33 +0000[diff] [blame]95<!-- *********************************************************************** -->
96<div class="doc_section">
97 <a name="instructions">Instructions</a>
98</div>
99<!-- *********************************************************************** -->
100
101<div class="doc_text">
102<p>
Brian Gaeke46079d22003-10-21 21:58:38 +0000[diff] [blame]103<ol>
Jim Laskeye9493d32006-06-16 23:34:49 +0000[diff] [blame]104<li>
105<p>Retrieve the appropriate llvm-gcc4-x.y.source.tar.gz archive from the llvm
106web site.</p>
107<p>It is also possible to download the sources of the llvm-gcc4 front end from
108a read-only mirror using subversion. To check out the code the first time use;
109</p>
110
111<tt>svn co svn://anonsvn.opensource.apple.com/svn/llvm <i>dst-directory</i></tt>
112
113<p>After that, the code can be be updated in the destination directory using;
114</p>
115
116<tt>svn update</tt>
117
118<p>The mirror is brought up to date every evening.</p>
119</li>
Reid Spencere0a7ddd2004-12-31 19:48:59 +0000[diff] [blame]120<li><p>Configure and build the LLVM libraries and tools. There are two ways to
John Criswelld0c4a762005-05-13 20:38:44 +0000[diff] [blame]121do this: either with <i>objdir</i> == <i>srcdir</i> or
122<i>objdir</i> != <i>srcdir</i>. It is recommended
Chris Lattnere9967142005-09-21 03:56:26 +0000[diff] [blame]123that <i>srcdir</i> be the same as <i>objdir</i> for your LLVM tree (but note
124that you should always use <i>srcdir</i> != <i>objdir</i> for llvm-gcc):</p>
Reid Spencere0a7ddd2004-12-31 19:48:59 +0000[diff] [blame]125<ul>
126 <li>With <i>objdir</i> != <i>srcdir</i>:<pre>
127 % cd <i>objdir</i>
128 % <i>srcdir</i>/configure --prefix=/some/path/you/can/install/to [options...]
129 % gmake tools-only
130 </pre></li>
131 <li>With <i>objdir</i> == <i>srcdir</i>:<pre>
Brian Gaeke46079d22003-10-21 21:58:38 +0000[diff] [blame]132 % cd llvm
Reid Spencer0b4f4682004-12-01 05:15:44 +0000[diff] [blame]133 % ./configure --prefix=/some/path/you/can/install/to [options...]
Misha Brukmane7490532004-08-14 22:13:33 +0000[diff] [blame]134 % gmake tools-only
Reid Spencere0a7ddd2004-12-31 19:48:59 +0000[diff] [blame]135 </pre></li>
136</ul>
137<p>This will build all of the LLVM tools and libraries. The <tt>--prefix</tt>
138option defaults to /usr/local (per configure standards) but unless you are a
139system administrator, you probably won't be able to install LLVM there because
140of permissions. Specify a path into which LLVM can be installed (e.g.
141<tt>--prefix=/home/user/llvm</tt>).</p>
Reid Spencer0b4f4682004-12-01 05:15:44 +0000[diff] [blame]142</li>
Brian Gaeke46079d22003-10-21 21:58:38 +0000[diff] [blame]143
144<li><p>Add the directory containing the tools to your PATH.</p>
145<pre>
John Criswellc7f42642004-12-01 14:12:30 +0000[diff] [blame]146 % set path = ( `cd llvm/Debug/bin &amp;&amp; pwd` $path )
Misha Brukman83bd33a2003-10-23 01:48:33 +0000[diff] [blame]147</pre></li>
Brian Gaeke46079d22003-10-21 21:58:38 +0000[diff] [blame]148
Chris Lattnerb1241b02005-02-11 21:17:26 +0000[diff] [blame]149<li><p>Unpack the C/C++ front-end source into cfrontend/src, either by
John Criswell8bfe6a72005-05-18 19:43:33 +0000[diff] [blame]150 untar'ing a cfrontend.source.tar.gz file or checking out CVS into this
Chris Lattnerb1241b02005-02-11 21:17:26 +0000[diff] [blame]151 directory.</p></li>
Brian Gaeke46079d22003-10-21 21:58:38 +0000[diff] [blame]152
John Criswelld0c4a762005-05-13 20:38:44 +0000[diff] [blame]153<li><p>Make "build" and "install" directories as siblings of the "src" tree:</p>
Brian Gaeke46079d22003-10-21 21:58:38 +0000[diff] [blame]154<pre>
155 % pwd
156 /usr/local/example/cfrontend/src
157 % cd ..
158 % mkdir build install
159 % set CFEINSTALL = `pwd`/install
Misha Brukman83bd33a2003-10-23 01:48:33 +0000[diff] [blame]160</pre></li>
Brian Gaeke46079d22003-10-21 21:58:38 +0000[diff] [blame]161
Chris Lattner6a615ad2004-06-01 18:13:05 +0000[diff] [blame]162
John Criswell9e2485c2004-12-10 15:51:16 +0000[diff] [blame]163<li><p>Configure, build, and install the GCC front-end:</p>
John Criswell55072842003-12-08 19:59:14 +0000[diff] [blame]164
165<p>
Misha Brukman31b24322004-06-21 14:00:44 +0000[diff] [blame]166<b>Linux/x86:</b><br>
Duraid Madina0203a312005-06-14 07:29:50 +0000[diff] [blame]167<b>Linux/IA-64:</b><br>
Misha Brukmana964fe52004-08-09 18:37:04 +0000[diff] [blame]168<b>MacOS X/PowerPC</b> (requires dlcompat library):<br>
169<b>AIX/PowerPC:</b>
John Criswell55072842003-12-08 19:59:14 +0000[diff] [blame]170</p>
171
Brian Gaeke46079d22003-10-21 21:58:38 +0000[diff] [blame]172<pre>
173 % cd build
Misha Brukmana964fe52004-08-09 18:37:04 +0000[diff] [blame]174 % ../src/configure --prefix=$CFEINSTALL --disable-threads --disable-nls \
Reid Spencer4ac306502004-12-22 06:40:29 +0000[diff] [blame]175 --disable-shared --enable-languages=c,c++ --program-prefix=llvm-
Brian Gaeke46079d22003-10-21 21:58:38 +0000[diff] [blame]176 % gmake all; gmake install
177</pre>
178
Misha Brukman62a93432004-06-18 15:54:54 +0000[diff] [blame]179<p><b>Cygwin/x86:</b></p>
Chris Lattner893c26a2004-06-02 19:27:50 +0000[diff] [blame]180
181<pre>
182 % cd build
Misha Brukmana964fe52004-08-09 18:37:04 +0000[diff] [blame]183 % ../src/configure --prefix=$CFEINSTALL --disable-threads --disable-nls \
Reid Spencer4ac306502004-12-22 06:40:29 +0000[diff] [blame]184 --disable-shared --enable-languages=c,c++ --disable-c-mbchar \
185 --program-prefix=llvm-
Chris Lattner893c26a2004-06-02 19:27:50 +0000[diff] [blame]186 % gmake all; gmake install
187</pre>
188
189<p><b>Solaris/SPARC:</b></p>
John Criswell55072842003-12-08 19:59:14 +0000[diff] [blame]190
191<p>
John Criswellaf94d582005-05-13 20:54:44 +0000[diff] [blame]192The GCC front-end can be configured for either SPARC V8 (32 bit) or SPARC V9 (64
193bit). This changes, among other things, the sizes of integer types and the
194macros defined for conditional compilation.
195</p>
196
197<p>
Chris Lattner23c5b3c2006-02-05 06:44:17 +0000[diff] [blame]198The SPARC V8 ABI support is more robust than the V9 ABI support and can generate
199SPARC V9 code. It is highly recommended that you use the V8 ABI with LLVM, as
200shown below. Also,
Brian Gaeke7e9bd802004-01-28 20:54:41 +0000[diff] [blame]201note that Solaris has trouble with various wide (multibyte) character
202functions from C as referenced from C++, so we typically configure with
Reid Spencer05fe4b02006-03-14 05:39:39 +0000[diff] [blame]203--disable-c-mbchar (cf. <a href="http://llvm.org/PR206">Bug 206</a>).
John Criswell55072842003-12-08 19:59:14 +0000[diff] [blame]204</p>
205
206<pre>
207 % cd build
Brian Gaeke7e9bd802004-01-28 20:54:41 +0000[diff] [blame]208 % ../src/configure --prefix=$CFEINSTALL --disable-threads --disable-nls \
Chris Lattner23c5b3c2006-02-05 06:44:17 +0000[diff] [blame]209 --disable-shared --enable-languages=c,c++ --host=sparc-sun-solaris2.8 \
Reid Spencer4ac306502004-12-22 06:40:29 +0000[diff] [blame]210 --disable-c-mbchar --program-prefix=llvm-
Brian Gaeke7e9bd802004-01-28 20:54:41 +0000[diff] [blame]211 % gmake all; gmake install
John Criswell55072842003-12-08 19:59:14 +0000[diff] [blame]212</pre>
213
Chris Lattnere38c6282003-10-23 03:55:23 +0000[diff] [blame]214 <p><b>Common Problem:</b> You may get error messages regarding the fact
Brian Gaeke46079d22003-10-21 21:58:38 +0000[diff] [blame]215 that LLVM does not support inline assembly. Here are two common
216 fixes:</p>
217
218 <ul>
219 <li><p><b>Fix 1:</b> If you have system header files that include
220 inline assembly, you may have to modify them to remove the inline
John Criswell9e2485c2004-12-10 15:51:16 +0000[diff] [blame]221 assembly and install the modified versions in
Chris Lattner37874052004-10-06 03:13:47 +0000[diff] [blame]222 <code>$CFEINSTALL/lib/gcc/<i>target-triplet</i>/3.4-llvm/include</code>.</li>
Brian Gaeke46079d22003-10-21 21:58:38 +0000[diff] [blame]223
224 <li><b>Fix 2:</b> If you are building the C++ front-end on a CPU we
225 haven't tried yet, you will probably have to edit the appropriate
226 version of atomicity.h under
227 <code>src/libstdc++-v3/config/cpu/<i>name-of-cpu</i>/atomicity.h</code>
Misha Brukman6a2b3102004-05-12 18:49:47 +0000[diff] [blame]228 and apply a patch so that it does not use inline assembly.</li>
Brian Gaeke46079d22003-10-21 21:58:38 +0000[diff] [blame]229 </ul>
230
John Criswell9e2485c2004-12-10 15:51:16 +0000[diff] [blame]231 <p><b>Porting to a new architecture:</b> If you are porting the front-end
232 to a new architecture or compiling in a configuration that we have
233 not tried previously, there are probably several changes you will have to make
234 to the GCC target to get it to work correctly. These include:<p>
Brian Gaeke46079d22003-10-21 21:58:38 +0000[diff] [blame]235
236 <ul>
John Criswell6e35eda2004-11-29 21:46:29 +0000[diff] [blame]237 <li>Often targets include special assembler or linker flags which
Chris Lattnere38c6282003-10-23 03:55:23 +0000[diff] [blame]238 <tt>gccas</tt>/<tt>gccld</tt> does not understand. In general, these can
239 just be removed.</li>
240 <li>LLVM currently does not support any floating point values other than
241 32-bit and 64-bit IEEE floating point. The primary effect of this is
242 that you may have to map "long double" onto "double".</li>
243 <li>The profiling hooks in GCC do not apply at all to the LLVM front-end.
244 These may need to be disabled.</li>
245 <li>No inline assembly for position independent code. At the LLVM level,
246 everything is position independent.</li>
247 <li>We handle <tt>.init</tt> and <tt>.fini</tt> differently.</li>
Chris Lattner13964e02003-10-24 16:02:34 +0000[diff] [blame]248 <li>You may have to disable multilib support in your target. Using multilib
249 support causes the GCC compiler driver to add a lot of "<tt>-L</tt>"
250 options to the link line, which do not relate to LLVM and confuse
251 <tt>gccld</tt>. To disable multilibs, delete any
252 <tt>MULTILIB_OPTIONS</tt> lines from your target files.</li>
Chris Lattnere38c6282003-10-23 03:55:23 +0000[diff] [blame]253 <li>Did we mention that we don't support inline assembly? You'll probably
254 have to add some fixinclude hacks to disable it in the system
255 headers.</li>
Brian Gaeke46079d22003-10-21 21:58:38 +0000[diff] [blame]256 </ul>
Misha Brukman83bd33a2003-10-23 01:48:33 +0000[diff] [blame]257</li>
Brian Gaeke46079d22003-10-21 21:58:38 +0000[diff] [blame]258
Reid Spencer4ac306502004-12-22 06:40:29 +0000[diff] [blame]259<li><p>Put <tt>$CFEINSTALL/bin</tt> into your <tt>PATH</tt> environment
260variable.</p>
261 <ul>
262 <li>sh: <tt>export PATH=$CFEINSTALL/bin:$PATH</tt></li>
263 <li>csh: <tt>setenv PATH $CFEINSTALL/bin:$PATH</tt></li>
Reid Spencer4ac306502004-12-22 06:40:29 +0000[diff] [blame]264 </ul>
265</li>
266
Chris Lattner6a615ad2004-06-01 18:13:05 +0000[diff] [blame]267<li><p>Go back into the LLVM source tree proper. Rerun configure, using
Reid Spencer4ac306502004-12-22 06:40:29 +0000[diff] [blame]268the same options as the last time. This will cause the configuration to now find
269the newly built llvm-gcc and llvm-g++ executables. </p></li>
Brian Gaeke46079d22003-10-21 21:58:38 +0000[diff] [blame]270
Chris Lattner6a615ad2004-06-01 18:13:05 +0000[diff] [blame]271<li><p>Rebuild your CVS tree. This shouldn't cause the whole thing to be
272 rebuilt, but it should build the runtime libraries. After the tree is
John Criswell9e2485c2004-12-10 15:51:16 +0000[diff] [blame]273 built, install the runtime libraries into your GCC front-end build tree.
Misha Brukman98558ae2005-03-01 17:15:23 +0000[diff] [blame]274 These are the commands you need:</p>
Brian Gaeke46079d22003-10-21 21:58:38 +0000[diff] [blame]275<pre>
Chris Lattner6a615ad2004-06-01 18:13:05 +0000[diff] [blame]276 % gmake
Reid Spencer3149ba72004-12-04 08:13:20 +0000[diff] [blame]277 % gmake -C runtime install-bytecode
Misha Brukman83bd33a2003-10-23 01:48:33 +0000[diff] [blame]278</pre></li>
Brian Gaeke46079d22003-10-21 21:58:38 +0000[diff] [blame]279
Reid Spencerf99e59a2004-11-25 17:13:17 +0000[diff] [blame]280<li><p>Optionally, build a symbol table for the newly installed runtime
Reid Spencer4ac306502004-12-22 06:40:29 +0000[diff] [blame]281libraries. Although this step is optional, you are strongly encouraged to
282do this as the symbol tables will make a significant difference in your
283link times. Use the <tt>llvm-ranlib</tt> tool to do this, as follows:</p>
Reid Spencerf99e59a2004-11-25 17:13:17 +0000[diff] [blame]284<pre>
285 % cd $CFEINSTALL/lib
286 % llvm-ranlib libiberty.a
287 % llvm-ranlib libstdc++.a
Chris Lattner302ed2a2004-12-01 04:16:29 +0000[diff] [blame]288 % llvm-ranlib libsupc++.a
Reid Spencercfaf80c2004-12-22 16:19:05 +0000[diff] [blame]289 % cd $CFEINSTALL/lib/gcc/<i>target-triplet</i>/3.4-llvm
Reid Spencerf99e59a2004-11-25 17:13:17 +0000[diff] [blame]290 % llvm-ranlib libgcc.a
291 % llvm-ranlib libgcov.a
292</pre>
293
Brian Gaeke46079d22003-10-21 21:58:38 +0000[diff] [blame]294<li><p>Test the newly-installed C frontend by one or more of the
295following means:</p>
296 <ul>
Reid Spencer4ac306502004-12-22 06:40:29 +0000[diff] [blame]297 <li> running the feature &amp; regression tests via <tt>make check</tt></li>
Chris Lattnere38c6282003-10-23 03:55:23 +0000[diff] [blame]298 <li> compiling and running a "hello, LLVM" program in C and C++.</li>
John Criswell9e2485c2004-12-10 15:51:16 +0000[diff] [blame]299 <li> running the tests found in the <tt>llvm-test</tt> CVS module</li>
Misha Brukman6a2b3102004-05-12 18:49:47 +0000[diff] [blame]300 </ul></li>
Brian Gaeke46079d22003-10-21 21:58:38 +0000[diff] [blame]301</ol>
Misha Brukman83bd33a2003-10-23 01:48:33 +0000[diff] [blame]302</div>
Brian Gaeke46079d22003-10-21 21:58:38 +0000[diff] [blame]303
304<!-- *********************************************************************** -->
John Criswelld000e1d2003-12-18 16:43:17 +0000[diff] [blame]305<div class="doc_section">
306 <a name="license">License Information</a>
307</div>
308
309<div class="doc_text">
310<p>
311The LLVM GCC frontend is licensed to you under the GNU General Public License
312and the GNU Lesser General Public License. Please see the files COPYING and
313COPYING.LIB for more details.
314</p>
315
316<p>
317The software also has the following additional copyrights:
318</p>
319
320<pre>
John Criswelle3602102004-03-12 18:02:17 +0000[diff] [blame]321
John Criswellb0aad7a2005-05-12 21:25:32 +0000[diff] [blame]322Copyright (c) 2003, 2004, 2005 University of Illinois at Urbana-Champaign.
John Criswelle3602102004-03-12 18:02:17 +0000[diff] [blame]323All rights reserved.
324
325Developed by:
326
327 LLVM Team
328
329 University of Illinois at Urbana-Champaign
330
Reid Spencer05fe4b02006-03-14 05:39:39 +0000[diff] [blame]331 http://llvm.org
John Criswelle3602102004-03-12 18:02:17 +0000[diff] [blame]332
333THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
334IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS
335FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
336CONTRIBUTORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
337LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
338OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS WITH THE
339SOFTWARE.
340
John Criswelld000e1d2003-12-18 16:43:17 +0000[diff] [blame]341Copyright (c) 1994
342Hewlett-Packard Company
343
344Permission to use, copy, modify, distribute and sell this software
345and its documentation for any purpose is hereby granted without fee,
346provided that the above copyright notice appear in all copies and
347that both that copyright notice and this permission notice appear
348in supporting documentation. Hewlett-Packard Company makes no
349representations about the suitability of this software for any
350purpose. It is provided "as is" without express or implied warranty.
351
352Copyright (c) 1996, 1997, 1998, 1999
353Silicon Graphics Computer Systems, Inc.
354
355Permission to use, copy, modify, distribute and sell this software
356and its documentation for any purpose is hereby granted without fee,
357provided that the above copyright notice appear in all copies and
358that both that copyright notice and this permission notice appear
359in supporting documentation. Silicon Graphics makes no
360representations about the suitability of this software for any
361purpose. It is provided "as is" without express or implied warranty.
362</pre>
363</div>
364
365<!-- *********************************************************************** -->
Brian Gaeke46079d22003-10-21 21:58:38 +0000[diff] [blame]366
Misha Brukmanb9e57892003-10-28 21:09:29 +0000[diff] [blame]367<hr>
Misha Brukman6a2b3102004-05-12 18:49:47 +0000[diff] [blame]368<address>
369 <a href="http://jigsaw.w3.org/css-validator/check/referer"><img
370 src="http://jigsaw.w3.org/css-validator/images/vcss" alt="Valid CSS!"></a>
371 <a href="http://validator.w3.org/check/referer"><img
372 src="http://www.w3.org/Icons/valid-html401" alt="Valid HTML 4.01!"></a>
373
374 Brian Gaeke<br>
Reid Spencer05fe4b02006-03-14 05:39:39 +0000[diff] [blame]375 <a href="http://llvm.org">LLVM Compiler Infrastructure</a><br>
Misha Brukmanb9e57892003-10-28 21:09:29 +0000[diff] [blame]376 Last modified: $Date$
Misha Brukman6a2b3102004-05-12 18:49:47 +0000[diff] [blame]377</address>
Brian Gaeke46079d22003-10-21 21:58:38 +0000[diff] [blame]378
Misha Brukman83bd33a2003-10-23 01:48:33 +0000[diff] [blame]379</body>
380</html>