1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
2 "http://www.w3.org/TR/html4/strict.dtd">
5 <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
6 <link rel="stylesheet" href="llvm.css" type="text/css">
7 <title>LLVM 1.4 Release Notes</title>
11 <div class="doc_title">LLVM 1.4 Release Notes</div>
14 <li><a href="#intro">Introduction</a></li>
15 <li><a href="#whatsnew">What's New?</a></li>
16 <li><a href="GettingStarted.html">Installation Instructions</a></li>
17 <li><a href="#portability">Portability and Supported Platforms</a></li>
18 <li><a href="#knownproblems">Known Problems</a>
20 <li><a href="#experimental">Experimental features included in this
22 <li><a href="#core">Known problems with the LLVM Core</a>
23 <li><a href="#c-fe">Known problems with the C Front-end</a>
24 <li><a href="#c++-fe">Known problems with the C++ Front-end</a>
25 <li><a href="#x86-be">Known problems with the X86 Back-end</a>
26 <li><a href="#sparcv9-be">Known problems with the SparcV9 Back-end</a>
27 <li><a href="#ppc-be">Known problems with the PowerPC Back-end</a>
28 <li><a href="#c-be">Known problems with the C back-end</a>
30 <li><a href="#additionalinfo">Additional Information</a></li>
33 <div class="doc_author">
34 <p>Written by the <a href="http://llvm.cs.uiuc.edu">LLVM team</a><p>
37 <!-- *********************************************************************** -->
38 <div class="doc_section">
39 <a name="intro">Introduction</a>
41 <!-- *********************************************************************** -->
43 <div class="doc_text">
45 <p>This document contains the release notes for the LLVM compiler
46 infrastructure, release 1.4. Here we describe the status of LLVM, including any
47 known problems and bug fixes from the previous release. The most up-to-date
48 version of this document can be found on the <a
49 href="http://llvm.cs.uiuc.edu/releases/1.4/">LLVM 1.4 web site</a>. If you are
50 not reading this on the LLVM web pages, you should probably go there because
51 this document may be updated after the release.</p>
53 <p>For more information about LLVM, including information about potentially more
54 current releases, please check out the <a href="http://llvm.cs.uiuc.edu">main
55 web site</a>. If you have questions or comments, the <a
56 href="http://mail.cs.uiuc.edu/mailman/listinfo/llvmdev">LLVM developer's mailing
57 list</a> is a good place to send them.</p>
59 <p>Note that if you are reading this file from CVS, this document applies
60 to the <i>next</i> release, not the current one. To see the release notes for
61 the current or previous releases, see the <a
62 href="http://llvm.cs.uiuc.edu/releases/">releases page</a>.</p>
66 <!-- *********************************************************************** -->
67 <div class="doc_section">
68 <a name="whatsnew">What's New?</a>
70 <!-- *********************************************************************** -->
72 <div class="doc_text">
74 <p>This is the fifth public release of the LLVM compiler infrastructure.</p>
76 <p> At this time, LLVM is known to correctly compile and run all C & C++
77 SPEC CPU95 & 2000 benchmarks, the Olden benchmarks, and the Ptrdist
78 benchmarks, and <b>many</b> other C and C++ programs.</p>
82 <!--=========================================================================-->
83 <div class="doc_subsubsection">
84 <a name="newfeatures">This release implements the following new features:</a>
87 <div class="doc_text">
89 <li>LLVM now includes a JIT for the PowerPC target.</li>
90 <li>LLVM now optimizes global variables significantly more than it did
93 <li>LLVM now includes the new '<tt>undef</tt>' value and
94 <a href="LangRef.html#i_unreachable"><tt>unreachable</tt></a> instruction,
95 which give the optimizer more information about the behavior of the
98 <li>llvmgcc and llvmg++ now emit source line number information when '-g' is
99 passed in. This information can be used with llvm-db or other tools and
102 <li>The test/Programs hierarchy <a href="http://llvm.cs.uiuc.edu/PR257">has
103 been moved out of the main LLVM tree</a> into a separate CVS repository and
104 tarball. This shrinks the distribution size of LLVM itself significantly.
106 <li>Bytecode compression with bzip2 has been implemented. All bytecode files
107 generated by LLVM will now be compressed by default. Compression can be
108 disabled with the <tt>-disable-compression</tt> option to the tools that can
109 generate bytecode files.
111 <li>A generic <a href="http://llvm.cs.uiuc.edu/PR353">compiler driver</a> and
112 an associated <a href="CommandGuide/html/llvm-ld.html">generic linker</a> have
113 been implemented. The compiler driver is generic because it can be configured
114 to pre-process, translate, optimize, assemble, and link code from any source
115 language. This aids compiler writers because all that is needed is a
116 source-to-bytecode or source-to-assembly translator and a configuration file.
117 The linker is generic because it allows dynamically loadable optimization
118 modules to be executed for link-time optimization. Language specific
119 link-time optimization modules can be created and executed automatically.
121 <li>The <a href="http://llvm.cs.uiuc.edu/PR263">dependent libraries</a>
122 feature has been implemented. This allows front end compilers to indicate in
123 the bytecode which libraries the bytecode needs to be linked with. Both the
124 C/C++ front end and Stacker support generating the required libraries. The
125 Linker now supports using this information to ensure required libaries are
126 linked into the module. This minimizes the need to use the <tt>-l</tt> option
127 when using <a href="CommandGuide/html/llvmc.html"><tt>llvmc</tt></a>
129 <li>The LLVM makefiles have been improved to build LLVM faster (2x) and
130 includes new targets (like dist-check, uninstall). One important change is
131 associated with <a href="http://llvm.cs.uiuc.edu/PR456">PR456</a>. The
132 libraries and tools will now be built into <tt>$builddir/Debug/{bin,lib}</tt>
133 instead of <tt>$builddir/tools/Debug</tt> and <tt>$builddir/lib/Debug</tt>.
134 Similarly for <tt>Release</tt> and <tt>Profile</tt> builds.
136 <li>The LLVM source code is much more compatible with Microsoft Visual C++,
137 including the JIT and runtime-code generation, though the entire system
138 may not work with it.
140 <li>The target-to-JIT interfaces <a href="http://llvm.cs.uiuc.edu/PR283">are
141 now much simpler</a> and more powerful.
143 <li>zlib and libpng are <a href="http://llvm.cs.uiuc.edu/PR417">no longer
144 included in the main LLVM tarball</a>.</li>
150 <!--=========================================================================-->
151 <div class="doc_subsubsection">
152 In this release, the following missing features were implemented:
155 <div class="doc_text">
158 <li><a href="http://llvm.cs.uiuc.edu/PR419">JIT interface should support
161 <li>The <tt>llvm-ar</tt> tool was previously incomplete and didn't properly
162 support other ar(1) implementations. This has been corrected. <tt>llvm-ar</tt>
163 now fully supports all archive editing functions, table of contents listing,
164 extraction, and printing. It can also read BSD4.4/MacOSX and SVR4 style
165 archives. See <a href="CommandGuide/html/llvm-ar.html">llvm-ar</a> for
172 <!--=========================================================================-->
173 <div class="doc_subsubsection">
174 <a name="qualityofimp">In this release, the following Quality of Implementation
175 issues were fixed:</a>
178 <div class="doc_text">
181 <li><a href="http://llvm.cs.uiuc.edu/PR426">[llvmg++] Tons of warnings
182 are spewed when linking to libstdc++</a>
184 <li><a href="http://llvm.cs.uiuc.edu/PR352">include/{Support,Config} ->
185 include/llvm/{Support,Config}</a>
187 <li>The names of the libraries generated by compiling LLVM source have been
188 changed to ensure they do not conflict with other packages upon installation.
189 Each LLVM library is now prefixed with LLVM and uses mixed clase. For example,
190 the library <tt>libasmparser.a</tt> in 1.3 has become
191 <tt>libLLVMAsmParser.a</tt> in release 1.4.
197 <!--=========================================================================-->
198 <div class="doc_subsubsection">
199 In this release, the following build problems were fixed:
202 <div class="doc_text">
204 <li><a href="http://llvm.cs.uiuc.edu/PR256">[autoconf] further standardizing
205 autoconf usage</a>. Various improvements in the configure.ac script were
206 made as well as the makefile system.
211 <!--=========================================================================-->
212 <div class="doc_subsubsection">
213 <a name="codequality">This release includes the following Code Quality
217 <div class="doc_text">
219 <li><a href="http://llvm.cs.uiuc.edu/PR362">Ugly code generated for
220 std::min/std::max</a>
225 <!--=========================================================================-->
226 <div class="doc_subsubsection">
227 <a name="bugfix">In this release, the following bugs in the previous release
231 <div class="doc_text">
233 <p>Bugs fixed in the LLVM Core:</p>
236 <li><a href="http://llvm.cs.uiuc.edu/PR420">[licm] LICM invalidates alias
237 analysis info and uses broken information</a> (optimizer crash)</li>
238 <li><a href="http://llvm.cs.uiuc.edu/PR422">[asmwriter] Asmwriter is really
239 slow for functions with lots of values</a></li>
240 <li><a href="http://llvm.cs.uiuc.edu/PR423">[anders-aa] Andersen's AA is
241 completely broken in LLVM 1.3</a></li>
242 <li><a href="http://llvm.cs.uiuc.edu/PR430">[bcwriter] Empty compaction
243 tables defined</a></li>
244 <li><a href="http://llvm.cs.uiuc.edu/PR227">[X86] llc output for functions
245 w/certain names tickles GNU 'as' bugs</a></li>
248 <p>Bugs in the C/C++ front-end:</p>
251 <li><a href="http://llvm.cs.uiuc.edu/PR445">[llvmg++] not enough templates are
252 instantiated</a></li>
253 <li><a href="http://llvm.cs.uiuc.edu/PR450">[llvmg++] Extern const globals
254 cannot be marked 'constant' if they have nontrivial ctors or dtors</a></li>
255 <li><a href="http://llvm.cs.uiuc.edu/PR461">[llvmgcc] Crash compiling unnamed
256 bitfield which does not increase struct size</a></li>
259 <p>Bugs fixed in the Sparc V9 back-end:</p>
262 <li><a href="http://llvm.cs.uiuc.edu/PR428">[sparcv9] regalloc assertion
263 failure with certain indirect calls</a></li>
268 <!-- *********************************************************************** -->
269 <div class="doc_section">
270 <a name="portability">Portability and Supported Platforms</a>
272 <!-- *********************************************************************** -->
274 <div class="doc_text">
276 <p>LLVM is known to work in the following platforms:</p>
279 <li>Intel and AMD machines running Red Hat Linux and FreeBSD (and probably
280 other unix-like systems).</li>
281 <li>Sun UltraSPARC workstations running Solaris 8.</li>
282 <li>Intel and AMD machines running on Win32 with the Cygwin libraries.</li>
283 <li>PowerPC-based Mac OS X boxes, running 10.2 and above.</li>
286 <p>The core LLVM infrastructure uses
287 <a href="http://www.gnu.org/software/autoconf/">GNU autoconf</a> to adapt itself
288 to the machine and operating system on which it is built. However, minor
289 porting may be required to get LLVM to work on new platforms. We welcome your
290 portability patches and reports of successful builds or error messages.</p>
292 <p>Note that the LLVM build system does not currently support directories with
293 spaces on them when running on Win32/cygwin. We strongly recommend running
294 LLVM and the C frontend out of a top-level directory without spaces (e.g.,
295 <tt>/cygdrive/c/llvm</tt>). Also, make sure to install <b>all</b> of the
296 cygwin packages. By default, many important tools are not installed that
297 are needed by the LLVM build process or test suite (e.g., /bin/time). Finally,
298 please make sure that there are no directories with spaces in them in your
299 PATH environment variable.</p>
303 <!-- *********************************************************************** -->
304 <div class="doc_section">
305 <a name="knownproblems">Known Problems</a>
307 <!-- *********************************************************************** -->
309 <div class="doc_text">
311 <p>This section contains all known problems with the LLVM system, listed by
312 component. As new problems are discovered, they will be added to these
313 sections. If you run into a problem, please check the <a
314 href="http://llvm.cs.uiuc.edu/bugs/">LLVM bug database</a> and submit a bug if
315 there isn't already one.</p>
319 <!-- ======================================================================= -->
320 <div class="doc_subsection">
321 <a name="experimental">Experimental features included with this release</a>
324 <div class="doc_text">
326 <p>The following components of this LLVM release are either untested, known to
327 be broken or unreliable, or are in early development. These components should
328 not be relied on, and bugs should not be filed against them, but they may be
329 useful to some people. In particular, if you would like to work on one of these
330 components, please contact us on the llvmdev list.</p>
333 <li>The following passes are incomplete or buggy: <tt>-pgmdep, -memdep,
334 -ipmodref, -cee, -branch-combine, -instloops, -paths</tt></li>
335 <li>The <tt>-pre</tt> pass is incomplete (there are cases it doesn't handle that
336 it should) and not thoroughly tested.</li>
337 <li>The <tt>llvm-db</tt> tool is in a very early stage of development.</li>
342 <!-- ======================================================================= -->
343 <div class="doc_subsection">
344 <a name="core">Known problems with the LLVM Core</a>
347 <div class="doc_text">
350 <li>In the JIT, <tt>dlsym</tt> on a symbol compiled by the JIT will not work.
352 <li>The JIT does not use mutexes to protect its internal data structures. As
353 such, execution of a threaded program could cause these data structures to be
356 <li>Linking in static archive files (.a files) is slow by default because
357 there is no symbol table in the archive. To remedy this, run
358 <a href="CommandGuide/html/llvm-ranlib.html"><tt>llvm-ranlib</tt></a> on the
359 archive to add an LLVM symbol table.
361 <li>The gccld program <a href="http://llvm.cs.uiuc.edu/PR139">does not link
362 objects/archives in the order specified on the command line.</a>
364 <li><a href="http://llvm.cs.uiuc.edu/PR240">The lower-invoke pass does not
365 mark values live across a setjmp as volatile</a>. This missing feature
366 only affects targets whose setjmp/longjmp libraries do not save and restore
367 the entire register file.</li>
368 <li><a href="http://llvm.cs.uiuc.edu/PR427">[bytecode] Assertion on V1
369 Bytecode Files</a>. This bug won't be fixed because V1 bytecode had its own
370 problems, no one is using V1 bytecode any more, and the fix is non-trivial.
375 <!-- ======================================================================= -->
376 <div class="doc_subsection">
377 <a name="c-fe">Known problems with the C front-end</a>
380 <!-- _______________________________________________________________________ -->
381 <div class="doc_subsubsection">Bugs</div>
383 <div class="doc_text">
385 <li>C99 Variable sized arrays do not release stack memory when they go out of
386 scope. Thus, the following program may run out of stack space:
388 for (i = 0; i != 1000000; ++i) {
394 <li>Initialization of global union variables can only be done <a
395 href="http://llvm.cs.uiuc.edu/bugs/show_bug.cgi?id=162">with the largest union
398 <li><a href="http://llvm.cs.uiuc.edu/PR244">[llvm-gcc] Error when an implicitly
399 external function is re-declared as static</a></li>
404 <!-- _______________________________________________________________________ -->
405 <div class="doc_subsubsection">
409 <div class="doc_text">
413 <li>Inline assembly is not yet supported.</li>
415 <li>"long double" is transformed by the front-end into "double". There is no
416 support for floating point data types of any size other than 32 and 64
419 <li>The following Unix system functionality has not been tested and may not
422 <li><tt>sigsetjmp</tt>, <tt>siglongjmp</tt> - These are not turned into the
423 appropriate <tt>invoke</tt>/<tt>unwind</tt> instructions. Note that
424 <tt>setjmp</tt> and <tt>longjmp</tt> <em>are</em> compiled correctly.
425 <li><tt>getcontext</tt>, <tt>setcontext</tt>, <tt>makecontext</tt>
426 - These functions have not been tested.
429 <li>Although many GCC extensions are supported, some are not. In particular,
430 the following extensions are known to <b>not be</b> supported:
432 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Local-Labels.html#Local%20Labels">Local Labels</a>: Labels local to a block.</li>
433 <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>
434 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Constructing-Calls.html#Constructing%20Calls">Constructing Calls</a>: Dispatching a call to another function.</li>
435 <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>
436 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Constraints.html#Constraints">Constraints</a>: Constraints for asm operands.</li>
437 <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>
438 <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>
439 <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>
440 <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>
441 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Thread-Local.html#Thread-Local">Thread-Local</a>: Per-thread variables.</li>
442 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Pragmas.html#Pragmas">Pragmas</a>: Pragmas accepted by GCC.</li>
445 <p>The following GCC extensions are <b>partially</b> supported. An ignored
446 attribute means that the LLVM compiler ignores the presence of the attribute,
447 but the code should still work. An unsupported attribute is one which is
448 ignored by the LLVM compiler and will cause a different interpretation of
452 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Variable-Length.html#Variable%20Length">Variable Length</a>:
453 Arrays whose length is computed at run time.<br>
454 Supported, but allocated stack space is not freed until the function returns (noted above).</li>
456 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Function-Attributes.html#Function%20Attributes">Function Attributes</a>:
458 Declaring that functions have no side effects or that they can never
461 <b>Supported:</b> <tt>format</tt>, <tt>format_arg</tt>, <tt>non_null</tt>,
462 <tt>constructor</tt>, <tt>destructor</tt>, <tt>unused</tt>,
463 <tt>deprecated</tt>, <tt>warn_unused_result</tt>, <tt>weak</tt><br>
465 <b>Ignored:</b> <tt>noreturn</tt>, <tt>noinline</tt>,
466 <tt>always_inline</tt>, <tt>pure</tt>, <tt>const</tt>, <tt>nothrow</tt>,
467 <tt>malloc</tt>, <tt>no_instrument_function</tt>, <tt>cdecl</tt><br>
469 <b>Unsupported:</b> <tt>used</tt>, <tt>section</tt>, <tt>alias</tt>,
470 <tt>visibility</tt>, <tt>regparm</tt>, <tt>stdcall</tt>,
471 <tt>fastcall</tt>, all other target specific attributes</li>
473 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Variable-Attributes.html#Variable%20Attributes">Variable Attributes</a>:
474 Specifying attributes of variables.<br>
475 <b>Supported:</b> <tt>cleanup</tt>, <tt>common</tt>, <tt>nocommon</tt>,
476 <tt>deprecated</tt>, <tt>transparent_union</tt>,
477 <tt>unused</tt>, <tt>weak</tt><br>
479 <b>Unsupported:</b> <tt>aligned</tt>, <tt>mode</tt>, <tt>packed</tt>,
480 <tt>section</tt>, <tt>shared</tt>, <tt>tls_model</tt>,
481 <tt>vector_size</tt>, <tt>dllimport</tt>,
482 <tt>dllexport</tt>, all target specific attributes.</li>
484 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Type-Attributes.html#Type%20Attributes">Type Attributes</a>: Specifying attributes of types.<br>
485 <b>Supported:</b> <tt>transparent_union</tt>, <tt>unused</tt>,
486 <tt>deprecated</tt>, <tt>may_alias</tt><br>
488 <b>Unsupported:</b> <tt>aligned</tt>, <tt>packed</tt>,
489 all target specific attributes.</li>
491 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Other-Builtins.html#Other%20Builtins">Other Builtins</a>:
492 Other built-in functions.<br>
493 We support all builtins which have a C language equivalent (e.g.,
494 <tt>__builtin_cos</tt>), <tt>__builtin_alloca</tt>,
495 <tt>__builtin_types_compatible_p</tt>, <tt>__builtin_choose_expr</tt>,
496 <tt>__builtin_constant_p</tt>, and <tt>__builtin_expect</tt>
497 (currently ignored). We also support builtins for ISO C99 floating
498 point comparison macros (e.g., <tt>__builtin_islessequal</tt>).</li>
501 <p>The following extensions <b>are</b> known to be supported:</p>
504 <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>
505 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Statement-Exprs.html#Statement%20Exprs">Statement Exprs</a>: Putting statements and declarations inside expressions.</li>
506 <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>
507 <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>
508 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Conditionals.html#Conditionals">Conditionals</a>: Omitting the middle operand of a <code>?:</code> expression.</li>
509 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Long-Long.html#Long%20Long">Long Long</a>: Double-word integers.</li>
510 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Complex.html#Complex">Complex</a>: Data types for complex numbers.</li>
511 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Hex-Floats.html#Hex%20Floats">Hex Floats</a>:Hexadecimal floating-point constants.</li>
512 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Zero-Length.html#Zero%20Length">Zero Length</a>: Zero-length arrays.</li>
513 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Empty-Structures.html#Empty%20Structures">Empty Structures</a>: Structures with no members.</li>
514 <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>
515 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Escaped-Newlines.html#Escaped%20Newlines">Escaped Newlines</a>: Slightly looser rules for escaped newlines.</li>
516 <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>
517 <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>
518 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Initializers.html#Initializers">Initializers</a>: Non-constant initializers.</li>
519 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Compound-Literals.html#Compound%20Literals">Compound Literals</a>: Compound literals give structures, unions,
520 or arrays as values.</li>
521 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Designated-Inits.html#Designated%20Inits">Designated Inits</a>: Labeling elements of initializers.</li>
522 <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>
523 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Case-Ranges.html#Case%20Ranges">Case Ranges</a>: `case 1 ... 9' and such.</li>
524 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Mixed-Declarations.html#Mixed%20Declarations">Mixed Declarations</a>: Mixing declarations and code.</li>
525 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Function-Prototypes.html#Function%20Prototypes">Function Prototypes</a>: Prototype declarations and old-style definitions.</li>
526 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/C---Comments.html#C++%20Comments">C++ Comments</a>: C++ comments are recognized.</li>
527 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Dollar-Signs.html#Dollar%20Signs">Dollar Signs</a>: Dollar sign is allowed in identifiers.</li>
528 <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>
529 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Alignment.html#Alignment">Alignment</a>: Inquiring about the alignment of a type or variable.</li>
530 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Inline.html#Inline">Inline</a>: Defining inline functions (as fast as macros).</li>
531 <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>
532 <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>
533 <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>
534 <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>
535 <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>
536 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Attribute-Syntax.html#Attribute%20Syntax">Attribute Syntax</a>: Formal syntax for attributes.</li>
541 <p>If you run into GCC extensions which have not been included in any of these
542 lists, please let us know (also including whether or not they work).</p>
546 <!-- ======================================================================= -->
547 <div class="doc_subsection">
548 <a name="c++-fe">Known problems with the C++ front-end</a>
551 <div class="doc_text">
553 <p>For this release, the C++ front-end is considered to be fully functional but
554 has not been tested as thoroughly as the C front-end. It has been tested and
555 works for a number of non-trivial programs, but there may be lurking bugs.
556 Please report any bugs or problems.</p>
560 <!-- _______________________________________________________________________ -->
561 <div class="doc_subsubsection">Bugs</div>
563 <div class="doc_text">
566 <li>The C++ front-end inherits all problems afflicting the <a href="#c-fe">C
569 <li><b>IA-64 specific</b>: The C++ front-end does not use <a
570 href="http://llvm.cs.uiuc.edu/PR406">IA64 ABI compliant layout of v-tables</a>.
571 In particular, it just stores function pointers instead of function
572 descriptors in the vtable. This bug prevents mixing C++ code compiled with
573 LLVM with C++ objects compiled by other C++ compilers.</li>
579 <!-- _______________________________________________________________________ -->
580 <div class="doc_subsubsection">
584 <div class="doc_text">
588 <li>The C++ front-end is based on a pre-release of the GCC 3.4 C++ parser. This
589 parser is significantly more standards compliant (and picky) than prior GCC
590 versions. For more information, see the C++ section of the <a
591 href="http://gcc.gnu.org/gcc-3.4/changes.html">GCC 3.4 release notes</a>.</li>
593 <li>Destructors for local objects are not always run when a <tt>longjmp</tt> is
594 performed. In particular, destructors for objects in the <tt>longjmp</tt>ing
595 function and in the <tt>setjmp</tt> receiver function may not be run.
596 Objects in intervening stack frames will be destroyed, however (which is
597 better than most compilers).</li>
599 <li>The LLVM C++ front-end follows the <a
600 href="http://www.codesourcery.com/cxx-abi">Itanium C++ ABI</a>.
601 This document, which is not Itanium specific, specifies a standard for name
602 mangling, class layout, v-table layout, RTTI formats, and other C++
603 representation issues. Because we use this API, code generated by the LLVM
604 compilers should be binary compatible with machine code generated by other
605 Itanium ABI C++ compilers (such as G++, the Intel and HP compilers, etc).
606 <i>However</i>, the exception handling mechanism used by LLVM is very
607 different from the model used in the Itanium ABI, so <b>exceptions will not
608 interact correctly</b>. </li>
614 <!-- ======================================================================= -->
615 <div class="doc_subsection">
616 <a name="x86-be">Known problems with the X86 back-end</a>
619 <div class="doc_text">
627 <!-- ======================================================================= -->
628 <div class="doc_subsection">
629 <a name="sparcv9-be">Known problems with the SparcV9 back-end</a>
632 <div class="doc_text">
635 <li><a href="http://llvm.cs.uiuc.edu/PR60">[sparcv9] SparcV9 backend miscompiles
636 several programs in the LLVM test suite</a></li>
641 <!-- ======================================================================= -->
642 <div class="doc_subsection">
643 <a name="ppc-be">Known problems with the PowerPC back-end</a>
646 <div class="doc_text">
654 <!-- ======================================================================= -->
655 <div class="doc_subsection">
656 <a name="c-be">Known problems with the C back-end</a>
659 <div class="doc_text">
663 <li>The C back-end produces code that violates the ANSI C Type-Based Alias
664 Analysis rules. As such, special options may be necessary to compile the code
665 (for example, GCC requires the <tt>-fno-strict-aliasing</tt> option). This
666 problem probably cannot be fixed.</li>
668 <li><a href="http://llvm.cs.uiuc.edu/PR33">Initializers for global variables</a>
669 cannot include special floating point numbers like Not-A-Number or
672 <li><a href="http://llvm.cs.uiuc.edu/PR56">Zero arg vararg functions are not
673 supported</a>. This should not affect LLVM produced by the C or C++
680 <!-- *********************************************************************** -->
681 <div class="doc_section">
682 <a name="additionalinfo">Additional Information</a>
684 <!-- *********************************************************************** -->
686 <div class="doc_text">
688 <p>A wide variety of additional information is available on the LLVM web page,
689 including mailing lists and publications describing algorithms and components
690 implemented in LLVM. The web page also contains versions of the API
691 documentation which is up-to-date with the CVS version of the source code. You
692 can access versions of these documents specific to this release by going into
693 the "<tt>llvm/doc/</tt>" directory in the LLVM tree.</p>
695 <p>If you have any questions or comments about LLVM, please feel free to contact
696 us via the <a href="http://mail.cs.uiuc.edu/mailman/listinfo/llvmdev">mailing
701 <!-- *********************************************************************** -->
705 <a href="http://jigsaw.w3.org/css-validator/check/referer"><img
706 src="http://jigsaw.w3.org/css-validator/images/vcss" alt="Valid CSS!"></a>
707 <a href="http://validator.w3.org/check/referer"><img
708 src="http://www.w3.org/Icons/valid-html401" alt="Valid HTML 4.01!" /></a>
710 <a href="http://llvm.cs.uiuc.edu">The LLVM Compiler Infrastructure</a><br>
711 Last modified: $Date$