1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
2 "http://www.w3.org/TR/html4/strict.dtd">
5 <link rel="stylesheet" href="llvm.css" type="text/css">
6 <title>LLVM 1.2 Release Notes</title>
10 <div class="doc_title">
11 LLVM 1.2 Release Notes
15 <li><a href="#intro">Introduction</a></li>
16 <li><a href="#whatsnew">What's New?</a></li>
17 <li><a href="#portability">Portability and Supported Platforms</a></li>
18 <li><a href="#install-instructions">Installation Instructions</a></li>
19 <li><a href="#knownproblems">Known Problems</a>
21 <li><a href="#core">Known problems with the LLVM Core</a>
22 <li><a href="#c-fe">Known problems with the C Front-end</a>
23 <li><a href="#c++-fe">Known problems with the C++ Front-end</a>
24 <li><a href="#x86-be">Known problems with the X86 Back-end</a>
25 <li><a href="#sparc-be">Known problems with the Sparc Back-end</a>
26 <li><a href="#c-be">Known problems with the C back-end</a>
28 <li><a href="#additionalinfo">Additional Information</a></li>
31 <div class="doc_text">
32 <p><b>Written by the <a href="http://llvm.cs.uiuc.edu">LLVM team</a></b><p>
35 <!-- *********************************************************************** -->
36 <div class="doc_section">
37 <a name="intro">Introduction</a>
39 <!-- *********************************************************************** -->
41 <div class="doc_text">
43 <p>This document contains the release notes for the LLVM compiler
44 infrastructure, release 1.2. Here we describe the status of LLVM, including any
45 known problems and bug fixes from the previous release. The most up-to-date
46 version of this document can be found on the <a
47 href="http://llvm.cs.uiuc.edu/releases/1.2/">LLVM 1.2 web site</a>. If you are
48 not reading this on the LLVM web pages, you should probably go there because
49 this document may be updated after the release.</p>
51 <p>For more information about LLVM, including information about potentially more
52 current releases, please check out the <a href="http://llvm.cs.uiuc.edu">main
53 web site</a>. If you have questions or comments, the <a
54 href="http://mail.cs.uiuc.edu/mailman/listinfo/llvmdev">LLVM developer's mailing
55 list</a> is a good place to send them.</p>
57 <p>Note that if you are reading this file from CVS, this document applies
58 to the <i>next</i> release, not the current one. To see the release notes for
59 the current or previous releases, see the <a
60 href="http://llvm.cs.uiuc.edu/releases/">releases page</a>.</p>
64 <!-- *********************************************************************** -->
65 <div class="doc_section">
66 <a name="whatsnew">What's New?</a>
68 <!-- *********************************************************************** -->
70 <div class="doc_text">
72 <p>This is the third public release of the LLVM compiler infrastructure.
75 <p>At this time, LLVM is known to correctly compile and run all C
76 & C++ SPEC CPU2000 benchmarks, the Olden benchmarks, and the Ptrdist
77 benchmarks. It has also been used to compile <b>many</b> other programs. LLVM
78 now also works with a broad variety of C++ programs, though it has still
79 received less testing than the C front-end.
83 <!--=========================================================================-->
84 <div class="doc_subsubsection">
85 This release implements the following new features:
89 <li><a href="SourceLevelDebugging.html">A new LLVM source-level debugger has been started.</a></li>
94 <!--=========================================================================-->
95 <div class="doc_subsubsection">
96 In this release, the following missing features were implemented:
100 <li><a href="http://llvm.cs.uiuc.edu/PR16">Exception handling support in the X86
101 & Sparc native code generators</a></li>
102 <li>The C/C++ front-end now support the GCC <tt>__builtin_return_address</tt> and <tt>__builtin_frame_address</tt> extensions.</li>
106 <!--=========================================================================-->
107 <div class="doc_subsubsection">
108 In this release, the following Quality of Implementation issues were fixed:
113 <li><a href="http://llvm.cs.uiuc.edu/PR135">JIT should lazily initialize global variables</a></li>
114 <li><a href="http://llvm.cs.uiuc.edu/PR192">[X86] X86 Backend never releases memory for machine code structures</a></li>
115 <li><a href="http://llvm.cs.uiuc.edu/PR196">[vmcore] OpaqueType objects memory leak</a></li>
116 <li><a href="http://llvm.cs.uiuc.edu/PR182">[llvmgcc] C front-end does not compile "extern inline" into linkonce</a></li>
117 <li><a href="http://llvm.cs.uiuc.edu/PR73">Bytecode format inconsistent</a></li>
118 <li><a href="http://llvm.cs.uiuc.edu/PR209">[loadvn/inline/scalarrepl] Slow optimizations with extremely large basic blocks</a></li>
119 <li><a href="http://llvm.cs.uiuc.edu/PR224">[asmparser] Really slow parsing of types with complex upreferences</a></li>
120 <li><a href="http://llvm.cs.uiuc.edu/PR205">[llvmgcc] C front-end does not emit 'zeroinitializer' when possible</a></li>
121 <li><a href="http://llvm.cs.uiuc.edu/PR239">LLVM is now much more memory efficient when handling large zero initialized arrays</a></li>
124 <!--=========================================================================-->
125 <div class="doc_subsubsection">
126 LLVM gained several improvements to its build and installation
127 infrastructure in this release. There is now
128 a <tt>autoconf/AutoRegen.sh</tt> script that you can run to rebuild the
129 <tt>configure</tt> script and its associated files
130 (<a href="http://llvm.cs.uiuc.edu/PR105">Bug 105</a>) as well as beta support
131 for "make install" (<a href="http://llvm.cs.uiuc.edu/PR208">Bug 208</a> and
132 <a href="http://llvm.cs.uiuc.edu/PR220">Bug 220</a>) and RPM package generation
133 (<a href="http://llvm.cs.uiuc.edu/PR203">Bug 203</a>).
134 Additionally, in this release, the following build problems were fixed:
138 <li><a href="http://llvm.cs.uiuc.edu/PR210">[build] Makefiles break if C frontend target string has unexpected value</a></li>
139 <li><a href="http://llvm.cs.uiuc.edu/PR214">[build] hard-wired assumption that shared-library extension is ".so"</a></li>
140 <li><A href="http://llvm.cs.uiuc.edu/PR222">make tools-only doesn't make lib/Support</a></li>
143 <!--=========================================================================-->
144 <div class="doc_subsubsection">
145 In this release, the following Code Quality issues were fixed:
149 <li><a href="http://llvm.cs.uiuc.edu/PR187">[loopsimplify] Many pointless phi nodes are created</a></li>
150 <li>The X86 backend didn't generate <tt>fchs</tt> to negate floating point numbers</li>
151 <li>The X86 backend didn't expand memcpy() into the <tt>rep movs</tt> instruction</li>
152 <li><a href="http://llvm.cs.uiuc.edu/PR237">[x86] wierd stack/frame pointer manipulation</a></li>
156 <!--=========================================================================-->
157 <div class="doc_subsubsection">
158 In this release, the following bugs in the previous release were fixed:
161 <p>Bugs in the LLVM Core:</p>
164 <li><a href="http://llvm.cs.uiuc.edu/PR179">[licm] LICM promotes volatile memory
165 locations to registers</a></li>
166 <li><a href="http://llvm.cs.uiuc.edu/PR191">[licm] Memory read after free causes
167 infrequent crash</a></li>
168 <li><a href="http://llvm.cs.uiuc.edu/PR194">[indvars] Induction variable
169 canonicalization always makes 32-bit indvars</a></li>
170 <li><a href="http://llvm.cs.uiuc.edu/PR193">[constantmerge] Merging globals can
171 cause use of invalid pointers!</a></li>
172 <li><a href="http://llvm.cs.uiuc.edu/PR212">[bcreader] Bytecode reader misreads 'long -9223372036854775808'!</a></li>
173 <li><a href="http://llvm.cs.uiuc.edu/bugs/show_bug.cgi?id=174">Tail duplication does not update SSA form correctly.</a></li>
174 <li><a href="http://llvm.cs.uiuc.edu/PR218">VMCore mishandles double -0.0</a></li>
175 <li><a href="http://llvm.cs.uiuc.edu/PR219">[X86] X86 backend code generates -0.0 as +0.0</a></li>
176 <li><a href="http://llvm.cs.uiuc.edu/PR223">[loopsimplify] Loopsimplify incorrectly updates dominator information</a></li>
177 <li><a href="http://llvm.cs.uiuc.edu/PR225">[pruneeh] -pruneeh pass removes invoke instructions it shouldn't</a></li>
178 <li><a href="http://llvm.cs.uiuc.edu/PR228">[sparc] Boolean constants are emitted as true and false</a></li>
179 <li><a href="http://llvm.cs.uiuc.edu/PR235">Tablegen aborts on errors</a></li>
180 <li><a href="http://llvm.cs.uiuc.edu/PR236">[inliner] Error inlining intrinsic calls into invoke instructions</a></li>
185 <p>Bugs in the C/C++ front-end:</p>
188 <li><a href="http://llvm.cs.uiuc.edu/PR186">Need weak linkage on memory
189 management functions in libc runtime to allow them to be overriden</a></li>
190 <li><a href="http://llvm.cs.uiuc.edu/PR202">[llvm-gcc] asserts when an extern inline function is redefined</a></li>
191 <li><a href="http://llvm.cs.uiuc.edu/PR204">[llvmg++] Dynamically initialized constants cannot be marked 'constant'</a></li>
192 <li><a href="http://llvm.cs.uiuc.edu/PR216">[llvmgcc] floating-point unary minus is incorrect for +0.0</a></li>
193 <li><a href="http://llvm.cs.uiuc.edu/PR221">[llvm-gcc] miscompilation of 'X = Y = Z' with aggregate values</a></li>
194 <li><a href="http://llvm.cs.uiuc.edu/PR233">[llvmgcc] Structure copies result in a LOT of code</a></li>
199 <!-- *********************************************************************** -->
200 <div class="doc_section">
201 <a name="portability">Portability and Supported Platforms</a>
203 <!-- *********************************************************************** -->
205 <div class="doc_text">
207 <p>LLVM has been extensively tested on Intel and AMD machines running Red
208 Hat Linux and FreeBSD. It has also been tested on Sun UltraSPARC workstations running Solaris 8.
210 LLVM works on Mac OS X 10.3 and above, but only with the C backend or
211 interpreter (no native backend for the PowerPC is available yet).
212 The core LLVM infrastructure uses "autoconf" for portability, so hopefully we
213 work on more platforms than that. However, it is likely that we
214 missed something and that minor porting is required to get LLVM to work on
215 new platforms. We welcome portability patches and error messages.</p>
219 <!-- *********************************************************************** -->
220 <div class="doc_section">
221 <a name="knownproblems">Known Problems</a>
223 <!-- *********************************************************************** -->
225 <div class="doc_text">
227 <p>This section contains all known problems with the LLVM system, listed by
228 component. As new problems are discovered, they will be added to these
229 sections. If you run into a problem, please check the <a
230 href="http://llvm.cs.uiuc.edu/bugs/">LLVM bug database</a> and submit a bug if
231 there isn't already one.</p>
235 <!-- _______________________________________________________________________ -->
237 </ul><h4><a name="portability"><hr size=0>Portability Problems</h4><ul>
241 <!-- ======================================================================= -->
242 <div class="doc_subsection">
243 <a name="core">Known problems with the LLVM Core</a>
246 <div class="doc_text">
250 <li>In the JIT, <tt>dlsym</tt> on a symbol compiled by the JIT will not
253 <li>The JIT does not use mutexes to protect its internal data structures. As
254 such, execution of a threaded program could cause these data structures to be
257 <li>It is not possible to <tt>dlopen</tt> an LLVM bytecode file in the JIT.</li>
259 <li>Linking in static archive files (.a files) is very slow (there is no symbol
260 table in the archive).</li>
262 <li><a href="http://llvm.cs.uiuc.edu/PR82">LLVM cannot handle structures with
263 more than 256 elements</a>.</li>
267 <a href="http://llvm.cs.uiuc.edu/bugs/show_bug.cgi?id=139">
268 does not link objects/archives in the order specified on the command line.
274 <!-- ======================================================================= -->
275 <div class="doc_subsection">
276 <a name="c-fe">Known problems with the C front-end</a>
279 <!-- _______________________________________________________________________ -->
280 <div class="doc_subsubsection">Bugs</div>
282 <div class="doc_text">
284 <li>C99 Variable sized arrays do not release stack memory when they go out of
285 scope. Thus, the following program may run out of stack space:
287 for (i = 0; i != 1000000; ++i) {
294 Initialization of global union variables can only be done
295 <a href="http://llvm.cs.uiuc.edu/bugs/show_bug.cgi?id=162">with the largest
301 <!-- _______________________________________________________________________ -->
302 <div class="doc_subsubsection">
306 <div class="doc_text">
310 <li>Inline assembly is not yet supported.</li>
312 <li>"long double" is transformed by the front-end into "double". There is no
313 support for floating point data types of any size other than 32 and 64
316 <li>The following Unix system functionality has not been tested and may not
319 <li><tt>sigsetjmp</tt>, <tt>siglongjmp</tt> - These are not turned into the
320 appropriate <tt>invoke</tt>/<tt>unwind</tt> instructions. Note that
321 <tt>setjmp</tt> and <tt>longjmp</tt> <em>are</em> compiled correctly.
322 <li><tt>getcontext</tt>, <tt>setcontext</tt>, <tt>makecontext</tt>
323 - These functions have not been tested.
326 <li>Although many GCC extensions are supported, some are not. In particular,
327 the following extensions are known to <b>not be</b> supported:
329 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Local-Labels.html#Local%20Labels">Local Labels</a>: Labels local to a block.</li>
330 <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.</li>
331 <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.</li>
332 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Constructing-Calls.html#Constructing%20Calls">Constructing Calls</a>: Dispatching a call to another function.</li>
333 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Extended-Asm.html#Extended%20Asm">Extended Asm</a>: Assembler instructions with C expressions as operands.</li>
334 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Constraints.html#Constraints">Constraints</a>: Constraints for asm operands.</li>
335 <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.</li>
336 <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.</li>
337 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Vector-Extensions.html#Vector%20Extensions">Vector Extensions</a>: Using vector instructions through built-in functions.</li>
338 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Target-Builtins.html#Target%20Builtins">Target Builtins</a>: Built-in functions specific to particular targets.</li>
339 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Thread-Local.html#Thread-Local">Thread-Local</a>: Per-thread variables.</li>
340 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Pragmas.html#Pragmas">Pragmas</a>: Pragmas accepted by GCC.</li>
343 <p>The following GCC extensions are <b>partially</b> supported. An ignored
344 attribute means that the LLVM compiler ignores the presence of the attribute,
345 but the code should still work. An unsupported attribute is one which is
346 ignored by the LLVM compiler and will cause a different interpretation of
350 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Variable-Length.html#Variable%20Length">Variable Length</a>:
351 Arrays whose length is computed at run time.<br>
352 Supported, but allocated stack space is not freed until the function returns (noted above).</li>
354 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Function-Attributes.html#Function%20Attributes">Function Attributes</a>:
356 Declaring that functions have no side effects or that they can never
359 <b>Supported:</b> <tt>format</tt>, <tt>format_arg</tt>, <tt>non_null</tt>,
360 <tt>constructor</tt>, <tt>destructor</tt>, <tt>unused</tt>,
361 <tt>deprecated</tt>, <tt>warn_unused_result</tt>, <tt>weak</tt><br>
363 <b>Ignored:</b> <tt>noreturn</tt>, <tt>noinline</tt>,
364 <tt>always_inline</tt>, <tt>pure</tt>, <tt>const</tt>, <tt>nothrow</tt>,
365 <tt>malloc</tt>, <tt>no_instrument_function</tt>, <tt>cdecl</tt><br>
367 <b>Unsupported:</b> <tt>used</tt>, <tt>section</tt>, <tt>alias</tt>,
368 <tt>visibility</tt>, <tt>regparm</tt>, <tt>stdcall</tt>,
369 <tt>fastcall</tt>, all other target specific attributes</li>
371 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Variable-Attributes.html#Variable%20Attributes">Variable Attributes</a>:
372 Specifying attributes of variables.<br>
373 <b>Supported:</b> <tt>cleanup</tt>, <tt>common</tt>, <tt>nocommon</tt>,
374 <tt>deprecated</tt>, <tt>transparent_union</tt>,
375 <tt>unused</tt>, <tt>weak</tt><br>
377 <b>Unsupported:</b> <tt>aligned</tt>, <tt>mode</tt>, <tt>packed</tt>,
378 <tt>section</tt>, <tt>shared</tt>, <tt>tls_model</tt>,
379 <tt>vector_size</tt>, <tt>dllimport</tt>,
380 <tt>dllexport</tt>, all target specific attributes.</li>
382 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Type-Attributes.html#Type%20Attributes">Type Attributes</a>: Specifying attributes of types.<br>
383 <b>Supported:</b> <tt>transparent_union</tt>, <tt>unused</tt>,
384 <tt>deprecated</tt>, <tt>may_alias</tt><br>
386 <b>Unsupported:</b> <tt>aligned</tt>, <tt>packed</tt>,
387 all target specific attributes.</li>
389 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Other-Builtins.html#Other%20Builtins">Other Builtins</a>:
390 Other built-in functions.<br>
391 We support all builtins which have a C language equivalent (e.g.,
392 <tt>__builtin_cos</tt>), <tt>__builtin_alloca</tt>,
393 <tt>__builtin_types_compatible_p</tt>, <tt>__builtin_choose_expr</tt>,
394 <tt>__builtin_constant_p</tt>, and <tt>__builtin_expect</tt> (ignored).</li>
398 <p>The following extensions <b>are</b> known to be supported:</p>
401 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Statement-Exprs.html#Statement%20Exprs">Statement Exprs</a>: Putting statements and declarations inside expressions.</li>
402 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Typeof.html#Typeof">Typeof</a>: <code>typeof</code>: referring to the type of an expression.</li>
403 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Lvalues.html#Lvalues">Lvalues</a>: Using <code>?:</code>, "<code>,</code>" and casts in lvalues.</li>
404 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Conditionals.html#Conditionals">Conditionals</a>: Omitting the middle operand of a <code>?:</code> expression.</li>
405 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Long-Long.html#Long%20Long">Long Long</a>: Double-word integers.</li>
406 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Complex.html#Complex">Complex</a>: Data types for complex numbers.</li>
407 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Hex-Floats.html#Hex%20Floats">Hex Floats</a>:Hexadecimal floating-point constants.</li>
408 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Zero-Length.html#Zero%20Length">Zero Length</a>: Zero-length arrays.</li>
409 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Empty-Structures.html#Empty%20Structures">Empty Structures</a>: Structures with no members.</li>
410 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Variadic-Macros.html#Variadic%20Macros">Variadic Macros</a>: Macros with a variable number of arguments.</li>
411 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Escaped-Newlines.html#Escaped%20Newlines">Escaped Newlines</a>: Slightly looser rules for escaped newlines.</li>
412 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Subscripting.html#Subscripting">Subscripting</a>: Any array can be subscripted, even if not an lvalue.</li>
413 <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.</li>
414 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Initializers.html#Initializers">Initializers</a>: Non-constant initializers.</li>
415 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Compound-Literals.html#Compound%20Literals">Compound Literals</a>: Compound literals give structures, unions,
416 or arrays as values.</li>
417 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Designated-Inits.html#Designated%20Inits">Designated Inits</a>: Labeling elements of initializers.</li>
418 <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.</li>
419 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Case-Ranges.html#Case%20Ranges">Case Ranges</a>: `case 1 ... 9' and such.</li>
420 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Mixed-Declarations.html#Mixed%20Declarations">Mixed Declarations</a>: Mixing declarations and code.</li>
421 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Function-Prototypes.html#Function%20Prototypes">Function Prototypes</a>: Prototype declarations and old-style definitions.</li>
422 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/C---Comments.html#C++%20Comments">C++ Comments</a>: C++ comments are recognized.</li>
423 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Dollar-Signs.html#Dollar%20Signs">Dollar Signs</a>: Dollar sign is allowed in identifiers.</li>
424 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Character-Escapes.html#Character%20Escapes">Character Escapes</a>: <code>\e</code> stands for the character <ESC>.</li>
425 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Alignment.html#Alignment">Alignment</a>: Inquiring about the alignment of a type or variable.</li>
426 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Inline.html#Inline">Inline</a>: Defining inline functions (as fast as macros).</li>
427 <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.</li>
428 <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.</li>
429 <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.</li>
430 <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.</li>
431 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Unnamed-Fields.html#Unnamed%20Fields">Unnamed Fields</a>: Unnamed struct/union fields within structs/unions.</li>
432 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Attribute-Syntax.html#Attribute%20Syntax">Attribute Syntax</a>: Formal syntax for attributes.</li>
437 <p>If you run into GCC extensions which have not been included in any of these
438 lists, please let us know (also including whether or not they work).</p>
442 <!-- ======================================================================= -->
443 <div class="doc_subsection">
444 <a name="c++-fe">Known problems with the C++ front-end</a>
447 <div class="doc_text">
449 <p>For this release, the C++ front-end is considered to be fully functional but
450 has not been tested as thoroughly as the C front-end. It has been tested and
451 works for a number of non-trivial programs, but there may be lurking bugs.
452 Please report any bugs or problems.</p>
456 <!-- _______________________________________________________________________ -->
457 <div class="doc_subsubsection">Bugs</div>
459 <div class="doc_text">
462 <li>The C++ front-end inherits all problems afflicting the <a href="#c-fe">C
467 <!-- _______________________________________________________________________ -->
468 <div class="doc_subsubsection">
472 <div class="doc_text">
476 <li>The C++ front-end is based on a pre-release of the GCC 3.4 C++ parser. This
477 parser is significantly more standards compliant (and picky) than prior GCC
478 versions. For more information, see the C++ section of the <a
479 href="http://gcc.gnu.org/gcc-3.4/changes.html">GCC 3.4 release notes</a>.</li>
481 <li>Destructors for local objects are not always run when a <tt>longjmp</tt> is
482 performed. In particular, destructors for objects in the <tt>longjmp</tt>ing
483 function and in the <tt>setjmp</tt> receiver function may not be run.
484 Objects in intervening stack frames will be destroyed, however (which is
485 better than most compilers).</li>
487 <li>The LLVM C++ front-end follows the <a
488 href="http://www.codesourcery.com/cxx-abi">Itanium C++ ABI</a>.
489 This document, which is not Itanium specific, specifies a standard for name
490 mangling, class layout, v-table layout, RTTI formats, and other C++
491 representation issues. Because we use this API, code generated by the LLVM
492 compilers should be binary compatible with machine code generated by other
493 Itanium ABI C++ compilers (such as G++, the Intel and HP compilers, etc).
494 <i>However</i>, the exception handling mechanism used by LLVM is very
495 different from the model used in the Itanium ABI, so <b>exceptions will not
496 interact correctly</b>. </li>
502 <!-- ======================================================================= -->
503 <div class="doc_subsection">
504 <a name="x86-be">Known problems with the X86 back-end</a>
507 <div class="doc_text">
515 <!-- ======================================================================= -->
516 <div class="doc_subsection">
517 <a name="sparc-be">Known problems with the Sparc back-end</a>
520 <div class="doc_text">
528 <!-- ======================================================================= -->
529 <div class="doc_subsection">
530 <a name="c-be">Known problems with the C back-end</a>
533 <div class="doc_text">
537 <li>The C back-end produces code that violates the ANSI C Type-Based Alias
538 Analysis rules. As such, special options may be necessary to compile the code
539 (for example, GCC requires the <tt>-fno-strict-aliasing</tt> option). This
540 problem probably cannot be fixed.</li>
542 <li><a href="http://llvm.cs.uiuc.edu/PR33">Initializers for global variables</a>
543 cannot include special floating point numbers like Not-A-Number or
546 <li><a href="http://llvm.cs.uiuc.edu/PR56">Zero arg vararg functions are not
547 supported</a>. This should not affect LLVM produced by the C or C++
554 <!-- *********************************************************************** -->
555 <div class="doc_section">
556 <a name="additionalinfo">Additional Information</a>
558 <!-- *********************************************************************** -->
560 <div class="doc_text">
562 <p>A wide variety of additional information is available on the LLVM web page,
563 including mailing lists and publications describing algorithms and components
564 implemented in LLVM. The web page also contains versions of the API
565 documentation which is up-to-date with the CVS version of the source code. You
566 can access versions of these documents specific to this release by going into
567 the "<tt>llvm/doc/</tt>" directory in the LLVM tree.</p>
569 <p>If you have any questions or comments about LLVM, please feel free to contact
570 us via the <a href="http://mail.cs.uiuc.edu/mailman/listinfo/llvmdev">mailing
575 <!-- *********************************************************************** -->
579 <a href="http://jigsaw.w3.org/css-validator/check/referer"><img
580 src="http://jigsaw.w3.org/css-validator/images/vcss" alt="Valid CSS!"></a>
581 <a href="http://validator.w3.org/check/referer"><img
582 src="http://www.w3.org/Icons/valid-html401" alt="Valid HTML 4.01!" /></a>
584 <a href="http://llvm.cs.uiuc.edu">The LLVM Compiler Infrastructure</a><br>
585 Last modified: $Date$