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.3 Release Notes</title>
10 <div class="doc_title">LLVM 1.3 Release Notes</div>
13 <li><a href="#intro">Introduction</a></li>
14 <li><a href="#whatsnew">What's New?</a></li>
15 <li><a href="GettingStarted.html">Installation Instructions</a></li>
16 <li><a href="#portability">Portability and Supported Platforms</a></li>
17 <li><a href="#knownproblems">Known Problems</a>
19 <li><a href="#experimental">Experimental features included in this
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.3. 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.3/">LLVM 1.3 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">
73 This is the fourth public release of the LLVM compiler infrastructure. This
74 release primarily improves the <a href="#codequality">performance of the
75 code</a> produced by all aspects of the LLVM compiler and adds some <a
76 href="#newfeatures">new features</a>, though it does <a href="#bugfix">fix a few
81 At this time, LLVM is known to correctly compile and run all C & C++ SPEC
82 CPU2000 benchmarks, the Olden benchmarks, and the Ptrdist benchmarks. It has
83 also been used to compile <b>many</b> other programs. LLVM now also works with
84 a broad variety of C++ programs, though it has still received less testing than
88 <!--=========================================================================-->
89 <div class="doc_subsubsection">
90 <a name="newfeatures">This release implements the following new features:</a>
94 <li>The LLVM <a href="LangRef.html#i_select"><tt>select</tt></a> instruction is
95 now fully implemented and supported by all transformations, native code
96 generators, and the interpreter.</li>
97 <li>Bugpoint can now narrow down code-generation bugs to a loop nest, where
98 before it could only narrow them down to a function being miscompiled.</li>
99 <li><a href="http://llvm.cs.uiuc.edu/PR40">Bugpoint can now debug arbitrary
100 modes of llc</a> and lli, by passing them command line flags (e.g.,
101 <tt>-regalloc=linearscan</tt>, <tt>-enable-correct-eh-support</tt>, etc.) </li>
102 <li>The Control Flow Graph in the native code generators is no longer
103 constrained to be the same as the CFG for the LLVM input code.</li>
104 <li>The LLVM induction variable analysis routines have been rewritten.</li>
105 <li>LLVM now has new loop unrolling and loop unswitching passes.</li>
106 <li>The induction variable substitution pass performs linear function test
107 replacement and exit value replacement optimizations.</li>
111 <!--=========================================================================-->
112 <div class="doc_subsubsection">
113 In this release, the following missing features were implemented:
117 <li><a href="http://llvm.cs.uiuc.edu/PR82">LLVM cannot handle structures with
118 more than 256 elements</a></li>
119 <li><a href="http://llvm.cs.uiuc.edu/PR38">[bugpoint] External functions used in
120 non-instruction entities, such as global constant initializer</a></li>
121 <li><a href="http://llvm.cs.uiuc.edu/PR290">Bugpoint doesn't support
122 uses of external fns by immediate constant exprs</a></li>
126 <!--=========================================================================-->
127 <div class="doc_subsubsection">
128 <a name="qualityofimp">In this release, the following Quality of Implementation
129 issues were fixed:</a>
133 <li><a href="http://llvm.cs.uiuc.edu/PR305">LLVM tools will happily spew
134 bytecode onto your terminal</a></li>
135 <li><a href="http://llvm.cs.uiuc.edu/PR329">[llvmgcc] type names are not emitted for structure typedefs</a></li>
138 <!--=========================================================================-->
139 <div class="doc_subsubsection">
140 In this release, the following build problems were fixed:
144 <li><a href="http://llvm.cs.uiuc.edu/PR301">Minor configure bugs with -disable/enable-povray and -disable-spec</a></li>
145 <li><a href="http://llvm.cs.uiuc.edu/PR289">shell scripts output by gccld don't work if you change PATH</a></li>
148 <!--=========================================================================-->
149 <div class="doc_subsubsection">
150 <a name="codequality">This release includes the following Code Quality
155 <li>Fixed: <a href="http://llvm.cs.uiuc.edu/PR309">[vmcore] Code quality problem
156 due to long operand of getelementptr</a></li>
158 <li>The X86 backend now generates substantially better code for 64-bit integer
159 and floating point operations.</li>
161 <li>The -inline pass no longer inlines mutually recursive functions until it
162 hits the inlining threshold.</li>
164 <li>The -inline pass no longer misses obvious inlining opportunities just
165 because the callee eventually calls into an external function.</li>
167 <li>The -simplifycfg pass can now "if convert" simple statements into the new
168 <tt>select</tt> instruction.</li>
170 <li>The -loopsimplify pass can now break <a
171 href="http://llvm.cs.uiuc.edu/PR35">natural loops with multiple backedges</a>
172 into multiple nested loops. This enables a variety of subsequent
175 <li>The -adce pass can now eliminate calls to functions that do not not write to
178 <li>The link-time optimizer now runs the -prune-eh pass (to remove unused
179 exception handlers).</li>
181 <li>The -simplifycfg pass can now eliminate simple correlated branches (such as
182 "<tt>if (A < B && A < B)</tt>", and can turn short-circuiting
183 operators into the strict versions when useful (such as "<tt>if (A < B || A
184 > C)</tt>" into "<tt>if (A < B | A > C)</tt>"</li>
186 <li>LLVM now has infrastructure for (simple and sparse conditional) constant
187 propagation of function calls. It currently supports a few math library
188 functions like sqrt/sin/cos/etc.</li>
192 <!--=========================================================================-->
193 <div class="doc_subsubsection">
194 <a name="bugfix">In this release, the following bugs in the previous release
198 <p>Bugs in the LLVM Core:</p>
201 <li><a href="http://llvm.cs.uiuc.edu/PR330">[vmcore] Linker causes erroneous
203 <li><a href="http://llvm.cs.uiuc.edu/PR306">[loopsimplify] Loop simplify
204 incorrectly updates dominator information</a></li>
205 <li><a href="http://llvm.cs.uiuc.edu/PR310">[tailduplicate] DemoteRegToStack
206 breaks SSA form</a></li>
207 <li><a href="http://llvm.cs.uiuc.edu/PR313">[X86] JIT miscompiles unsigned short
208 to floating point cast</a></li>
209 <li><a href="http://llvm.cs.uiuc.edu/PR332">[adce] Crash handling unreachable code that unwinds</a></li>
210 <li><a href="http://llvm.cs.uiuc.edu/PR333">[sparc] LLC can't emit 2 functions of
211 the same name, both having constant pools</a></li>
214 <p>Bugs in the C/C++ front-end:</p>
217 <li><a href="http://llvm.cs.uiuc.edu/PR326">[llvmgcc] Crash on use of undeclared enum type</a></li>
218 <li><a href="http://llvm.cs.uiuc.edu/PR298">[llvmgcc] Variable length array indexing miscompiled</a></li>
223 <!-- *********************************************************************** -->
224 <div class="doc_section">
225 <a name="portability">Portability and Supported Platforms</a>
227 <!-- *********************************************************************** -->
229 <div class="doc_text">
231 <p>LLVM has been extensively tested on Intel and AMD machines running Red Hat
232 Linux. It has also been tested under FreeBSD, and on Sun UltraSPARC
233 workstations running Solaris 8. Additionally, LLVM works on Mac OS X 10.3 and
234 above, but only with the C backend and interpreter; no native machine-code
235 generator for the PowerPC is available yet.</p>
237 <p>The core LLVM infrastructure uses
238 <a href="http://www.gnu.org/software/autoconf/">GNU autoconf</a> to adapt itself
239 to the machine and operating system on which it is built. However, minor
240 porting may be required to get LLVM to work on new platforms. We welcome your
241 portability patches and reports of successful builds or error messages.</p>
245 <!--=========================================================================-->
246 <div class="doc_subsection">
247 In this release, the following portability problems were fixed:
251 <li><a href="http://llvm.cs.uiuc.edu/PR304">warnings compiling Stacker compiler on Mac OS X</a></li>
252 <li><a href="http://llvm.cs.uiuc.edu/PR308">Archive file reader doesn't understand abbreviated names in headers</a></li>
255 <!-- *********************************************************************** -->
256 <div class="doc_section">
257 <a name="knownproblems">Known Problems</a>
259 <!-- *********************************************************************** -->
261 <div class="doc_text">
263 <p>This section contains all known problems with the LLVM system, listed by
264 component. As new problems are discovered, they will be added to these
265 sections. If you run into a problem, please check the <a
266 href="http://llvm.cs.uiuc.edu/bugs/">LLVM bug database</a> and submit a bug if
267 there isn't already one.</p>
271 <!-- ======================================================================= -->
272 <div class="doc_subsection">
273 <a name="experimental">Experimental features included with this release</a>
276 <div class="doc_text">
279 The following components of this LLVM release are either untested, known to be
280 broken or unreliable, or are in early development. These components should not
281 be relied on, and bugs should not be filed against them, but they may be useful
282 to some people. In particular, if you would like to work on one of these
283 components, please contact us on the llvmdev list.
287 <li>The following passes are incomplete or buggy: <tt>-pgmdep, -memdep,
288 -ipmodref, -sortstructs, -swapstructs, -cee</tt></li>
290 <li>The <tt>-pre</tt> pass is incomplete (there are cases it doesn't handle that
291 it should) and not thoroughly tested.</li>
292 <li>The <tt>llvm-ar</tt> tool is incomplete and probably buggy.</li>
293 <li>The <tt>llvm-db</tt> tool is in a very early stage of development.</li>
298 <!-- ======================================================================= -->
299 <div class="doc_subsection">
300 <a name="core">Known problems with the LLVM Core</a>
303 <div class="doc_text">
307 <li>In the JIT, <tt>dlsym</tt> on a symbol compiled by the JIT will not
310 <li>The JIT does not use mutexes to protect its internal data structures. As
311 such, execution of a threaded program could cause these data structures to be
314 <li>It is not possible to <tt>dlopen</tt> an LLVM bytecode file in the JIT.</li>
316 <li>Linking in static archive files (.a files) is very slow (there is no symbol
317 table in the archive).</li>
319 <li>The gccld program <a href="http://llvm.cs.uiuc.edu/PR139">does not link
320 objects/archives in the order specified on the command line.</a></li>
322 <li><a href="http://llvm.cs.uiuc.edu/PR240">The lower-invoke pass does not mark
323 values live across a setjmp as volatile</a>. This missing feature only affects
324 targets whose setjmp/longjmp libraries do not save and restore the entire
329 <!-- ======================================================================= -->
330 <div class="doc_subsection">
331 <a name="c-fe">Known problems with the C front-end</a>
334 <!-- _______________________________________________________________________ -->
335 <div class="doc_subsubsection">Bugs</div>
337 <div class="doc_text">
339 <li>C99 Variable sized arrays do not release stack memory when they go out of
340 scope. Thus, the following program may run out of stack space:
342 for (i = 0; i != 1000000; ++i) {
349 Initialization of global union variables can only be done
350 <a href="http://llvm.cs.uiuc.edu/bugs/show_bug.cgi?id=162">with the largest
354 <li><a href="http://llvm.cs.uiuc.edu/PR244">[llvm-gcc] Error when an implicitly
355 external function is re-declared as static</a></li>
360 <!-- _______________________________________________________________________ -->
361 <div class="doc_subsubsection">
365 <div class="doc_text">
369 <li>Inline assembly is not yet supported.</li>
371 <li>"long double" is transformed by the front-end into "double". There is no
372 support for floating point data types of any size other than 32 and 64
375 <li>The following Unix system functionality has not been tested and may not
378 <li><tt>sigsetjmp</tt>, <tt>siglongjmp</tt> - These are not turned into the
379 appropriate <tt>invoke</tt>/<tt>unwind</tt> instructions. Note that
380 <tt>setjmp</tt> and <tt>longjmp</tt> <em>are</em> compiled correctly.
381 <li><tt>getcontext</tt>, <tt>setcontext</tt>, <tt>makecontext</tt>
382 - These functions have not been tested.
385 <li>Although many GCC extensions are supported, some are not. In particular,
386 the following extensions are known to <b>not be</b> supported:
388 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Local-Labels.html#Local%20Labels">Local Labels</a>: Labels local to a block.</li>
389 <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>
390 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Constructing-Calls.html#Constructing%20Calls">Constructing Calls</a>: Dispatching a call to another function.</li>
391 <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>
392 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Constraints.html#Constraints">Constraints</a>: Constraints for asm operands.</li>
393 <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>
394 <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>
395 <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>
396 <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>
397 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Thread-Local.html#Thread-Local">Thread-Local</a>: Per-thread variables.</li>
398 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Pragmas.html#Pragmas">Pragmas</a>: Pragmas accepted by GCC.</li>
401 <p>The following GCC extensions are <b>partially</b> supported. An ignored
402 attribute means that the LLVM compiler ignores the presence of the attribute,
403 but the code should still work. An unsupported attribute is one which is
404 ignored by the LLVM compiler and will cause a different interpretation of
408 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Variable-Length.html#Variable%20Length">Variable Length</a>:
409 Arrays whose length is computed at run time.<br>
410 Supported, but allocated stack space is not freed until the function returns (noted above).</li>
412 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Function-Attributes.html#Function%20Attributes">Function Attributes</a>:
414 Declaring that functions have no side effects or that they can never
417 <b>Supported:</b> <tt>format</tt>, <tt>format_arg</tt>, <tt>non_null</tt>,
418 <tt>constructor</tt>, <tt>destructor</tt>, <tt>unused</tt>,
419 <tt>deprecated</tt>, <tt>warn_unused_result</tt>, <tt>weak</tt><br>
421 <b>Ignored:</b> <tt>noreturn</tt>, <tt>noinline</tt>,
422 <tt>always_inline</tt>, <tt>pure</tt>, <tt>const</tt>, <tt>nothrow</tt>,
423 <tt>malloc</tt>, <tt>no_instrument_function</tt>, <tt>cdecl</tt><br>
425 <b>Unsupported:</b> <tt>used</tt>, <tt>section</tt>, <tt>alias</tt>,
426 <tt>visibility</tt>, <tt>regparm</tt>, <tt>stdcall</tt>,
427 <tt>fastcall</tt>, all other target specific attributes</li>
429 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Variable-Attributes.html#Variable%20Attributes">Variable Attributes</a>:
430 Specifying attributes of variables.<br>
431 <b>Supported:</b> <tt>cleanup</tt>, <tt>common</tt>, <tt>nocommon</tt>,
432 <tt>deprecated</tt>, <tt>transparent_union</tt>,
433 <tt>unused</tt>, <tt>weak</tt><br>
435 <b>Unsupported:</b> <tt>aligned</tt>, <tt>mode</tt>, <tt>packed</tt>,
436 <tt>section</tt>, <tt>shared</tt>, <tt>tls_model</tt>,
437 <tt>vector_size</tt>, <tt>dllimport</tt>,
438 <tt>dllexport</tt>, all target specific attributes.</li>
440 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Type-Attributes.html#Type%20Attributes">Type Attributes</a>: Specifying attributes of types.<br>
441 <b>Supported:</b> <tt>transparent_union</tt>, <tt>unused</tt>,
442 <tt>deprecated</tt>, <tt>may_alias</tt><br>
444 <b>Unsupported:</b> <tt>aligned</tt>, <tt>packed</tt>,
445 all target specific attributes.</li>
447 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Other-Builtins.html#Other%20Builtins">Other Builtins</a>:
448 Other built-in functions.<br>
449 We support all builtins which have a C language equivalent (e.g.,
450 <tt>__builtin_cos</tt>), <tt>__builtin_alloca</tt>,
451 <tt>__builtin_types_compatible_p</tt>, <tt>__builtin_choose_expr</tt>,
452 <tt>__builtin_constant_p</tt>, and <tt>__builtin_expect</tt> (ignored).</li>
456 <p>The following extensions <b>are</b> known to be supported:</p>
459 <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>
460 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Statement-Exprs.html#Statement%20Exprs">Statement Exprs</a>: Putting statements and declarations inside expressions.</li>
461 <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>
462 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Lvalues.html#Lvalues">Lvalues</a>: Using <code>?:</code>, "<code>,</code>" and casts in lvalues.</li>
463 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Conditionals.html#Conditionals">Conditionals</a>: Omitting the middle operand of a <code>?:</code> expression.</li>
464 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Long-Long.html#Long%20Long">Long Long</a>: Double-word integers.</li>
465 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Complex.html#Complex">Complex</a>: Data types for complex numbers.</li>
466 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Hex-Floats.html#Hex%20Floats">Hex Floats</a>:Hexadecimal floating-point constants.</li>
467 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Zero-Length.html#Zero%20Length">Zero Length</a>: Zero-length arrays.</li>
468 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Empty-Structures.html#Empty%20Structures">Empty Structures</a>: Structures with no members.</li>
469 <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>
470 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Escaped-Newlines.html#Escaped%20Newlines">Escaped Newlines</a>: Slightly looser rules for escaped newlines.</li>
471 <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>
472 <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>
473 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Initializers.html#Initializers">Initializers</a>: Non-constant initializers.</li>
474 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Compound-Literals.html#Compound%20Literals">Compound Literals</a>: Compound literals give structures, unions,
475 or arrays as values.</li>
476 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Designated-Inits.html#Designated%20Inits">Designated Inits</a>: Labeling elements of initializers.</li>
477 <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>
478 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Case-Ranges.html#Case%20Ranges">Case Ranges</a>: `case 1 ... 9' and such.</li>
479 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Mixed-Declarations.html#Mixed%20Declarations">Mixed Declarations</a>: Mixing declarations and code.</li>
480 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Function-Prototypes.html#Function%20Prototypes">Function Prototypes</a>: Prototype declarations and old-style definitions.</li>
481 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/C---Comments.html#C++%20Comments">C++ Comments</a>: C++ comments are recognized.</li>
482 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Dollar-Signs.html#Dollar%20Signs">Dollar Signs</a>: Dollar sign is allowed in identifiers.</li>
483 <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>
484 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Alignment.html#Alignment">Alignment</a>: Inquiring about the alignment of a type or variable.</li>
485 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Inline.html#Inline">Inline</a>: Defining inline functions (as fast as macros).</li>
486 <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>
487 <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>
488 <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>
489 <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>
490 <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>
491 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Attribute-Syntax.html#Attribute%20Syntax">Attribute Syntax</a>: Formal syntax for attributes.</li>
496 <p>If you run into GCC extensions which have not been included in any of these
497 lists, please let us know (also including whether or not they work).</p>
501 <!-- ======================================================================= -->
502 <div class="doc_subsection">
503 <a name="c++-fe">Known problems with the C++ front-end</a>
506 <div class="doc_text">
508 <p>For this release, the C++ front-end is considered to be fully functional but
509 has not been tested as thoroughly as the C front-end. It has been tested and
510 works for a number of non-trivial programs, but there may be lurking bugs.
511 Please report any bugs or problems.</p>
515 <!-- _______________________________________________________________________ -->
516 <div class="doc_subsubsection">Bugs</div>
518 <div class="doc_text">
521 <li>The C++ front-end inherits all problems afflicting the <a href="#c-fe">C
526 <!-- _______________________________________________________________________ -->
527 <div class="doc_subsubsection">
531 <div class="doc_text">
535 <li>The C++ front-end is based on a pre-release of the GCC 3.4 C++ parser. This
536 parser is significantly more standards compliant (and picky) than prior GCC
537 versions. For more information, see the C++ section of the <a
538 href="http://gcc.gnu.org/gcc-3.4/changes.html">GCC 3.4 release notes</a>.</li>
540 <li>Destructors for local objects are not always run when a <tt>longjmp</tt> is
541 performed. In particular, destructors for objects in the <tt>longjmp</tt>ing
542 function and in the <tt>setjmp</tt> receiver function may not be run.
543 Objects in intervening stack frames will be destroyed, however (which is
544 better than most compilers).</li>
546 <li>The LLVM C++ front-end follows the <a
547 href="http://www.codesourcery.com/cxx-abi">Itanium C++ ABI</a>.
548 This document, which is not Itanium specific, specifies a standard for name
549 mangling, class layout, v-table layout, RTTI formats, and other C++
550 representation issues. Because we use this API, code generated by the LLVM
551 compilers should be binary compatible with machine code generated by other
552 Itanium ABI C++ compilers (such as G++, the Intel and HP compilers, etc).
553 <i>However</i>, the exception handling mechanism used by LLVM is very
554 different from the model used in the Itanium ABI, so <b>exceptions will not
555 interact correctly</b>. </li>
561 <!-- ======================================================================= -->
562 <div class="doc_subsection">
563 <a name="x86-be">Known problems with the X86 back-end</a>
566 <div class="doc_text">
574 <!-- ======================================================================= -->
575 <div class="doc_subsection">
576 <a name="sparc-be">Known problems with the Sparc back-end</a>
579 <div class="doc_text">
582 <li>There are several programs in the LLVM testsuite that the Sparc code generator is known to miscompile.</li>
587 <!-- ======================================================================= -->
588 <div class="doc_subsection">
589 <a name="c-be">Known problems with the C back-end</a>
592 <div class="doc_text">
596 <li>The C back-end produces code that violates the ANSI C Type-Based Alias
597 Analysis rules. As such, special options may be necessary to compile the code
598 (for example, GCC requires the <tt>-fno-strict-aliasing</tt> option). This
599 problem probably cannot be fixed.</li>
601 <li><a href="http://llvm.cs.uiuc.edu/PR33">Initializers for global variables</a>
602 cannot include special floating point numbers like Not-A-Number or
605 <li><a href="http://llvm.cs.uiuc.edu/PR56">Zero arg vararg functions are not
606 supported</a>. This should not affect LLVM produced by the C or C++
613 <!-- *********************************************************************** -->
614 <div class="doc_section">
615 <a name="additionalinfo">Additional Information</a>
617 <!-- *********************************************************************** -->
619 <div class="doc_text">
621 <p>A wide variety of additional information is available on the LLVM web page,
622 including mailing lists and publications describing algorithms and components
623 implemented in LLVM. The web page also contains versions of the API
624 documentation which is up-to-date with the CVS version of the source code. You
625 can access versions of these documents specific to this release by going into
626 the "<tt>llvm/doc/</tt>" directory in the LLVM tree.</p>
628 <p>If you have any questions or comments about LLVM, please feel free to contact
629 us via the <a href="http://mail.cs.uiuc.edu/mailman/listinfo/llvmdev">mailing
634 <!-- *********************************************************************** -->
638 <a href="http://jigsaw.w3.org/css-validator/check/referer"><img
639 src="http://jigsaw.w3.org/css-validator/images/vcss" alt="Valid CSS!"></a>
640 <a href="http://validator.w3.org/check/referer"><img
641 src="http://www.w3.org/Icons/valid-html401" alt="Valid HTML 4.01!" /></a>
643 <a href="http://llvm.cs.uiuc.edu">The LLVM Compiler Infrastructure</a><br>
644 Last modified: $Date$