Gitiles
Code Review Sign In
gerrit-public.fairphone.software / toolchain / llvm-project / 9580ce235be2976360bf4aa61cb95665e763a4ad / . / llvm / docs / ReleaseNotes.html
blob: cb16d7f16bdb7a1fd4d26d7a08ae50cec2fb5494 [file] [log] [blame]
Chris Lattner3d482502003-10-02 04:57:28 +0000[diff] [blame]1<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
Chris Lattner7c4bd1d2003-10-27 01:31:14 +0000[diff] [blame]2<html><head><title>LLVM 1.1 Release Notes</title></head>
Chris Lattner3d482502003-10-02 04:57:28 +0000[diff] [blame]3<body bgcolor=white>
4
5<table width="100%" bgcolor="#330077" border=0 cellpadding=4 cellspacing=0>
Chris Lattner7c4bd1d2003-10-27 01:31:14 +0000[diff] [blame]6<tr><td>&nbsp; <font size=+3 color="#EEEEFF" face="Georgia,Palatino,Times,Roman"><b>LLVM 1.1 Release Notes</b></font></td>
Chris Lattner3d482502003-10-02 04:57:28 +0000[diff] [blame]7</tr></table>
8
9<ol>
Chris Lattnera9b4c392003-10-02 05:09:46 +0000[diff] [blame]10 <li><a href="#intro">Introduction</a>
Chris Lattner3d482502003-10-02 04:57:28 +0000[diff] [blame]11 <li><a href="#whatsnew">What's New?</a>
Chris Lattner62495762003-10-02 16:38:05 +0000[diff] [blame]12 <li><a href="#portability">Portability and Supported Platforms</a>
Chris Lattner3d482502003-10-02 04:57:28 +0000[diff] [blame]13 <li><a href="#install-instructions">Installation Instructions</a>
14 <li><a href="#knownproblems">Known Problems</a>
15 <ul>
Chris Lattner62495762003-10-02 16:38:05 +0000[diff] [blame]16<!-- <li><a href="#portabilityprobs">Portability Problems</a> -->
Chris Lattner3d482502003-10-02 04:57:28 +0000[diff] [blame]17 <li><a href="#core">Known problems with the LLVM Core</a>
18 <li><a href="#c-fe">Known problems with the C Front-end</a>
19 <li><a href="#c++-fe">Known problems with the C++ Front-end</a>
20 <li><a href="#x86-be">Known problems with the X86 Back-end</a>
21 <li><a href="#sparc-be">Known problems with the Sparc Back-end</a>
22 <li><a href="#c-be">Known problems with the C back-end</a>
23 </ul>
24 <li><a href="#additionalinfo">Additional Information</a>
25 </ul>
26
27 <p><b>Written by <a href="mailto:sabre@nondot.org">Chris Lattner</a></b><p>
28</ol>
29
30
31<!-- *********************************************************************** -->
32<table width="100%" bgcolor="#330077" border=0 cellpadding=4 cellspacing=0>
33<tr><td align=center><font color="#EEEEFF" size=+2 face="Georgia,Palatino"><b>
34<a name="intro">Introduction
35</b></font></td></tr></table><ul>
36<!-- *********************************************************************** -->
37
38This document contains the release notes for the LLVM compiler infrastructure,
Chris Lattner7c4bd1d2003-10-27 01:31:14 +0000[diff] [blame]39release 1.1. Here we describe the status of LLVM, including any known problems,
40and bug fixes from the previous release. The most up-to-date version of this
41document can be found on the <a
42href="http://llvm.cs.uiuc.edu/releases/1.1/">LLVM 1.1 web site</a>. If you are
Chris Lattnere7525b52003-10-07 21:38:31 +0000[diff] [blame]43not reading this on the LLVM web pages, you should probably go there, because
44this document may be updated after the release.<p>
Chris Lattner62495762003-10-02 16:38:05 +0000[diff] [blame]45
Chris Lattnere7525b52003-10-07 21:38:31 +0000[diff] [blame]46For more information about LLVM, including information about potentially more
47current releases, please check out the <a href="http://llvm.cs.uiuc.edu">main
48web site</a>. If you have questions or comments, the <a
49href="http://mail.cs.uiuc.edu/mailman/listinfo/llvmdev">LLVM developer's mailing
50list</a> is a good place to send them.<p>
Chris Lattner3d482502003-10-02 04:57:28 +0000[diff] [blame]51
Chris Lattner7c4bd1d2003-10-27 01:31:14 +0000[diff] [blame]52Note that if you are reading this file from CVS, that this document applies to
53the <i>next</i> release, not the previous one. To see the release notes for the
54previous release, see the <a href="http://llvm.cs.uiuc.edu/releases/">releases
55page</a>.<p>
Chris Lattner3d482502003-10-02 04:57:28 +0000[diff] [blame]56
57<!-- *********************************************************************** -->
58</ul><table width="100%" bgcolor="#330077" border=0 cellpadding=4 cellspacing=0>
59<tr><td align=center><font color="#EEEEFF" size=+2 face="Georgia,Palatino"><b>
60<a name="whatsnew">What's New?
61</b></font></td></tr></table><ul>
62<!-- *********************************************************************** -->
63
Chris Lattner7c4bd1d2003-10-27 01:31:14 +0000[diff] [blame]64This is the second public release of the LLVM compiler infrastructure. This
65release implements the following new features:<p>
Chris Lattnere7525b52003-10-07 21:38:31 +0000[diff] [blame]66
67<ol>
Chris Lattner4491de62003-11-08 04:28:55 +0000[diff] [blame]68<li><a href="http://mail.cs.uiuc.edu/pipermail/llvmdev/2003-November/000528.html">A new LLVM profiler, similar to gprof</a> is available</li><p>
69
70<li>LLVM and the C/C++ front-end now compile on Mac OSX! Mac OSX users can now
71explore the LLVM optimizer with the C backend (note that LLVM requires GCC 3.3
72on Mac OSX).</li><p>
73
Chris Lattner74a22992003-11-11 23:46:35 +0000[diff] [blame]74<li>LLVM has been <a
75href="http://mail.cs.uiuc.edu/pipermail/llvmdev/2003-November/000554.html">moved
76into an 'llvm' C++ namespace</a>, for easier integration with third-party
77code.</a></li>
Brian Gaeke10ea8232003-11-11 22:45:41 +0000[diff] [blame]78
Chris Lattner4491de62003-11-08 04:28:55 +0000[diff] [blame]79</ol><p>
80
81In this release, the following missing features were implemented:<p>
82
83<ol>
84<li><a href="http://llvm.cs.uiuc.edu/PR88">The interpreter does not support
85invoke or unwind</a></li>
Chris Lattnere7525b52003-10-07 21:38:31 +0000[diff] [blame]86</ol><p>
87
Chris Lattner639579c2003-10-27 17:06:39 +0000[diff] [blame]88In this release, the following Quality of Implementation issues were fixed:<p>
89
90<ol>
Chris Lattner4491de62003-11-08 04:28:55 +0000[diff] [blame]91
92<li><a href="http://llvm.cs.uiuc.edu/PR29">C++ front-end is not generating
93linkonce linkage type when it can</a></li>
94
95<li><a href="http://llvm.cs.uiuc.edu/PR84">C front-end doesn't emit
96getelementptr for address of array element</a></li>
97
Chris Lattner639579c2003-10-27 17:06:39 +0000[diff] [blame]98</ol><p>
99
Chris Lattner4491de62003-11-08 04:28:55 +0000[diff] [blame]100
Chris Lattner25fd5c12003-10-27 05:41:39 +0000[diff] [blame]101In this release, the following bugs in the previous release were fixed:<p>
Chris Lattnere7525b52003-10-07 21:38:31 +0000[diff] [blame]102
103<ol>
Chris Lattner25fd5c12003-10-27 05:41:39 +0000[diff] [blame]104<li><a href="http://llvm.cs.uiuc.edu/PR57">[inliner] Inlining invoke with PHI in unwind target is broken</a></li>
Chris Lattner639579c2003-10-27 17:06:39 +0000[diff] [blame]105<li><a href="http://llvm.cs.uiuc.edu/PR58">[linker] linkonce globals should link successfully to external globals</a></li>
Chris Lattnerd16d9752003-10-27 17:58:57 +0000[diff] [blame]106<li><a href="http://llvm.cs.uiuc.edu/PR59">C++ frontend can crash when compiling virtual base classes</a></li>
Chris Lattner36213c72003-10-28 23:13:03 +0000[diff] [blame]107<li><a href="http://llvm.cs.uiuc.edu/PR62">C backend fails on constant cast expr to ptr-to-anonymous struct</a></li>
Chris Lattner56df0a52003-10-29 01:26:07 +0000[diff] [blame]108<li><a href="http://llvm.cs.uiuc.edu/PR63">#ident is not recognized by C frontend</a></li>
Chris Lattnera1a090e2003-10-29 07:17:13 +0000[diff] [blame]109<li><a href="http://llvm.cs.uiuc.edu/PR64">[constmerge] Constant merging pass merges constants with external linkage</a></li>
110<li><a href="http://llvm.cs.uiuc.edu/PR65">C front-end miscompiles the builtin_expect intrinsic!</a></li>
Chris Lattner5b83b562003-10-29 18:49:14 +0000[diff] [blame]111<li><a href="http://llvm.cs.uiuc.edu/PR66">[scalarrepl] Scalar Replacement of aggregates is decimating structures it shouldn't be</a></li>
112<li><a href="http://llvm.cs.uiuc.edu/PR67">1.0 precompiled libstdc++ does not include wchar_t support</a></li>
Chris Lattnerab8873d2003-10-29 20:59:45 +0000[diff] [blame]113<li><a href="http://llvm.cs.uiuc.edu/PR68">llvmgcc asserts when compiling functions renamed with asm's</a></li>
114<li><a href="http://llvm.cs.uiuc.edu/PR69">C frontend crashes on some programs with lots of types.</a></li>
Chris Lattnera2bd4e02003-10-30 01:20:42 +0000[diff] [blame]115<li><a href="http://llvm.cs.uiuc.edu/PR70">[instcombine] Resolving invoke inserts cast after terminator</a></li>
Chris Lattnera306dd22003-10-30 01:43:33 +0000[diff] [blame]116<li><a href="http://llvm.cs.uiuc.edu/PR71">llvm-as crashes when labels are used in phi nodes</a></li>
Chris Lattnerb45e1f92003-10-30 16:20:15 +0000[diff] [blame]117<li><a href="http://llvm.cs.uiuc.edu/PR72">[build problem] Callgraph.cpp not pulled in from libipa.a</a></li>
Chris Lattnerdd024a02003-11-02 02:15:11 +0000[diff] [blame]118<li><a href="http://llvm.cs.uiuc.edu/PR79">llvm-gcc crashes compiling global union initializer</a></li>
119<li><a href="http://llvm.cs.uiuc.edu/PR80">C front-end crash on empty structure</a></li>
120<li><a href="http://llvm.cs.uiuc.edu/PR81">CFrontend crashes when compiling C99 compound expressions</a></li>
Chris Lattneref114d52003-11-03 20:08:08 +0000[diff] [blame]121<li><a href="http://llvm.cs.uiuc.edu/PR83">[X86] Emission of global bool initializers broken</a></li>
Chris Lattnerc679fbb2003-11-04 20:06:53 +0000[diff] [blame]122<li><a href="http://llvm.cs.uiuc.edu/PR87">llvm-gcc infinite loops on "case MAXINT:"</a></li>
Chris Lattnerab77bc52003-11-05 06:30:04 +0000[diff] [blame]123<li><a href="http://llvm.cs.uiuc.edu/PR89">[C++] Catch blocks make unparsable labels</a></li>
124<li><a href="http://llvm.cs.uiuc.edu/PR90">[C++] Initializing array with constructable objects fail</a></li>
125<li><a href="http://llvm.cs.uiuc.edu/PR91">[gccld] The -r (relinking) option does not work correctly</a></li>
Chris Lattner34596d72003-11-07 04:46:56 +0000[diff] [blame]126<li><a href="http://llvm.cs.uiuc.edu/PR92">[bcreader] Cannot read shift constant expressions from bytecode file</a></li>
127<li><a href="http://llvm.cs.uiuc.edu/PR93">[lowersetjmp] Lowersetjmp pass breaks dominance properties!</a></li>
128<li><a href="http://llvm.cs.uiuc.edu/PR94">llvm-gcc tries to add bools</a></li>
Chris Lattner881cb482003-11-09 19:44:07 +0000[diff] [blame]129<li><a href="http://llvm.cs.uiuc.edu/PR95">SymbolTable::getUniqueName is very inefficient</a></li>
Chris Lattner34596d72003-11-07 04:46:56 +0000[diff] [blame]130<li><a href="http://llvm.cs.uiuc.edu/PR98">[buildscripts] Building into objdir with .o in it fails</a></li>
Chris Lattner699a58d2003-11-08 05:18:50 +0000[diff] [blame]131<li><a href="http://llvm.cs.uiuc.edu/PR101">[setjmp/longjmp] Linking C programs which use setjmp/longjmp sometimes fail with references to the C++ runtime library!</a></li>
Chris Lattner881cb482003-11-09 19:44:07 +0000[diff] [blame]132<li><a href="http://llvm.cs.uiuc.edu/PR104">[c++] C++ Frontend lays out superclasses like anonymous bitfields!</a></li>
Chris Lattnera7235372003-11-12 04:42:37 +0000[diff] [blame]133<li><a href="http://llvm.cs.uiuc.edu/PR107">AsmParser Misses Symbol Redefinition Error</a></li>
Brian Gaeke7aeb2b72003-11-11 21:52:34 +0000[diff] [blame]134<li><a href="http://llvm.cs.uiuc.edu/PR108">gccld -Lfoo -lfoo fails to find ./foo/libfoo.a</a></li>
Chris Lattnere7525b52003-10-07 21:38:31 +0000[diff] [blame]135</ol><p>
136
Chris Lattnera623e482003-10-20 19:05:03 +0000[diff] [blame]137At this time, LLVM is known to work properly with SPEC CPU 2000, the Olden
138benchmarks, and the Ptrdist benchmarks among many other programs. Note however
139that the Sparc and X86 backends do not currently support exception throwing or
Chris Lattnerb28c3282003-10-24 04:03:19 +0000[diff] [blame]140long jumping (including 253.perlbmk in SPEC). For these programs you must use
141the C backend.<p>
Chris Lattner62495762003-10-02 16:38:05 +0000[diff] [blame]142
143
144<!-- *********************************************************************** -->
145</ul><table width="100%" bgcolor="#330077" border=0 cellpadding=4 cellspacing=0>
146<tr><td align=center><font color="#EEEEFF" size=+2 face="Georgia,Palatino"><b>
147<a name="portability">Portability and Supported Platforms
148</b></font></td></tr></table><ul>
149<!-- *********************************************************************** -->
150
Chris Lattner14b5d5a2003-11-08 05:22:09 +0000[diff] [blame]151LLVM has been extensively tested on Intel and AMD machines running Red
152Hat Linux, and Sun UltraSPARC workstations running Solaris 8. Additionally,
153LLVM works on Mac OS/X 10.3 and above, but only with the C back-end (no native
154backend for the PowerPC is available yet).
Chris Lattner62495762003-10-02 16:38:05 +0000[diff] [blame]155The core LLVM infrastructure uses "autoconf" for portability, so hopefully we
Chris Lattner14b5d5a2003-11-08 05:22:09 +0000[diff] [blame]156work on more platforms than that. However, it is likely that we
157missed something, and that minor porting is required to get LLVM to work on
158new platforms. We welcome portability patches and error messages.<p>
Chris Lattner3d482502003-10-02 04:57:28 +0000[diff] [blame]159
160
161<!-- *********************************************************************** -->
162</ul><table width="100%" bgcolor="#330077" border=0 cellpadding=4 cellspacing=0>
163<tr><td align=center><font color="#EEEEFF" size=+2 face="Georgia,Palatino"><b>
Chris Lattner3d482502003-10-02 04:57:28 +0000[diff] [blame]164<a name="knownproblems">Known Problems
165</b></font></td></tr></table><ul>
166<!-- *********************************************************************** -->
167
168This section contains all known problems with the LLVM system, listed by
169component. As new problems are discovered, they will be added to these
Chris Lattner62495762003-10-02 16:38:05 +0000[diff] [blame]170sections.
Chris Lattner3d482502003-10-02 04:57:28 +0000[diff] [blame]171
172
173<!-- _______________________________________________________________________ -->
Chris Lattner62495762003-10-02 16:38:05 +0000[diff] [blame]174<!--
Chris Lattner3d482502003-10-02 04:57:28 +0000[diff] [blame]175</ul><h4><a name="portability"><hr size=0>Portability Problems</h4><ul>
Chris Lattner62495762003-10-02 16:38:05 +0000[diff] [blame]176-->
Chris Lattner3d482502003-10-02 04:57:28 +0000[diff] [blame]177
178
179<!-- _______________________________________________________________________ -->
180</ul><h4><a name="core"><hr size=0>Known problems with the LLVM Core</h4><ul>
181
182<li>In the JIT, <tt>dlsym</tt> on a symbol compiled by the JIT will not work.<p>
183
184<li>The JIT does not use mutexes to protect its internal data structures. As
185 such, execution of a threaded program could cause these data structures to
186 be corrupted.<p>
187
188<li>It is not possible to <tt>dlopen</tt> an LLVM bytecode file in the JIT.<p>
189
Chris Lattnera623e482003-10-20 19:05:03 +0000[diff] [blame]190<li>Linking in static archive files (.a files) is very slow (there is no symbol
Chris Lattnerc679fbb2003-11-04 20:06:53 +0000[diff] [blame]191table in the archive).<p>
192
Chris Lattnerc679fbb2003-11-04 20:06:53 +0000[diff] [blame]193<li><a href="http://llvm.cs.uiuc.edu/PR82">LLVM cannot handle structures with
194more than 256 elements</a>.<p>
Chris Lattner178f3db2003-10-02 05:07:23 +0000[diff] [blame]195
Chris Lattner3d482502003-10-02 04:57:28 +0000[diff] [blame]196<!-- _______________________________________________________________________ -->
197</ul><h4><a name="c-fe"><hr size=0>Known problems with the C front-end</h4><ul>
198
Chris Lattnerd2a74272003-10-27 18:30:37 +0000[diff] [blame]199</ul><b>Bugs:</b><ul><p>
Chris Lattner3d482502003-10-02 04:57:28 +0000[diff] [blame]200
Chris Lattnerd2a74272003-10-27 18:30:37 +0000[diff] [blame]201<li><a href="http://llvm.cs.uiuc.edu/PR6">Oversized integer bitfields cause crash</a>.<p>
202
Chris Lattner3d482502003-10-02 04:57:28 +0000[diff] [blame]203<li>C99 Variable sized arrays do not release stack memory when they go out of
204 scope. Thus, the following program may run out of stack space:
205<pre>
206 for (i = 0; i != 1000000; ++i) {
207 int X[n];
208 foo(X);
209 }
210</pre><p>
211
Chris Lattnerd2a74272003-10-27 18:30:37 +0000[diff] [blame]212</ul><b>Notes:</b><ul><p>
213
214<li>Inline assembly is not yet supported.<p>
215
216<li>"long double" is transformed by the front-end into "double". There is no
217 support for floating point data types of any size other than 32 and 64 bits.
218 <p>
219
Chris Lattnera9b4c392003-10-02 05:09:46 +0000[diff] [blame]220<li>The following Unix system functionality has not been tested and may not work:
Chris Lattner3d482502003-10-02 04:57:28 +0000[diff] [blame]221<ol>
222 <li><tt>sigsetjmp</tt>, <tt>siglongjmp</tt> - These are not turned into the
John Criswell9d977d52003-10-27 17:41:53 +0000[diff] [blame]223 appropriate <tt>invoke</tt>/<tt>unwind</tt> instructions. Note that
224 <tt>setjmp</tt> and <tt>longjmp</tt> <em>are</em> compiled correctly.
Chris Lattner3d482502003-10-02 04:57:28 +0000[diff] [blame]225 <li><tt>getcontext</tt>, <tt>setcontext</tt>, <tt>makecontext</tt>
226 - These functions have not been tested.
227</ol><p>
228
229<li>Although many GCC extensions are supported, some are not. In particular,
230 the following extensions are known to <b>not be</b> supported:
231 <ol>
232 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Local-Labels.html#Local%20Labels">Local Labels</a>: Labels local to a block.
233 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Labels-as-Values.html#Labels%20as%20Values">Labels as Values</a>: Getting pointers to labels, and computed gotos.
234 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Nested-Functions.html#Nested%20Functions">Nested Functions</a>: As in Algol and Pascal, lexical scoping of functions.
235 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Constructing-Calls.html#Constructing%20Calls">Constructing Calls</a>: Dispatching a call to another function.
236 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Extended-Asm.html#Extended%20Asm">Extended Asm</a>: Assembler instructions with C expressions as operands.
237 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Constraints.html#Constraints">Constraints</a>: Constraints for asm operands
238 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Asm-Labels.html#Asm%20Labels">Asm Labels</a>: Specifying the assembler name to use for a C symbol.
239 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Explicit-Reg-Vars.html#Explicit%20Reg%20Vars">Explicit Reg Vars</a>: Defining variables residing in specified registers.
240 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Return-Address.html#Return%20Address">Return Address</a>: Getting the return or frame address of a function.
241 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Vector-Extensions.html#Vector%20Extensions">Vector Extensions</a>: Using vector instructions through built-in functions.
242 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Target-Builtins.html#Target%20Builtins">Target Builtins</a>: Built-in functions specific to particular targets.
243 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Thread-Local.html#Thread-Local">Thread-Local</a>: Per-thread variables.
244 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Pragmas.html#Pragmas">Pragmas</a>: Pragmas accepted by GCC.
245 </ol><p>
246
247 The following GCC extensions are <b>partially</b> supported. An ignored
248 attribute means that the LLVM compiler ignores the presence of the attribute,
249 but the code should still work. An unsupported attribute is one which is
250 ignored by the LLVM compiler, which will cause a different interpretation of
251 the program.<p>
252
253 <ol>
254 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Variable-Length.html#Variable%20Length">Variable Length</a>:
255 Arrays whose length is computed at run time.<br>
256 Supported, but allocated stack space is not freed until the function returns (noted above).
257
258 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Function-Attributes.html#Function%20Attributes">Function Attributes</a>:
259 Declaring that functions have no side effects, or that they can never return.<br>
260 <b>Supported:</b> <tt>format</tt>, <tt>format_arg</tt>, <tt>non_null</tt>, <tt>constructor</tt>, <tt>destructor</tt>, <tt>unused</tt>, <tt>deprecated</tt>,
261 <tt>warn_unused_result</tt>, <tt>weak</tt><br>
262 <b>Ignored:</b> <tt>noreturn</tt>, <tt>noinline</tt>, <tt>always_inline</tt>, <tt>pure</tt>, <tt>const</tt>, <tt>nothrow</tt>, <tt>malloc</tt>
263 <tt>no_instrument_function</tt>, <tt>cdecl</tt><br>
264 <b>Unsupported:</b> <tt>used</tt>, <tt>section</tt>, <tt>alias</tt>, <tt>visibility</tt>, <tt>regparm</tt>, <tt>stdcall</tt>,
265 <tt>fastcall</tt>, all other target specific attributes
266
267 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Variable-Attributes.html#Variable%20Attributes">Variable Attributes</a>:
268 Specifying attributes of variables.<br>
269 <b>Supported:</b> <tt>cleanup</tt>, <tt>common</tt>, <tt>nocommon</tt>,
270 <tt>deprecated</tt>, <tt>transparent_union</tt>,
271 <tt>unused</tt>, <tt>weak</tt><br>
272 <b>Unsupported:</b> <tt>aligned</tt>, <tt>mode</tt>, <tt>packed</tt>,
273 <tt>section</tt>, <tt>shared</tt>, <tt>tls_model</tt>,
274 <tt>vector_size</tt>, <tt>dllimport</tt>,
275 <tt>dllexport</tt>, all target specific attributes.<br>
276
277 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Type-Attributes.html#Type%20Attributes">Type Attributes</a>: Specifying attributes of types.
278 <b>Supported:</b> <tt>transparent_union</tt>, <tt>unused</tt>,
279 <tt>deprecated</tt>, <tt>may_alias</tt>
280 <b>Unsupported:</b> <tt>aligned</tt>, <tt>packed</tt>
281 all target specific attributes.<br>
282 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Other-Builtins.html#Other%20Builtins">Other Builtins</a>:
283 Other built-in functions.<br>
284 We support all builtins which have a C language equivalent (e.g.,
285 <tt>__builtin_cos</tt>), <tt>__builtin_alloca</tt>,
286 <tt>__builtin_types_compatible_p</tt>, <tt>__builtin_choose_expr</tt>,
287 <tt>__builtin_constant_p</tt>, and <tt>__builtin_expect</tt> (ignored).
288 </ol><p>
289
290
291 The following extensions <b>are</b> known to be supported:
292 <ol>
293 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Statement-Exprs.html#Statement%20Exprs">Statement Exprs</a>: Putting statements and declarations inside expressions.
294 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Typeof.html#Typeof">Typeof</a>: <code>typeof</code>: referring to the type of an expression.
Chris Lattner62495762003-10-02 16:38:05 +0000[diff] [blame]295 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Lvalues.html#Lvalues">Lvalues</a>: Using <code>?:</code>, "<code>,</code>" and casts in lvalues.
Chris Lattner3d482502003-10-02 04:57:28 +0000[diff] [blame]296 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Conditionals.html#Conditionals">Conditionals</a>: Omitting the middle operand of a <code>?:</code> expression.
297 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Long-Long.html#Long%20Long">Long Long</a>: Double-word integers.
298 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Complex.html#Complex">Complex</a>: Data types for complex numbers.
299 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Hex-Floats.html#Hex%20Floats">Hex Floats</a>:Hexadecimal floating-point constants.
300 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Zero-Length.html#Zero%20Length">Zero Length</a>: Zero-length arrays.
301 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Empty-Structures.html#Empty%20Structures">Empty Structures</a>: Structures with no members.
302 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Variadic-Macros.html#Variadic%20Macros">Variadic Macros</a>: Macros with a variable number of arguments.
303 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Escaped-Newlines.html#Escaped%20Newlines">Escaped Newlines</a>: Slightly looser rules for escaped newlines.
304 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Subscripting.html#Subscripting">Subscripting</a>: Any array can be subscripted, even if not an lvalue.
305 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Pointer-Arith.html#Pointer%20Arith">Pointer Arith</a>:Arithmetic on <code>void</code>-pointers and function pointers.
306 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Initializers.html#Initializers">Initializers</a>: Non-constant initializers.
307 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Compound-Literals.html#Compound%20Literals">Compound Literals</a>: Compound literals give structures, unions or arrays as values.
308 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Designated-Inits.html#Designated%20Inits">Designated Inits</a>: Labeling elements of initializers.
309
310 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Cast-to-Union.html#Cast%20to%20Union">Cast to Union</a>:Casting to union type from any member of the union.
311 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Case-Ranges.html#Case%20Ranges">Case Ranges</a>: `case 1 ... 9' and such.
312 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Mixed-Declarations.html#Mixed%20Declarations">Mixed Declarations</a>: Mixing declarations and code.
313
314 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Function-Prototypes.html#Function%20Prototypes">Function Prototypes</a>: Prototype declarations and old-style definitions.
315 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/C---Comments.html#C++%20Comments">C++ Comments</a>: C++ comments are recognized.
316 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Dollar-Signs.html#Dollar%20Signs">Dollar Signs</a>: Dollar sign is allowed in identifiers.
317 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Character-Escapes.html#Character%20Escapes">Character Escapes</a>: <code>\e</code> stands for the character &lt;ESC&gt;.
318 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Alignment.html#Alignment">Alignment</a>: Inquiring about the alignment of a type or variable.
319 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Inline.html#Inline">Inline</a>: Defining inline functions (as fast as macros).
320 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Alternate-Keywords.html#Alternate%20Keywords">Alternate Keywords</a>:<code>__const__</code>, <code>__asm__</code>, etc., for header files.
321 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Incomplete-Enums.html#Incomplete%20Enums">Incomplete Enums</a>: <code>enum foo;</code>, with details to follow.
322 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Function-Names.html#Function%20Names">Function Names</a>: Printable strings which are the name of the current function.
323 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Unnamed-Fields.html#Unnamed%20Fields">Unnamed Fields</a>: Unnamed struct/union fields within structs/unions.
324 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Attribute-Syntax.html#Attribute%20Syntax">Attribute Syntax</a>: Formal syntax for attributes.
325 </ol><p>
326
327 If you run into GCC extensions which have not been included in any of these
328 lists, please let us know (also including whether or not they work).
329
330
331<!-- _______________________________________________________________________ -->
332</ul><h4><a name="c++-fe"><hr size=0>Known problems with the C++ front-end</h4><ul>
333
John Criswell9d977d52003-10-27 17:41:53 +0000[diff] [blame]334For this release, the C++ front-end is considered to be fully functional but
335of <b>beta</b> quality. It has been tested and works for a number of simple programs that collectively exercise most of the language. Nevertheless, it has not been in use as long as the C front-end. Please report any bugs or problems.<p>
Chris Lattner3d482502003-10-02 04:57:28 +0000[diff] [blame]336
Chris Lattnerd2a74272003-10-27 18:30:37 +0000[diff] [blame]337</ul><b>Bugs</b>:<ul><p>
338
Chris Lattner3d482502003-10-02 04:57:28 +0000[diff] [blame]339<li>The C++ front-end inherits all problems afflicting the <a href="#c-fe">C
340 front-end</a><p>
341
Chris Lattnerd2a74272003-10-27 18:30:37 +0000[diff] [blame]342</ul><b>Notes</b>:<ul><p>
343
Chris Lattner3d482502003-10-02 04:57:28 +0000[diff] [blame]344<li>The C++ front-end is based on a pre-release of the GCC 3.4 C++ parser. This
345parser is significantly more standards compliant (and picky) than prior GCC
346versions. For more information, see the C++ section of the <a
347href="http://gcc.gnu.org/gcc-3.4/changes.html">GCC 3.4 release notes</a>.<p>
348
349<li>Destructors for local objects are not always run when a <tt>longjmp</tt> is
Chris Lattner62495762003-10-02 16:38:05 +0000[diff] [blame]350 performed. In particular, destructors for objects in the <tt>longjmp</tt>ing
Chris Lattner3d482502003-10-02 04:57:28 +0000[diff] [blame]351 function and in the <tt>setjmp</tt> receiver function may not be run.
352 Objects in intervening stack frames will be destroyed however (which is
353 better than most compilers).<p>
354
Chris Lattner62495762003-10-02 16:38:05 +0000[diff] [blame]355<li>The LLVM C++ front-end follows the <a
356 href="http://www.codesourcery.com/cxx-abi">Itanium C++ ABI</a>.
357 This document, which is not Itanium specific, specifies a standard for name
358 mangling, class layout, v-table layout, RTTI formats, and other C++
359 representation issues. Because we use this API, code generated by the LLVM
360 compilers should be binary compatible with machine code generated by other
361 Itanium ABI C++ compilers (such as G++, the Intel and HP compilers, etc).
362 <i>However</i>, the exception handling mechanism used by LLVM is very
363 different from the model used in the Itanium ABI, so <b>exceptions will not
364 interact correctly</b> .
Chris Lattner3d482502003-10-02 04:57:28 +0000[diff] [blame]365
Chris Lattnerd2a74272003-10-27 18:30:37 +0000[diff] [blame]366<li><a href="http://llvm.cs.uiuc.edu/PR11">Code for executing destructors when
367 unwinding is not shared</a> (this is a quality of implementation problem,
368 which does not effect functionality).<p>
Chris Lattner46ecf612003-10-07 22:14:37 +0000[diff] [blame]369
370
Chris Lattner3d482502003-10-02 04:57:28 +0000[diff] [blame]371<!-- _______________________________________________________________________ -->
372</ul><h4><a name="x86-be"><hr size=0>Known problems with the X86 back-end</h4><ul>
373
Chris Lattner46ecf612003-10-07 22:14:37 +0000[diff] [blame]374<li>The X86 code generator <a
Chris Lattnerc4788bb2003-10-08 06:01:38 +0000[diff] [blame]375href="http://llvm.cs.uiuc.edu/PR16">does not currently
Chris Lattner46ecf612003-10-07 22:14:37 +0000[diff] [blame]376support the <tt>unwind</tt> instruction</a>, so code that throws a C++ exception
377or calls the C <tt>longjmp</tt> function will abort.<p>
Chris Lattner3d482502003-10-02 04:57:28 +0000[diff] [blame]378
Chris Lattner3d482502003-10-02 04:57:28 +0000[diff] [blame]379
380<!-- _______________________________________________________________________ -->
381</ul><h4><a name="sparc-be"><hr size=0>Known problems with the Sparc back-end</h4><ul>
382
Chris Lattner46ecf612003-10-07 22:14:37 +0000[diff] [blame]383<li>The Sparc code generator <a
Chris Lattnerc4788bb2003-10-08 06:01:38 +0000[diff] [blame]384href="http://llvm.cs.uiuc.edu/PR15">does not currently
Chris Lattner46ecf612003-10-07 22:14:37 +0000[diff] [blame]385support the <tt>unwind</tt> instruction</a>, so code that throws a C++ exception
386or calls the C <tt>longjmp</tt> function will abort.<p>
Chris Lattner3d482502003-10-02 04:57:28 +0000[diff] [blame]387
388
389<!-- _______________________________________________________________________ -->
390</ul><h4><a name="c-be"><hr size=0>Known problems with the C back-end</h4><ul>
391
392<li>The C back-end produces code that violates the ANSI C Type-Based Alias
393Analysis rules. As such, special options may be necessary to compile the code
394(for example, GCC requires the <tt>-fno-strict-aliasing</tt> option). This
395problem probably cannot be fixed.<p>
396
Chris Lattnera623e482003-10-20 19:05:03 +0000[diff] [blame]397<li><a href="http://llvm.cs.uiuc.edu/PR33">Initializers for global variables</a>
398cannot include special floating point numbers like Not-A-Number or Infinity.<p>
Chris Lattner3d482502003-10-02 04:57:28 +0000[diff] [blame]399
Chris Lattnerc679fbb2003-11-04 20:06:53 +0000[diff] [blame]400<li><a href="http://llvm.cs.uiuc.edu/PR56">Zero arg vararg functions are not
Chris Lattnerb28c3282003-10-24 04:03:19 +0000[diff] [blame]401supported</a>. This should not affect LLVM produced by the C or C++
402frontends.<p>
403
Chris Lattnerc679fbb2003-11-04 20:06:53 +0000[diff] [blame]404<li><a href="http://llvm.cs.uiuc.edu/PR77">Variables in scope of output setjmp
405calls should be volatile</a>. Note that this does not effect correctness on
406many platforms.<p>
407
408<li>The code produces by the C back-end has only been tested with the Sun CC,
409GCC, and Intel compilers. It is possible that it will have to be adjusted to
410support other C compilers.<p>
Chris Lattner3d482502003-10-02 04:57:28 +0000[diff] [blame]411
412
413
414<!-- *********************************************************************** -->
415</ul><table width="100%" bgcolor="#330077" border=0 cellpadding=4 cellspacing=0>
416<tr><td align=center><font color="#EEEEFF" size=+2 face="Georgia,Palatino"><b>
417<a name="additionalinfo">Additional Information
418</b></font></td></tr></table><ul>
419<!-- *********************************************************************** -->
420
421A wide variety of additional information is available on the LLVM web page,
422including mailing lists publications describing algorithms and components
423implemented in LLVM. The web page also contains versions of the API
424documentation which is up-to-date with the CVS version of the source code. You
425can access versions of these documents specific to this release by going into
Chris Lattnera623e482003-10-20 19:05:03 +0000[diff] [blame]426the "<tt>llvm/doc/</tt>" directory in the LLVM tree.<p>
Chris Lattner3d482502003-10-02 04:57:28 +0000[diff] [blame]427
428If you have any questions or comments about LLVM, please feel free to contact us
429via the mailing lists.<p>
430
431
432<!-- *********************************************************************** -->
433</ul>
434<!-- *********************************************************************** -->
435
436<hr><font size-1>
437
Chris Lattnere7525b52003-10-07 21:38:31 +0000[diff] [blame]438Maintained By: <a href="http://llvm.cs.uiuc.edu/">The LLVM Team</a><br>
Chris Lattner3d482502003-10-02 04:57:28 +0000[diff] [blame]439<!-- Created: Wed Oct 1 17:38:54 CDT 2003 -->
440<!-- hhmts start -->
Chris Lattnera7235372003-11-12 04:42:37 +0000[diff] [blame]441Last modified: Tue Nov 11 22:41:53 CST 2003
Chris Lattner3d482502003-10-02 04:57:28 +0000[diff] [blame]442<!-- hhmts end -->
443</body></html>