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 optimizes global variables significantly more than it did
92 <li>LLVM now includes the new '<tt>undef</tt>' value and
93 <a href="LangRef.html#i_unreachable"><tt>unreachable</tt></a> instruction,
94 which give the optimizer more information about the behavior of the
97 <li>llvmgcc and llvmg++ now emit source line number information when '-g' is
98 passed in. This information can be used with llvm-db or other tools and
101 <li>The test/Programs hierarchy <a href="http://llvm.cs.uiuc.edu/PR257">has
102 been moved out of the main LLVM tree</a> into a separate CVS repository and
103 tarball. This shrinks the distribution size of LLVM itself significantly.
105 <li>Bytecode compression with bzip2 has been implemented. All bytecode files
106 generated by LLVM will now be compressed by default. Compression can be
107 disabled with the <tt>-disable-compression</tt> option to the tools that can
108 generate bytecode files.
110 <li>A generic <a href="http://llvm.cs.uiuc.edu/PR353">compiler driver</a> and
111 an associated <a href="CommandGuide/html/llvm-ld.html">generic linker</a> have
112 been implemented. The compiler driver is generic because it can be configured
113 to pre-process, translate, optimize, assemble, and link code from any source
114 language. This aids compiler writers because all that is needed is a
115 source-to-bytecode or source-to-assembly translator and a configuration file.
116 The linker is generic because it allows dynamically loadable optimization
117 modules to be executed for link-time optimization. Language specific
118 link-time optimization modules can be created and executed automatically.
120 <li>The <a href="http://llvm.cs.uiuc.edu/PR263">dependent libraries</a>
121 feature has been implemented. This allows front end compilers to indicate in
122 the bytecode which libraries the bytecode needs to be linked with. Both the
123 C/C++ front end and Stacker support generating the required libraries. The
124 Linker now supports using this information to ensure required libaries are
125 linked into the module. This minimizes the need to use the <tt>-l</tt> option
126 when using <a href="CommandGuide/html/llvmc.html"><tt>llvmc</tt></a>
128 <li>The LLVM makefiles have been improved to build LLVM faster (2x) and
129 includes new targets (like dist-check, uninstall). One important change is
130 associated with <a href="http://llvm.cs.uiuc.edu/PR456">PR456</a>. The
131 libraries and tools will now be built into <tt>$builddir/Debug/{bin,lib}</tt>
132 instead of <tt>$builddir/tools/Debug</tt> and <tt>$builddir/lib/Debug</tt>.
133 Similarly for <tt>Release</tt> and <tt>Profile</tt> builds.
135 <li>The LLVM source code is much more compatible with Microsoft Visual C++,
136 including the JIT and runtime-code generation, though the entire system
137 may not work with it.
139 <li>The target-to-JIT interfaces <a href="http://llvm.cs.uiuc.edu/PR283">are
140 now much simpler</a> and more powerful.
147 <!--=========================================================================-->
148 <div class="doc_subsubsection">
149 In this release, the following missing features were implemented:
152 <div class="doc_text">
155 <li><a href="http://llvm.cs.uiuc.edu/PR419">JIT interface should support
158 <li>The <tt>llvm-ar</tt> tool was previously incomplete and didn't properly
159 support other ar(1) implementations. This has been corrected. <tt>llvm-ar</tt>
160 now fully supports all archive editing functions, table of contents listing,
161 extraction, and printing. It can also read BSD4.4/MacOSX and SVR4 style
162 archives. See <a href="CommandGuide/html/llvm-ar.html">llvm-ar</a> for
169 <!--=========================================================================-->
170 <div class="doc_subsubsection">
171 <a name="qualityofimp">In this release, the following Quality of Implementation
172 issues were fixed:</a>
175 <div class="doc_text">
178 <li><a href="http://llvm.cs.uiuc.edu/PR426">[llvmg++] Tons of warnings
179 are spewed when linking to libstdc++</a>
181 <li><a href="http://llvm.cs.uiuc.edu/PR352">include/{Support,Config} ->
182 include/llvm/{Support,Config}</a>
184 <li>The names of the libraries generated by compiling LLVM source have been
185 changed to ensure they do not conflict with other packages upon installation.
186 Each LLVM library is now prefixed with LLVM and uses mixed clase. For example,
187 the library <tt>libasmparser.a</tt> in 1.3 has become
188 <tt>libLLVMAsmParser.a</tt> in release 1.4.
194 <!--=========================================================================-->
195 <div class="doc_subsubsection">
196 In this release, the following build problems were fixed:
199 <div class="doc_text">
201 <li><a href="http://llvm.cs.uiuc.edu/PR256">[autoconf] further standardizing
202 autoconf usage</a>. Various improvements in the configure.ac script were
203 made as well as the makefile system.
208 <!--=========================================================================-->
209 <div class="doc_subsubsection">
210 <a name="codequality">This release includes the following Code Quality
214 <div class="doc_text">
216 <li><a href="http://llvm.cs.uiuc.edu/PR362">Ugly code generated for
217 std::min/std::max</a>
222 <!--=========================================================================-->
223 <div class="doc_subsubsection">
224 <a name="bugfix">In this release, the following bugs in the previous release
228 <div class="doc_text">
230 <p>Bugs fixed in the LLVM Core:</p>
233 <li><a href="http://llvm.cs.uiuc.edu/PR420">[licm] LICM invalidates alias
234 analysis info and uses broken information</a> (optimizer crash)</li>
235 <li><a href="http://llvm.cs.uiuc.edu/PR422">[asmwriter] Asmwriter is really
236 slow for functions with lots of values</a></li>
237 <li><a href="http://llvm.cs.uiuc.edu/PR423">[anders-aa] Andersen's AA is
238 completely broken in LLVM 1.3</a></li>
239 <li><a href="http://llvm.cs.uiuc.edu/PR430">[bcwriter] Empty compaction
240 tables defined</a></li>
241 <li><a href="http://llvm.cs.uiuc.edu/PR227">[X86] llc output for functions
242 w/certain names tickles GNU 'as' bugs</a></li>
245 <p>Bugs in the C/C++ front-end:</p>
248 <li><a href="http://llvm.cs.uiuc.edu/PR445">[llvmg++] not enough templates are
249 instantiated</a></li>
250 <li><a href="http://llvm.cs.uiuc.edu/PR450">[llvmg++] Extern const globals
251 cannot be marked 'constant' if they have nontrivial ctors or dtors</a></li>
252 <li><a href="http://llvm.cs.uiuc.edu/PR461">[llvmgcc] Crash compiling unnamed
253 bitfield which does not increase struct size</a></li>
256 <p>Bugs fixed in the Sparc V9 back-end:</p>
259 <li><a href="http://llvm.cs.uiuc.edu/PR428">[sparcv9] regalloc assertion
260 failure with certain indirect calls</a></li>
265 <!-- *********************************************************************** -->
266 <div class="doc_section">
267 <a name="portability">Portability and Supported Platforms</a>
269 <!-- *********************************************************************** -->
271 <div class="doc_text">
273 <p>LLVM is known to work in the following platforms:</p>
276 <li>Intel and AMD machines running Red Hat Linux and FreeBSD (and probably
277 other unix-like systems).</li>
278 <li>Sun UltraSPARC workstations running Solaris 8.</li>
279 <li>Intel and AMD machines running on Win32 with the Cygwin libraries.</li>
280 <li>PowerPC-based Mac OS X boxes, running 10.2 and above.</li>
283 <p>The core LLVM infrastructure uses
284 <a href="http://www.gnu.org/software/autoconf/">GNU autoconf</a> to adapt itself
285 to the machine and operating system on which it is built. However, minor
286 porting may be required to get LLVM to work on new platforms. We welcome your
287 portability patches and reports of successful builds or error messages.</p>
289 <p>Note that the LLVM build system does not currently support directories with
290 spaces on them when running on Win32/cygwin. We strongly recommend running
291 LLVM and the C frontend out of a top-level directory without spaces (e.g.,
292 <tt>/cygdrive/c/llvm</tt>). Also, make sure to install <b>all</b> of the
293 cygwin packages. By default, many important tools are not installed that
294 are needed by the LLVM build process or test suite (e.g., /bin/time). Finally,
295 please make sure that there are no directories with spaces in them in your
296 PATH environment variable.</p>
300 <!-- *********************************************************************** -->
301 <div class="doc_section">
302 <a name="knownproblems">Known Problems</a>
304 <!-- *********************************************************************** -->
306 <div class="doc_text">
308 <p>This section contains all known problems with the LLVM system, listed by
309 component. As new problems are discovered, they will be added to these
310 sections. If you run into a problem, please check the <a
311 href="http://llvm.cs.uiuc.edu/bugs/">LLVM bug database</a> and submit a bug if
312 there isn't already one.</p>
316 <!-- ======================================================================= -->
317 <div class="doc_subsection">
318 <a name="experimental">Experimental features included with this release</a>
321 <div class="doc_text">
323 <p>The following components of this LLVM release are either untested, known to
324 be broken or unreliable, or are in early development. These components should
325 not be relied on, and bugs should not be filed against them, but they may be
326 useful to some people. In particular, if you would like to work on one of these
327 components, please contact us on the llvmdev list.</p>
330 <li>The following passes are incomplete or buggy: <tt>-pgmdep, -memdep,
331 -ipmodref, -cee, -branch-combine, -instloops, -paths</tt></li>
332 <li>The <tt>-pre</tt> pass is incomplete (there are cases it doesn't handle that
333 it should) and not thoroughly tested.</li>
334 <li>The <tt>llvm-db</tt> tool is in a very early stage of development.</li>
339 <!-- ======================================================================= -->
340 <div class="doc_subsection">
341 <a name="core">Known problems with the LLVM Core</a>
344 <div class="doc_text">
347 <li>In the JIT, <tt>dlsym</tt> on a symbol compiled by the JIT will not work.
349 <li>The JIT does not use mutexes to protect its internal data structures. As
350 such, execution of a threaded program could cause these data structures to be
353 <li>Linking in static archive files (.a files) is slow by default because
354 there is no symbol table in the archive. To remedy this, run
355 <a href="CommandGuide/html/llvm-ranlib.html"><tt>llvm-ranlib</tt></a> on the
356 archive to add an LLVM symbol table.
358 <li>The gccld program <a href="http://llvm.cs.uiuc.edu/PR139">does not link
359 objects/archives in the order specified on the command line.</a>
361 <li><a href="http://llvm.cs.uiuc.edu/PR240">The lower-invoke pass does not
362 mark values live across a setjmp as volatile</a>. This missing feature
363 only affects targets whose setjmp/longjmp libraries do not save and restore
364 the entire register file.</li>
368 <!-- ======================================================================= -->
369 <div class="doc_subsection">
370 <a name="c-fe">Known problems with the C front-end</a>
373 <!-- _______________________________________________________________________ -->
374 <div class="doc_subsubsection">Bugs</div>
376 <div class="doc_text">
378 <li>C99 Variable sized arrays do not release stack memory when they go out of
379 scope. Thus, the following program may run out of stack space:
381 for (i = 0; i != 1000000; ++i) {
387 <li>Initialization of global union variables can only be done <a
388 href="http://llvm.cs.uiuc.edu/bugs/show_bug.cgi?id=162">with the largest union
391 <li><a href="http://llvm.cs.uiuc.edu/PR244">[llvm-gcc] Error when an implicitly
392 external function is re-declared as static</a></li>
397 <!-- _______________________________________________________________________ -->
398 <div class="doc_subsubsection">
402 <div class="doc_text">
406 <li>Inline assembly is not yet supported.</li>
408 <li>"long double" is transformed by the front-end into "double". There is no
409 support for floating point data types of any size other than 32 and 64
412 <li>The following Unix system functionality has not been tested and may not
415 <li><tt>sigsetjmp</tt>, <tt>siglongjmp</tt> - These are not turned into the
416 appropriate <tt>invoke</tt>/<tt>unwind</tt> instructions. Note that
417 <tt>setjmp</tt> and <tt>longjmp</tt> <em>are</em> compiled correctly.
418 <li><tt>getcontext</tt>, <tt>setcontext</tt>, <tt>makecontext</tt>
419 - These functions have not been tested.
422 <li>Although many GCC extensions are supported, some are not. In particular,
423 the following extensions are known to <b>not be</b> supported:
425 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Local-Labels.html#Local%20Labels">Local Labels</a>: Labels local to a block.</li>
426 <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>
427 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Constructing-Calls.html#Constructing%20Calls">Constructing Calls</a>: Dispatching a call to another function.</li>
428 <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>
429 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Constraints.html#Constraints">Constraints</a>: Constraints for asm operands.</li>
430 <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>
431 <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>
432 <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>
433 <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>
434 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Thread-Local.html#Thread-Local">Thread-Local</a>: Per-thread variables.</li>
435 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Pragmas.html#Pragmas">Pragmas</a>: Pragmas accepted by GCC.</li>
438 <p>The following GCC extensions are <b>partially</b> supported. An ignored
439 attribute means that the LLVM compiler ignores the presence of the attribute,
440 but the code should still work. An unsupported attribute is one which is
441 ignored by the LLVM compiler and will cause a different interpretation of
445 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Variable-Length.html#Variable%20Length">Variable Length</a>:
446 Arrays whose length is computed at run time.<br>
447 Supported, but allocated stack space is not freed until the function returns (noted above).</li>
449 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Function-Attributes.html#Function%20Attributes">Function Attributes</a>:
451 Declaring that functions have no side effects or that they can never
454 <b>Supported:</b> <tt>format</tt>, <tt>format_arg</tt>, <tt>non_null</tt>,
455 <tt>constructor</tt>, <tt>destructor</tt>, <tt>unused</tt>,
456 <tt>deprecated</tt>, <tt>warn_unused_result</tt>, <tt>weak</tt><br>
458 <b>Ignored:</b> <tt>noreturn</tt>, <tt>noinline</tt>,
459 <tt>always_inline</tt>, <tt>pure</tt>, <tt>const</tt>, <tt>nothrow</tt>,
460 <tt>malloc</tt>, <tt>no_instrument_function</tt>, <tt>cdecl</tt><br>
462 <b>Unsupported:</b> <tt>used</tt>, <tt>section</tt>, <tt>alias</tt>,
463 <tt>visibility</tt>, <tt>regparm</tt>, <tt>stdcall</tt>,
464 <tt>fastcall</tt>, all other target specific attributes</li>
466 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Variable-Attributes.html#Variable%20Attributes">Variable Attributes</a>:
467 Specifying attributes of variables.<br>
468 <b>Supported:</b> <tt>cleanup</tt>, <tt>common</tt>, <tt>nocommon</tt>,
469 <tt>deprecated</tt>, <tt>transparent_union</tt>,
470 <tt>unused</tt>, <tt>weak</tt><br>
472 <b>Unsupported:</b> <tt>aligned</tt>, <tt>mode</tt>, <tt>packed</tt>,
473 <tt>section</tt>, <tt>shared</tt>, <tt>tls_model</tt>,
474 <tt>vector_size</tt>, <tt>dllimport</tt>,
475 <tt>dllexport</tt>, all target specific attributes.</li>
477 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Type-Attributes.html#Type%20Attributes">Type Attributes</a>: Specifying attributes of types.<br>
478 <b>Supported:</b> <tt>transparent_union</tt>, <tt>unused</tt>,
479 <tt>deprecated</tt>, <tt>may_alias</tt><br>
481 <b>Unsupported:</b> <tt>aligned</tt>, <tt>packed</tt>,
482 all target specific attributes.</li>
484 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Other-Builtins.html#Other%20Builtins">Other Builtins</a>:
485 Other built-in functions.<br>
486 We support all builtins which have a C language equivalent (e.g.,
487 <tt>__builtin_cos</tt>), <tt>__builtin_alloca</tt>,
488 <tt>__builtin_types_compatible_p</tt>, <tt>__builtin_choose_expr</tt>,
489 <tt>__builtin_constant_p</tt>, and <tt>__builtin_expect</tt>
490 (currently ignored). We also support builtins for ISO C99 floating
491 point comparison macros (e.g., <tt>__builtin_islessequal</tt>).</li>
494 <p>The following extensions <b>are</b> known to be supported:</p>
497 <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>
498 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Statement-Exprs.html#Statement%20Exprs">Statement Exprs</a>: Putting statements and declarations inside expressions.</li>
499 <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>
500 <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>
501 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Conditionals.html#Conditionals">Conditionals</a>: Omitting the middle operand of a <code>?:</code> expression.</li>
502 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Long-Long.html#Long%20Long">Long Long</a>: Double-word integers.</li>
503 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Complex.html#Complex">Complex</a>: Data types for complex numbers.</li>
504 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Hex-Floats.html#Hex%20Floats">Hex Floats</a>:Hexadecimal floating-point constants.</li>
505 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Zero-Length.html#Zero%20Length">Zero Length</a>: Zero-length arrays.</li>
506 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Empty-Structures.html#Empty%20Structures">Empty Structures</a>: Structures with no members.</li>
507 <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>
508 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Escaped-Newlines.html#Escaped%20Newlines">Escaped Newlines</a>: Slightly looser rules for escaped newlines.</li>
509 <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>
510 <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>
511 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Initializers.html#Initializers">Initializers</a>: Non-constant initializers.</li>
512 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Compound-Literals.html#Compound%20Literals">Compound Literals</a>: Compound literals give structures, unions,
513 or arrays as values.</li>
514 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Designated-Inits.html#Designated%20Inits">Designated Inits</a>: Labeling elements of initializers.</li>
515 <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>
516 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Case-Ranges.html#Case%20Ranges">Case Ranges</a>: `case 1 ... 9' and such.</li>
517 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Mixed-Declarations.html#Mixed%20Declarations">Mixed Declarations</a>: Mixing declarations and code.</li>
518 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Function-Prototypes.html#Function%20Prototypes">Function Prototypes</a>: Prototype declarations and old-style definitions.</li>
519 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/C---Comments.html#C++%20Comments">C++ Comments</a>: C++ comments are recognized.</li>
520 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Dollar-Signs.html#Dollar%20Signs">Dollar Signs</a>: Dollar sign is allowed in identifiers.</li>
521 <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>
522 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Alignment.html#Alignment">Alignment</a>: Inquiring about the alignment of a type or variable.</li>
523 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Inline.html#Inline">Inline</a>: Defining inline functions (as fast as macros).</li>
524 <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>
525 <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>
526 <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>
527 <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>
528 <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>
529 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Attribute-Syntax.html#Attribute%20Syntax">Attribute Syntax</a>: Formal syntax for attributes.</li>
534 <p>If you run into GCC extensions which have not been included in any of these
535 lists, please let us know (also including whether or not they work).</p>
539 <!-- ======================================================================= -->
540 <div class="doc_subsection">
541 <a name="c++-fe">Known problems with the C++ front-end</a>
544 <div class="doc_text">
546 <p>For this release, the C++ front-end is considered to be fully functional but
547 has not been tested as thoroughly as the C front-end. It has been tested and
548 works for a number of non-trivial programs, but there may be lurking bugs.
549 Please report any bugs or problems.</p>
553 <!-- _______________________________________________________________________ -->
554 <div class="doc_subsubsection">Bugs</div>
556 <div class="doc_text">
559 <li>The C++ front-end inherits all problems afflicting the <a href="#c-fe">C
562 <li><b>IA-64 specific</b>: The C++ front-end does not use <a
563 href="http://llvm.cs.uiuc.edu/PR406">IA64 ABI compliant layout of v-tables</a>.
564 In particular, it just stores function pointers instead of function
565 descriptors in the vtable. This bug prevents mixing C++ code compiled with
566 LLVM with C++ objects compiled by other C++ compilers.</li>
572 <!-- _______________________________________________________________________ -->
573 <div class="doc_subsubsection">
577 <div class="doc_text">
581 <li>The C++ front-end is based on a pre-release of the GCC 3.4 C++ parser. This
582 parser is significantly more standards compliant (and picky) than prior GCC
583 versions. For more information, see the C++ section of the <a
584 href="http://gcc.gnu.org/gcc-3.4/changes.html">GCC 3.4 release notes</a>.</li>
586 <li>Destructors for local objects are not always run when a <tt>longjmp</tt> is
587 performed. In particular, destructors for objects in the <tt>longjmp</tt>ing
588 function and in the <tt>setjmp</tt> receiver function may not be run.
589 Objects in intervening stack frames will be destroyed, however (which is
590 better than most compilers).</li>
592 <li>The LLVM C++ front-end follows the <a
593 href="http://www.codesourcery.com/cxx-abi">Itanium C++ ABI</a>.
594 This document, which is not Itanium specific, specifies a standard for name
595 mangling, class layout, v-table layout, RTTI formats, and other C++
596 representation issues. Because we use this API, code generated by the LLVM
597 compilers should be binary compatible with machine code generated by other
598 Itanium ABI C++ compilers (such as G++, the Intel and HP compilers, etc).
599 <i>However</i>, the exception handling mechanism used by LLVM is very
600 different from the model used in the Itanium ABI, so <b>exceptions will not
601 interact correctly</b>. </li>
607 <!-- ======================================================================= -->
608 <div class="doc_subsection">
609 <a name="x86-be">Known problems with the X86 back-end</a>
612 <div class="doc_text">
620 <!-- ======================================================================= -->
621 <div class="doc_subsection">
622 <a name="sparcv9-be">Known problems with the SparcV9 back-end</a>
625 <div class="doc_text">
628 <li><a href="http://llvm.cs.uiuc.edu/PR60">[sparcv9] SparcV9 backend miscompiles
629 several programs in the LLVM test suite</a></li>
634 <!-- ======================================================================= -->
635 <div class="doc_subsection">
636 <a name="ppc-be">Known problems with the PowerPC back-end</a>
639 <div class="doc_text">
647 <!-- ======================================================================= -->
648 <div class="doc_subsection">
649 <a name="c-be">Known problems with the C back-end</a>
652 <div class="doc_text">
656 <li>The C back-end produces code that violates the ANSI C Type-Based Alias
657 Analysis rules. As such, special options may be necessary to compile the code
658 (for example, GCC requires the <tt>-fno-strict-aliasing</tt> option). This
659 problem probably cannot be fixed.</li>
661 <li><a href="http://llvm.cs.uiuc.edu/PR33">Initializers for global variables</a>
662 cannot include special floating point numbers like Not-A-Number or
665 <li><a href="http://llvm.cs.uiuc.edu/PR56">Zero arg vararg functions are not
666 supported</a>. This should not affect LLVM produced by the C or C++
673 <!-- *********************************************************************** -->
674 <div class="doc_section">
675 <a name="additionalinfo">Additional Information</a>
677 <!-- *********************************************************************** -->
679 <div class="doc_text">
681 <p>A wide variety of additional information is available on the LLVM web page,
682 including mailing lists and publications describing algorithms and components
683 implemented in LLVM. The web page also contains versions of the API
684 documentation which is up-to-date with the CVS version of the source code. You
685 can access versions of these documents specific to this release by going into
686 the "<tt>llvm/doc/</tt>" directory in the LLVM tree.</p>
688 <p>If you have any questions or comments about LLVM, please feel free to contact
689 us via the <a href="http://mail.cs.uiuc.edu/mailman/listinfo/llvmdev">mailing
694 <!-- *********************************************************************** -->
698 <a href="http://jigsaw.w3.org/css-validator/check/referer"><img
699 src="http://jigsaw.w3.org/css-validator/images/vcss" alt="Valid CSS!"></a>
700 <a href="http://validator.w3.org/check/referer"><img
701 src="http://www.w3.org/Icons/valid-html401" alt="Valid HTML 4.01!" /></a>
703 <a href="http://llvm.cs.uiuc.edu">The LLVM Compiler Infrastructure</a><br>
704 Last modified: $Date$