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.4 Release Notes</title>
10 <div class="doc_title">LLVM 1.4 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="#sparcv9-be">Known problems with the SparcV9 Back-end</a>
26 <li><a href="#ppc-be">Known problems with the PowerPC Back-end</a>
27 <li><a href="#c-be">Known problems with the C back-end</a>
29 <li><a href="#additionalinfo">Additional Information</a></li>
32 <div class="doc_author">
33 <p>Written by the <a href="http://llvm.cs.uiuc.edu">LLVM team</a><p>
36 <!-- *********************************************************************** -->
37 <div class="doc_section">
38 <a name="intro">Introduction</a>
40 <!-- *********************************************************************** -->
42 <div class="doc_text">
44 <p>This document contains the release notes for the LLVM compiler
45 infrastructure, release 1.4. Here we describe the status of LLVM, including any
46 known problems and bug fixes from the previous release. The most up-to-date
47 version of this document can be found on the <a
48 href="http://llvm.cs.uiuc.edu/releases/1.4/">LLVM 1.4 web site</a>. If you are
49 not reading this on the LLVM web pages, you should probably go there because
50 this document may be updated after the release.</p>
52 <p>For more information about LLVM, including information about potentially more
53 current releases, please check out the <a href="http://llvm.cs.uiuc.edu">main
54 web site</a>. If you have questions or comments, the <a
55 href="http://mail.cs.uiuc.edu/mailman/listinfo/llvmdev">LLVM developer's mailing
56 list</a> is a good place to send them.</p>
58 <p>Note that if you are reading this file from CVS, this document applies
59 to the <i>next</i> release, not the current one. To see the release notes for
60 the current or previous releases, see the <a
61 href="http://llvm.cs.uiuc.edu/releases/">releases page</a>.</p>
65 <!-- *********************************************************************** -->
66 <div class="doc_section">
67 <a name="whatsnew">What's New?</a>
69 <!-- *********************************************************************** -->
71 <div class="doc_text">
73 <p>This is the fifth public release of the LLVM compiler infrastructure.</p>
75 <p> At this time, LLVM is known to correctly compile and run all C & C++
76 SPEC CPU95 & 2000 benchmarks, the Olden benchmarks, and the Ptrdist
77 benchmarks, and <b>many</b> other C and C++ programs.</p>
81 <!--=========================================================================-->
82 <div class="doc_subsubsection">
83 <a name="newfeatures">This release implements the following new features:</a>
86 <div class="doc_text">
89 <li>The test/Programs hierarchy <a href="http://llvm.cs.uiuc.edu/PR257">has
90 been moved out of the main LLVM tree</a> into a separate CVS repo and
92 <li>LLVM now optimizes global variables significantly more than it did
94 <li>LLVM now includes the new '<tt>undef</tt>' value and <a
95 href="LangRef.html#i_unreachable"><tt>unreachable</tt></a> instruction,
96 which give the optimizer more information about the behavior of the
98 <li>The LLVM makefiles have been improved to build LLVM much faster and
99 includes new targets (like make dist-check).</li>
100 <li>The LLVM source code is much more compatible with Microsoft Visual C++,
101 including the JIT and runtime-code generation, though the entire system
102 may not work with it.</li>
108 <!--=========================================================================-->
109 <div class="doc_subsubsection">
110 In this release, the following missing features were implemented:
113 <div class="doc_text">
116 <li><a href="http://llvm.cs.uiuc.edu/PR419">JIT interface should support
117 arbitrary calls</a></li>
122 <!--=========================================================================-->
123 <div class="doc_subsubsection">
124 <a name="qualityofimp">In this release, the following Quality of Implementation
125 issues were fixed:</a>
128 <div class="doc_text">
131 <li><a href="http://llvm.cs.uiuc.edu/PR426">[llvmg++] Tons of warnings are spewed when
132 linking to libstdc++</a></li>
133 <li><a href="http://llvm.cs.uiuc.edu/PR352">include/{Support,Config} ->
134 include/llvm/{Support,Config}</a></li>
139 <!--=========================================================================-->
140 <div class="doc_subsubsection">
141 In this release, the following build problems were fixed:
144 <div class="doc_text">
150 <!--=========================================================================-->
151 <div class="doc_subsubsection">
152 <a name="codequality">This release includes the following Code Quality
156 <div class="doc_text">
158 <li><a href="http://llvm.cs.uiuc.edu/PR362">Ugly code generated for
159 std::min/std::max</a></li>
163 <!--=========================================================================-->
164 <div class="doc_subsubsection">
165 <a name="bugfix">In this release, the following bugs in the previous release
169 <div class="doc_text">
171 <p>Bugs fixed in the LLVM Core:</p>
174 <li><a href="http://llvm.cs.uiuc.edu/PR420">[licm] LICM invalidates alias analysis info
175 and uses broken information</a> (optimizer crash)</li>
176 <li><a href="http://llvm.cs.uiuc.edu/PR422">[asmwriter] Asmwriter is really slow for
177 functions with lots of values</a></li>
178 <li><a href="http://llvm.cs.uiuc.edu/PR423">[anders-aa] Andersen's AA is completely
179 broken in LLVM 1.3</a></li>
180 <li><a href="http://llvm.cs.uiuc.edu/PR430">[bcwriter] Empty compaction tables
182 <li><a href="http://llvm.cs.uiuc.edu/PR227">[X86] llc output for functions w/certain
183 names tickles GNU 'as' bugs</a></li>
186 <p>Bugs in the C/C++ front-end:</p>
189 <li><a href="http://llvm.cs.uiuc.edu/PR445">[llvmg++] not enough templates are instantiated</a></li>
190 <li><a href="http://llvm.cs.uiuc.edu/PR450">[llvmg++] Extern const globals cannot be
191 marked 'constant' if they have nontrivial ctors or dtors</a></li>
194 <p>Bugs fixed in the Sparc V9 back-end:</p>
197 <li><a href="http://llvm.cs.uiuc.edu/PR428">[sparcv9] regalloc assertion
198 failure with certain indirect calls</a></li>
203 <!-- *********************************************************************** -->
204 <div class="doc_section">
205 <a name="portability">Portability and Supported Platforms</a>
207 <!-- *********************************************************************** -->
209 <div class="doc_text">
211 <p>LLVM is known to work in the following platforms:</p>
214 <li>Intel and AMD machines running Red Hat Linux and FreeBSD (and probably
215 other unix-like systems).</li>
216 <li>Sun UltraSPARC workstations running Solaris 8.</li>
217 <li>Intel and AMD machines running on Win32 with the Cygwin libraries.</li>
218 <li>PowerPC-based Mac OS X boxes, running 10.2 and above. Note that no JIT
219 support is available yet, and LLC support is beta. The C backend can be used
220 to produce stable code for this platform.</li>
223 <p>The core LLVM infrastructure uses
224 <a href="http://www.gnu.org/software/autoconf/">GNU autoconf</a> to adapt itself
225 to the machine and operating system on which it is built. However, minor
226 porting may be required to get LLVM to work on new platforms. We welcome your
227 portability patches and reports of successful builds or error messages.</p>
229 <p>Note that the LLVM build system does not currently support directories with
230 spaces on them when running on Win32/cygwin. We strongly recommend running
231 LLVM and the C frontend out of a top-level directory without spaces (e.g.,
232 <tt>/cygdrive/c/llvm</tt>). Also, make sure to install <b>all</b> of the
233 cygwin packages. By default, many important tools are not installed that
234 are needed by the LLVM build process or test suite (e.g., /bin/time). Finally,
235 please make sure that there are no directories with spaces in them in your
236 PATH environment variable.</p>
240 <!-- *********************************************************************** -->
241 <div class="doc_section">
242 <a name="knownproblems">Known Problems</a>
244 <!-- *********************************************************************** -->
246 <div class="doc_text">
248 <p>This section contains all known problems with the LLVM system, listed by
249 component. As new problems are discovered, they will be added to these
250 sections. If you run into a problem, please check the <a
251 href="http://llvm.cs.uiuc.edu/bugs/">LLVM bug database</a> and submit a bug if
252 there isn't already one.</p>
256 <!-- ======================================================================= -->
257 <div class="doc_subsection">
258 <a name="experimental">Experimental features included with this release</a>
261 <div class="doc_text">
263 <p>The following components of this LLVM release are either untested, known to
264 be broken or unreliable, or are in early development. These components should
265 not be relied on, and bugs should not be filed against them, but they may be
266 useful to some people. In particular, if you would like to work on one of these
267 components, please contact us on the llvmdev list.</p>
270 <li>The PowerPC backend is incomplete and is known to miscompile several SPEC
271 benchmarks. The file <tt>llvm/lib/Target/PowerPC/README.txt</tt> has
273 <li>The following passes are incomplete or buggy: <tt>-pgmdep, -memdep,
274 -ipmodref, -cee, -branch-combine, -instloops, -paths</tt></li>
275 <li>The <tt>-pre</tt> pass is incomplete (there are cases it doesn't handle that
276 it should) and not thoroughly tested.</li>
277 <li>The <tt>llvm-ar</tt> tool is incomplete and probably buggy.</li>
278 <li>The <tt>llvm-db</tt> tool is in a very early stage of development.</li>
283 <!-- ======================================================================= -->
284 <div class="doc_subsection">
285 <a name="core">Known problems with the LLVM Core</a>
288 <div class="doc_text">
292 <li>In the JIT, <tt>dlsym</tt> on a symbol compiled by the JIT will not
295 <li>The JIT does not use mutexes to protect its internal data structures. As
296 such, execution of a threaded program could cause these data structures to be
299 <li>Linking in static archive files (.a files) is slow (there is no symbol
300 table in the archive).</li>
302 <li>The gccld program <a href="http://llvm.cs.uiuc.edu/PR139">does not link
303 objects/archives in the order specified on the command line.</a></li>
305 <li><a href="http://llvm.cs.uiuc.edu/PR240">The lower-invoke pass does not mark
306 values live across a setjmp as volatile</a>. This missing feature only affects
307 targets whose setjmp/longjmp libraries do not save and restore the entire
312 <!-- ======================================================================= -->
313 <div class="doc_subsection">
314 <a name="c-fe">Known problems with the C front-end</a>
317 <!-- _______________________________________________________________________ -->
318 <div class="doc_subsubsection">Bugs</div>
320 <div class="doc_text">
322 <li>C99 Variable sized arrays do not release stack memory when they go out of
323 scope. Thus, the following program may run out of stack space:
325 for (i = 0; i != 1000000; ++i) {
331 <li>Initialization of global union variables can only be done <a
332 href="http://llvm.cs.uiuc.edu/bugs/show_bug.cgi?id=162">with the largest union
335 <li><a href="http://llvm.cs.uiuc.edu/PR244">[llvm-gcc] Error when an implicitly
336 external function is re-declared as static</a></li>
341 <!-- _______________________________________________________________________ -->
342 <div class="doc_subsubsection">
346 <div class="doc_text">
350 <li>Inline assembly is not yet supported.</li>
352 <li>"long double" is transformed by the front-end into "double". There is no
353 support for floating point data types of any size other than 32 and 64
356 <li>The following Unix system functionality has not been tested and may not
359 <li><tt>sigsetjmp</tt>, <tt>siglongjmp</tt> - These are not turned into the
360 appropriate <tt>invoke</tt>/<tt>unwind</tt> instructions. Note that
361 <tt>setjmp</tt> and <tt>longjmp</tt> <em>are</em> compiled correctly.
362 <li><tt>getcontext</tt>, <tt>setcontext</tt>, <tt>makecontext</tt>
363 - These functions have not been tested.
366 <li>Although many GCC extensions are supported, some are not. In particular,
367 the following extensions are known to <b>not be</b> supported:
369 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Local-Labels.html#Local%20Labels">Local Labels</a>: Labels local to a block.</li>
370 <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>
371 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Constructing-Calls.html#Constructing%20Calls">Constructing Calls</a>: Dispatching a call to another function.</li>
372 <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>
373 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Constraints.html#Constraints">Constraints</a>: Constraints for asm operands.</li>
374 <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>
375 <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>
376 <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>
377 <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>
378 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Thread-Local.html#Thread-Local">Thread-Local</a>: Per-thread variables.</li>
379 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Pragmas.html#Pragmas">Pragmas</a>: Pragmas accepted by GCC.</li>
382 <p>The following GCC extensions are <b>partially</b> supported. An ignored
383 attribute means that the LLVM compiler ignores the presence of the attribute,
384 but the code should still work. An unsupported attribute is one which is
385 ignored by the LLVM compiler and will cause a different interpretation of
389 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Variable-Length.html#Variable%20Length">Variable Length</a>:
390 Arrays whose length is computed at run time.<br>
391 Supported, but allocated stack space is not freed until the function returns (noted above).</li>
393 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Function-Attributes.html#Function%20Attributes">Function Attributes</a>:
395 Declaring that functions have no side effects or that they can never
398 <b>Supported:</b> <tt>format</tt>, <tt>format_arg</tt>, <tt>non_null</tt>,
399 <tt>constructor</tt>, <tt>destructor</tt>, <tt>unused</tt>,
400 <tt>deprecated</tt>, <tt>warn_unused_result</tt>, <tt>weak</tt><br>
402 <b>Ignored:</b> <tt>noreturn</tt>, <tt>noinline</tt>,
403 <tt>always_inline</tt>, <tt>pure</tt>, <tt>const</tt>, <tt>nothrow</tt>,
404 <tt>malloc</tt>, <tt>no_instrument_function</tt>, <tt>cdecl</tt><br>
406 <b>Unsupported:</b> <tt>used</tt>, <tt>section</tt>, <tt>alias</tt>,
407 <tt>visibility</tt>, <tt>regparm</tt>, <tt>stdcall</tt>,
408 <tt>fastcall</tt>, all other target specific attributes</li>
410 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Variable-Attributes.html#Variable%20Attributes">Variable Attributes</a>:
411 Specifying attributes of variables.<br>
412 <b>Supported:</b> <tt>cleanup</tt>, <tt>common</tt>, <tt>nocommon</tt>,
413 <tt>deprecated</tt>, <tt>transparent_union</tt>,
414 <tt>unused</tt>, <tt>weak</tt><br>
416 <b>Unsupported:</b> <tt>aligned</tt>, <tt>mode</tt>, <tt>packed</tt>,
417 <tt>section</tt>, <tt>shared</tt>, <tt>tls_model</tt>,
418 <tt>vector_size</tt>, <tt>dllimport</tt>,
419 <tt>dllexport</tt>, all target specific attributes.</li>
421 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Type-Attributes.html#Type%20Attributes">Type Attributes</a>: Specifying attributes of types.<br>
422 <b>Supported:</b> <tt>transparent_union</tt>, <tt>unused</tt>,
423 <tt>deprecated</tt>, <tt>may_alias</tt><br>
425 <b>Unsupported:</b> <tt>aligned</tt>, <tt>packed</tt>,
426 all target specific attributes.</li>
428 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Other-Builtins.html#Other%20Builtins">Other Builtins</a>:
429 Other built-in functions.<br>
430 We support all builtins which have a C language equivalent (e.g.,
431 <tt>__builtin_cos</tt>), <tt>__builtin_alloca</tt>,
432 <tt>__builtin_types_compatible_p</tt>, <tt>__builtin_choose_expr</tt>,
433 <tt>__builtin_constant_p</tt>, and <tt>__builtin_expect</tt>
434 (currently ignored). We also support builtins for ISO C99 floating
435 point comparison macros (e.g., <tt>__builtin_islessequal</tt>).</li>
438 <p>The following extensions <b>are</b> known to be supported:</p>
441 <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>
442 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Statement-Exprs.html#Statement%20Exprs">Statement Exprs</a>: Putting statements and declarations inside expressions.</li>
443 <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>
444 <li><a href="http://gcc.gnu.org/onlinedocs/gcc-3.4.0/gcc/Lvalues.html#Lvalues">Lvalues</a>: Using <code>?:</code>, "<code>,</code>" and casts in lvalues.</li>
445 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Conditionals.html#Conditionals">Conditionals</a>: Omitting the middle operand of a <code>?:</code> expression.</li>
446 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Long-Long.html#Long%20Long">Long Long</a>: Double-word integers.</li>
447 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Complex.html#Complex">Complex</a>: Data types for complex numbers.</li>
448 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Hex-Floats.html#Hex%20Floats">Hex Floats</a>:Hexadecimal floating-point constants.</li>
449 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Zero-Length.html#Zero%20Length">Zero Length</a>: Zero-length arrays.</li>
450 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Empty-Structures.html#Empty%20Structures">Empty Structures</a>: Structures with no members.</li>
451 <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>
452 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Escaped-Newlines.html#Escaped%20Newlines">Escaped Newlines</a>: Slightly looser rules for escaped newlines.</li>
453 <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>
454 <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>
455 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Initializers.html#Initializers">Initializers</a>: Non-constant initializers.</li>
456 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Compound-Literals.html#Compound%20Literals">Compound Literals</a>: Compound literals give structures, unions,
457 or arrays as values.</li>
458 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Designated-Inits.html#Designated%20Inits">Designated Inits</a>: Labeling elements of initializers.</li>
459 <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>
460 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Case-Ranges.html#Case%20Ranges">Case Ranges</a>: `case 1 ... 9' and such.</li>
461 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Mixed-Declarations.html#Mixed%20Declarations">Mixed Declarations</a>: Mixing declarations and code.</li>
462 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Function-Prototypes.html#Function%20Prototypes">Function Prototypes</a>: Prototype declarations and old-style definitions.</li>
463 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/C---Comments.html#C++%20Comments">C++ Comments</a>: C++ comments are recognized.</li>
464 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Dollar-Signs.html#Dollar%20Signs">Dollar Signs</a>: Dollar sign is allowed in identifiers.</li>
465 <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>
466 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Alignment.html#Alignment">Alignment</a>: Inquiring about the alignment of a type or variable.</li>
467 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Inline.html#Inline">Inline</a>: Defining inline functions (as fast as macros).</li>
468 <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>
469 <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>
470 <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>
471 <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>
472 <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>
473 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Attribute-Syntax.html#Attribute%20Syntax">Attribute Syntax</a>: Formal syntax for attributes.</li>
478 <p>If you run into GCC extensions which have not been included in any of these
479 lists, please let us know (also including whether or not they work).</p>
483 <!-- ======================================================================= -->
484 <div class="doc_subsection">
485 <a name="c++-fe">Known problems with the C++ front-end</a>
488 <div class="doc_text">
490 <p>For this release, the C++ front-end is considered to be fully functional but
491 has not been tested as thoroughly as the C front-end. It has been tested and
492 works for a number of non-trivial programs, but there may be lurking bugs.
493 Please report any bugs or problems.</p>
497 <!-- _______________________________________________________________________ -->
498 <div class="doc_subsubsection">Bugs</div>
500 <div class="doc_text">
503 <li>The C++ front-end inherits all problems afflicting the <a href="#c-fe">C
506 <li><b>IA-64 specific</b>: The C++ front-end does not use <a
507 href="http://llvm.cs.uiuc.edu/PR406">IA64 ABI compliant layout of v-tables</a>.
508 In particular, it just stores function pointers instead of function
509 descriptors in the vtable. This bug prevents mixing C++ code compiled with
510 LLVM with C++ objects compiled by other C++ compilers.</li>
516 <!-- _______________________________________________________________________ -->
517 <div class="doc_subsubsection">
521 <div class="doc_text">
525 <li>The C++ front-end is based on a pre-release of the GCC 3.4 C++ parser. This
526 parser is significantly more standards compliant (and picky) than prior GCC
527 versions. For more information, see the C++ section of the <a
528 href="http://gcc.gnu.org/gcc-3.4/changes.html">GCC 3.4 release notes</a>.</li>
530 <li>Destructors for local objects are not always run when a <tt>longjmp</tt> is
531 performed. In particular, destructors for objects in the <tt>longjmp</tt>ing
532 function and in the <tt>setjmp</tt> receiver function may not be run.
533 Objects in intervening stack frames will be destroyed, however (which is
534 better than most compilers).</li>
536 <li>The LLVM C++ front-end follows the <a
537 href="http://www.codesourcery.com/cxx-abi">Itanium C++ ABI</a>.
538 This document, which is not Itanium specific, specifies a standard for name
539 mangling, class layout, v-table layout, RTTI formats, and other C++
540 representation issues. Because we use this API, code generated by the LLVM
541 compilers should be binary compatible with machine code generated by other
542 Itanium ABI C++ compilers (such as G++, the Intel and HP compilers, etc).
543 <i>However</i>, the exception handling mechanism used by LLVM is very
544 different from the model used in the Itanium ABI, so <b>exceptions will not
545 interact correctly</b>. </li>
551 <!-- ======================================================================= -->
552 <div class="doc_subsection">
553 <a name="x86-be">Known problems with the X86 back-end</a>
556 <div class="doc_text">
564 <!-- ======================================================================= -->
565 <div class="doc_subsection">
566 <a name="sparcv9-be">Known problems with the SparcV9 back-end</a>
569 <div class="doc_text">
572 <li><a href="http://llvm.cs.uiuc.edu/PR60">[sparcv9] SparcV9 backend miscompiles
573 several programs in the LLVM test suite</a></li>
578 <!-- ======================================================================= -->
579 <div class="doc_subsection">
580 <a name="ppc-be">Known problems with the PowerPC back-end</a>
583 <div class="doc_text">
591 <!-- ======================================================================= -->
592 <div class="doc_subsection">
593 <a name="c-be">Known problems with the C back-end</a>
596 <div class="doc_text">
600 <li>The C back-end produces code that violates the ANSI C Type-Based Alias
601 Analysis rules. As such, special options may be necessary to compile the code
602 (for example, GCC requires the <tt>-fno-strict-aliasing</tt> option). This
603 problem probably cannot be fixed.</li>
605 <li><a href="http://llvm.cs.uiuc.edu/PR33">Initializers for global variables</a>
606 cannot include special floating point numbers like Not-A-Number or
609 <li><a href="http://llvm.cs.uiuc.edu/PR56">Zero arg vararg functions are not
610 supported</a>. This should not affect LLVM produced by the C or C++
617 <!-- *********************************************************************** -->
618 <div class="doc_section">
619 <a name="additionalinfo">Additional Information</a>
621 <!-- *********************************************************************** -->
623 <div class="doc_text">
625 <p>A wide variety of additional information is available on the LLVM web page,
626 including mailing lists and publications describing algorithms and components
627 implemented in LLVM. The web page also contains versions of the API
628 documentation which is up-to-date with the CVS version of the source code. You
629 can access versions of these documents specific to this release by going into
630 the "<tt>llvm/doc/</tt>" directory in the LLVM tree.</p>
632 <p>If you have any questions or comments about LLVM, please feel free to contact
633 us via the <a href="http://mail.cs.uiuc.edu/mailman/listinfo/llvmdev">mailing
638 <!-- *********************************************************************** -->
642 <a href="http://jigsaw.w3.org/css-validator/check/referer"><img
643 src="http://jigsaw.w3.org/css-validator/images/vcss" alt="Valid CSS!"></a>
644 <a href="http://validator.w3.org/check/referer"><img
645 src="http://www.w3.org/Icons/valid-html401" alt="Valid HTML 4.01!" /></a>
647 <a href="http://llvm.cs.uiuc.edu">The LLVM Compiler Infrastructure</a><br>
648 Last modified: $Date$