1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
2 "http://www.w3.org/TR/html4/strict.dtd">
5 <link rel="stylesheet" href="llvm.css" type="text/css">
6 <title>LLVM 1.3 Release Notes</title>
10 <div class="doc_title">LLVM 1.3 Release Notes</div>
13 <li><a href="#intro">Introduction</a></li>
14 <li><a href="#whatsnew">What's New?</a></li>
15 <li><a href="GettingStarted.html">Installation Instructions</a></li>
16 <li><a href="#portability">Portability and Supported Platforms</a></li>
17 <li><a href="#knownproblems">Known Problems</a>
19 <li><a href="#experimental">Experimental features included in this
21 <li><a href="#core">Known problems with the LLVM Core</a>
22 <li><a href="#c-fe">Known problems with the C Front-end</a>
23 <li><a href="#c++-fe">Known problems with the C++ Front-end</a>
24 <li><a href="#x86-be">Known problems with the X86 Back-end</a>
25 <li><a href="#sparc-be">Known problems with the Sparc Back-end</a>
26 <li><a href="#c-be">Known problems with the C back-end</a>
28 <li><a href="#additionalinfo">Additional Information</a></li>
31 <div class="doc_author">
32 <p>Written by the <a href="http://llvm.cs.uiuc.edu">LLVM team</a><p>
35 <!-- *********************************************************************** -->
36 <div class="doc_section">
37 <a name="intro">Introduction</a>
39 <!-- *********************************************************************** -->
41 <div class="doc_text">
43 <p>This document contains the release notes for the LLVM compiler
44 infrastructure, release 1.3. Here we describe the status of LLVM, including any
45 known problems and bug fixes from the previous release. The most up-to-date
46 version of this document can be found on the <a
47 href="http://llvm.cs.uiuc.edu/releases/1.3/">LLVM 1.3 web site</a>. If you are
48 not reading this on the LLVM web pages, you should probably go there because
49 this document may be updated after the release.</p>
51 <p>For more information about LLVM, including information about potentially more
52 current releases, please check out the <a href="http://llvm.cs.uiuc.edu">main
53 web site</a>. If you have questions or comments, the <a
54 href="http://mail.cs.uiuc.edu/mailman/listinfo/llvmdev">LLVM developer's mailing
55 list</a> is a good place to send them.</p>
57 <p>Note that if you are reading this file from CVS, this document applies
58 to the <i>next</i> release, not the current one. To see the release notes for
59 the current or previous releases, see the <a
60 href="http://llvm.cs.uiuc.edu/releases/">releases page</a>.</p>
64 <!-- *********************************************************************** -->
65 <div class="doc_section">
66 <a name="whatsnew">What's New?</a>
68 <!-- *********************************************************************** -->
70 <div class="doc_text">
72 <p>This is the fourth public release of the LLVM compiler infrastructure. This
73 release primarily improves the <a href="#codequality">performance of the
74 code</a> produced by all aspects of the LLVM compiler and adds many <a
75 href="#newfeatures">new features</a>, and <a href="#bugfix">fixes a few
78 <p> At this time, LLVM is known to correctly compile and run all C & C++
79 SPEC CPU2000 benchmarks, the Olden benchmarks, and the Ptrdist benchmarks. It
80 has also been used to compile <b>many</b> other programs. LLVM now also works
81 with a broad variety of C++ programs, though it has still received less testing
82 than the C front-end.</p>
86 <!--=========================================================================-->
87 <div class="doc_subsubsection">
88 <a name="newfeatures">This release implements the following new features:</a>
91 <div class="doc_text">
94 <li>The LLVM <a href="LangRef.html#i_select"><tt>select</tt></a> instruction is
95 now fully implemented and supported by all transformations, native code
96 generators, and the interpreter.</li>
97 <li>Bugpoint can now narrow down code-generation bugs to a loop nest, where
98 before it could only narrow them down to a function being miscompiled.</li>
99 <li><a href="http://llvm.cs.uiuc.edu/PR40">Bugpoint can now debug arbitrary
100 modes of llc</a> and lli, by passing them command line flags (e.g.,
101 <tt>-regalloc=linearscan</tt>, <tt>-enable-correct-eh-support</tt>, etc.) </li>
102 <li>The Control Flow Graph in the native code generators is no longer
103 constrained to be the same as the CFG for the LLVM input code.</li>
104 <li>The LLVM induction variable analysis routines have been rewritten.</li>
105 <li>LLVM now has new loop unrolling and loop unswitching passes.</li>
106 <li>The induction variable substitution pass performs linear function test
107 replacement and exit value replacement optimizations.</li>
108 <li>LLVM now has first-class support for <a href="GarbageCollection.html">Accurate
109 Garbage Collection</a>, enabling the use of aggressive copying and generational
111 <li>LLVM now includes an implementation of Andersen's interprocedural alias
112 analysis algorithm.</li>
113 <li>Bugpoint can <a href="http://llvm.cs.uiuc.edu/PR327">extract individual
114 basic blocks</a> to track down reduce miscompilation testcases.</li>
115 <li>LLVM and the C front-end now work under Win32 using the
116 <a href="http://www.cygwin.com">Cygwin</a> runtime libraries.
117 This includes the JIT compiler.</li>
118 <li>The LLVM code generator is now being <a
119 href="CodeGenerator.html">documented</a>.</li>
120 <li>There is a new tool, llvm-abcd, the Analysis of ByteCode Dumper (abcd).
121 This tool can compute basic statistics and bytecode density statistics on a
122 module or function basis and also dump out bytecode in a textual format that
123 is lower level than assembly (values are not resolved from slot numbers).
124 It should only be of interest to (a) those who are working to improve the
125 bytecode format and (b) those who really want to understand or document the
126 details of the bytecode format.</li>
127 <li>The <a href="BytecodeFormat.html">LLVM Bytecode file format</a> is now
128 being documented.</li>
129 <li>LLVM now provides an <a href="LangRef.html#i_isunordered">llvm.isunordered</a> intrinsic
130 for efficient implementation of unordered floating point comparisons.</li>
131 <li>The llvmgcc front-end now supports the GCC builtins for ISO C99 floating
132 point comparison macros (e.g., <tt>__builtin_islessequal</tt>).</li>
138 <!--=========================================================================-->
139 <div class="doc_subsubsection">
140 In this release, the following missing features were implemented:
143 <div class="doc_text">
146 <li><a href="http://llvm.cs.uiuc.edu/PR82">LLVM cannot handle structures with
147 more than 256 elements</a></li>
148 <li><a href="http://llvm.cs.uiuc.edu/PR38">[bugpoint] External functions used in
149 non-instruction entities, such as global constant initializer</a></li>
150 <li><a href="http://llvm.cs.uiuc.edu/PR178">Stacker does not handle targets
151 with 64-bit pointers.</a></li>
152 <li><a href="http://llvm.cs.uiuc.edu/PR290">Bugpoint doesn't support
153 uses of external fns by immediate constant exprs</a></li>
158 <!--=========================================================================-->
159 <div class="doc_subsubsection">
160 <a name="qualityofimp">In this release, the following Quality of Implementation
161 issues were fixed:</a>
164 <div class="doc_text">
167 <li><a href="http://llvm.cs.uiuc.edu/PR305">LLVM tools will happily spew
168 bytecode onto your terminal</a></li>
169 <li><a href="http://llvm.cs.uiuc.edu/PR329">[llvmgcc] type names are not emitted
170 for structure typedefs</a></li>
171 <li>All documentation is now conformant to the HTML 4.01 (Strict) level.</li>
172 <li>The spurious "WARNING: Found global types that are not compatible" warning
173 produced when linking C++ programs has been fixed.</li>
178 <!--=========================================================================-->
179 <div class="doc_subsubsection">
180 In this release, the following build problems were fixed:
183 <div class="doc_text">
185 <li><a href="http://llvm.cs.uiuc.edu/PR301">Minor configure bugs with
186 -disable/enable-povray and -disable-spec</a></li>
187 <li><a href="http://llvm.cs.uiuc.edu/PR289">shell scripts output by gccld don't
188 work if you change PATH</a></li>
189 <li><a href="http://llvm.cs.uiuc.edu/PR364">[llvmgcc] llvmgcc does not compile
190 with gcc 3.4</a></li>
194 <!--=========================================================================-->
195 <div class="doc_subsubsection">
196 <a name="codequality">This release includes the following Code Quality
200 <div class="doc_text">
202 <li>Fixed: <a href="http://llvm.cs.uiuc.edu/PR309">[vmcore] Code quality problem
203 due to long operand of getelementptr</a></li>
205 <li>The X86 backend now generates substantially better code for 64-bit integer
206 and floating point operations.</li>
208 <li>The -inline pass no longer inlines mutually recursive functions until it
209 hits the inlining threshold.</li>
211 <li>The -inline pass no longer misses obvious inlining opportunities just
212 because the callee eventually calls into an external function.</li>
214 <li>The -simplifycfg pass can now "if convert" simple statements into the new
215 <tt>select</tt> instruction.</li>
217 <li>The -loopsimplify pass can now break <a
218 href="http://llvm.cs.uiuc.edu/PR35">natural loops with multiple backedges</a>
219 into multiple nested loops. This enables a variety of subsequent
222 <li>The -adce pass can now eliminate calls to functions that do not not write to
225 <li>The link-time optimizer now runs the -prune-eh pass (to remove unused
226 exception handlers).</li>
228 <li>The -simplifycfg pass can now eliminate simple correlated branches (such as
229 "<tt>if (A < B && A < B)</tt>", and can turn short-circuiting
230 operators into the strict versions when useful (such as "<tt>if (A < B || A
231 > C)</tt>" into "<tt>if (A < B | A > C)</tt>"</li>
233 <li>LLVM now has infrastructure for (simple and sparse conditional) constant
234 propagation of function calls. It currently supports a few math library
235 functions like sqrt/sin/cos/etc.</li>
237 <li>The C backend now emits <a href="http://llvm.cs.uiuc.edu/PR334">Syntactic
238 loops</a> in the code to help C compilers whose optimizers do not recognize
239 loops formed from gotos (like GCC).</li>
241 <li>Fixed: <a href="http://llvm.cs.uiuc.edu/PR368">[sparcv9] null
242 often spilled to constant pool</a>.</li>
246 <!--=========================================================================-->
247 <div class="doc_subsubsection">
248 <a name="bugfix">In this release, the following bugs in the previous release
252 <div class="doc_text">
254 <p>Bugs in the LLVM Core:</p>
257 <li><a href="http://llvm.cs.uiuc.edu/PR330">[vmcore] Linker causes erroneous
259 <li><a href="http://llvm.cs.uiuc.edu/PR306">[loopsimplify] Loop simplify
260 incorrectly updates dominator information</a></li>
261 <li><a href="http://llvm.cs.uiuc.edu/PR310">[tailduplicate] DemoteRegToStack
262 breaks SSA form</a></li>
263 <li><a href="http://llvm.cs.uiuc.edu/PR313">[X86] JIT miscompiles unsigned short
264 to floating point cast</a></li>
265 <li><a href="http://llvm.cs.uiuc.edu/PR332">[adce] Crash handling unreachable
266 code that unwinds</a></li>
267 <li><a href="http://llvm.cs.uiuc.edu/PR333">[sparc] LLC can't emit 2 functions
268 of the same name, both having constant pools</a></li>
269 <li><a href="http://llvm.cs.uiuc.edu/PR337">[livevar] Live variables missed
270 physical register use of aliased definition</a></li>
271 <li><a href="http://llvm.cs.uiuc.edu/PR340">Verifier misses malformed switch instruction</a></li>
272 <li><a href="http://llvm.cs.uiuc.edu/PR315">[jit] abort, don't warn, when missing external functions encountered</a></li>
273 <li><a href="http://llvm.cs.uiuc.edu/PR369">[X86] stackifier crash on floating point setcc X, X</a></li>
276 <p>Bugs in the C/C++ front-end:</p>
279 <li><a href="http://llvm.cs.uiuc.edu/PR326">[llvmgcc] Crash on use of undeclared
281 <li><a href="http://llvm.cs.uiuc.edu/PR298">[llvmgcc] Variable length array
282 indexing miscompiled</a></li>
283 <li><a href="http://llvm.cs.uiuc.edu/PR355">[llvmgcc] Errors handling function prototypes that take opaque structs by-value</a></li>
287 <!-- *********************************************************************** -->
288 <div class="doc_section">
289 <a name="portability">Portability and Supported Platforms</a>
291 <!-- *********************************************************************** -->
293 <div class="doc_text">
295 <p>LLVM is known to work in the following platforms:</p>
298 <li>Intel and AMD machines running Red Hat Linux and FreeBSD (and probably
299 other unix-like systems).</li>
300 <li>Sun UltraSPARC workstations running Solaris 8.</li>
301 <li>PowerPC-based Mac OS X boxes, running 10.3 and above (C backend and
302 interpreter only, no native codegen is available yet).</li>
303 <li>Intel and AMD machines running on Win32 with the Cygwin libraries.</li>
307 <p>The core LLVM infrastructure uses
308 <a href="http://www.gnu.org/software/autoconf/">GNU autoconf</a> to adapt itself
309 to the machine and operating system on which it is built. However, minor
310 porting may be required to get LLVM to work on new platforms. We welcome your
311 portability patches and reports of successful builds or error messages.</p>
313 <p>Note that the LLVM build system does not currently support directories with
314 spaces on them when running on Win32/cygwin. We strongly recommend running
315 LLVM and the C frontend out of a top-level directory without spaces (e.g.,
316 <tt>/cygdrive/c/llvm</tt>). Also, make sure to install <b>all</b> of the
317 cygwin packages. By default, many important tools are not installed that
318 are needed by the LLVM build process or test suite (e.g., /bin/time).</p>
322 <!--=========================================================================-->
323 <div class="doc_subsection">
324 In this release, the following portability problems were fixed:
327 <div class="doc_text">
330 <li><a href="http://llvm.cs.uiuc.edu/PR304">warnings compiling Stacker compiler
332 <li><a href="http://llvm.cs.uiuc.edu/PR308">Archive file reader doesn't
333 understand abbreviated names in headers</a></li>
338 <!-- *********************************************************************** -->
339 <div class="doc_section">
340 <a name="knownproblems">Known Problems</a>
342 <!-- *********************************************************************** -->
344 <div class="doc_text">
346 <p>This section contains all known problems with the LLVM system, listed by
347 component. As new problems are discovered, they will be added to these
348 sections. If you run into a problem, please check the <a
349 href="http://llvm.cs.uiuc.edu/bugs/">LLVM bug database</a> and submit a bug if
350 there isn't already one.</p>
354 <!-- ======================================================================= -->
355 <div class="doc_subsection">
356 <a name="experimental">Experimental features included with this release</a>
359 <div class="doc_text">
361 <p>The following components of this LLVM release are either untested, known to
362 be broken or unreliable, or are in early development. These components should
363 not be relied on, and bugs should not be filed against them, but they may be
364 useful to some people. In particular, if you would like to work on one of these
365 components, please contact us on the llvmdev list.</p>
368 <li>The following passes are incomplete or buggy: <tt>-pgmdep, -memdep,
369 -ipmodref, -sortstructs, -swapstructs, -cee</tt></li>
371 <li>The <tt>-pre</tt> pass is incomplete (there are cases it doesn't handle that
372 it should) and not thoroughly tested.</li>
373 <li>The <tt>llvm-ar</tt> tool is incomplete and probably buggy.</li>
374 <li>The <tt>llvm-db</tt> tool is in a very early stage of development.</li>
379 <!-- ======================================================================= -->
380 <div class="doc_subsection">
381 <a name="core">Known problems with the LLVM Core</a>
384 <div class="doc_text">
388 <li>In the JIT, <tt>dlsym</tt> on a symbol compiled by the JIT will not
391 <li>The JIT does not use mutexes to protect its internal data structures. As
392 such, execution of a threaded program could cause these data structures to be
395 <li>It is not possible to <tt>dlopen</tt> an LLVM bytecode file in the JIT.</li>
397 <li>Linking in static archive files (.a files) is very slow (there is no symbol
398 table in the archive).</li>
400 <li>The gccld program <a href="http://llvm.cs.uiuc.edu/PR139">does not link
401 objects/archives in the order specified on the command line.</a></li>
403 <li><a href="http://llvm.cs.uiuc.edu/PR240">The lower-invoke pass does not mark
404 values live across a setjmp as volatile</a>. This missing feature only affects
405 targets whose setjmp/longjmp libraries do not save and restore the entire
410 <!-- ======================================================================= -->
411 <div class="doc_subsection">
412 <a name="c-fe">Known problems with the C front-end</a>
415 <!-- _______________________________________________________________________ -->
416 <div class="doc_subsubsection">Bugs</div>
418 <div class="doc_text">
420 <li>C99 Variable sized arrays do not release stack memory when they go out of
421 scope. Thus, the following program may run out of stack space:
423 for (i = 0; i != 1000000; ++i) {
429 <li>Initialization of global union variables can only be done <a
430 href="http://llvm.cs.uiuc.edu/bugs/show_bug.cgi?id=162">with the largest union
433 <li><a href="http://llvm.cs.uiuc.edu/PR244">[llvm-gcc] Error when an implicitly
434 external function is re-declared as static</a></li>
439 <!-- _______________________________________________________________________ -->
440 <div class="doc_subsubsection">
444 <div class="doc_text">
448 <li>Inline assembly is not yet supported.</li>
450 <li>"long double" is transformed by the front-end into "double". There is no
451 support for floating point data types of any size other than 32 and 64
454 <li>The following Unix system functionality has not been tested and may not
457 <li><tt>sigsetjmp</tt>, <tt>siglongjmp</tt> - These are not turned into the
458 appropriate <tt>invoke</tt>/<tt>unwind</tt> instructions. Note that
459 <tt>setjmp</tt> and <tt>longjmp</tt> <em>are</em> compiled correctly.
460 <li><tt>getcontext</tt>, <tt>setcontext</tt>, <tt>makecontext</tt>
461 - These functions have not been tested.
464 <li>Although many GCC extensions are supported, some are not. In particular,
465 the following extensions are known to <b>not be</b> supported:
467 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Local-Labels.html#Local%20Labels">Local Labels</a>: Labels local to a block.</li>
468 <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>
469 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Constructing-Calls.html#Constructing%20Calls">Constructing Calls</a>: Dispatching a call to another function.</li>
470 <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>
471 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Constraints.html#Constraints">Constraints</a>: Constraints for asm operands.</li>
472 <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>
473 <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>
474 <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>
475 <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>
476 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Thread-Local.html#Thread-Local">Thread-Local</a>: Per-thread variables.</li>
477 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Pragmas.html#Pragmas">Pragmas</a>: Pragmas accepted by GCC.</li>
480 <p>The following GCC extensions are <b>partially</b> supported. An ignored
481 attribute means that the LLVM compiler ignores the presence of the attribute,
482 but the code should still work. An unsupported attribute is one which is
483 ignored by the LLVM compiler and will cause a different interpretation of
487 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Variable-Length.html#Variable%20Length">Variable Length</a>:
488 Arrays whose length is computed at run time.<br>
489 Supported, but allocated stack space is not freed until the function returns (noted above).</li>
491 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Function-Attributes.html#Function%20Attributes">Function Attributes</a>:
493 Declaring that functions have no side effects or that they can never
496 <b>Supported:</b> <tt>format</tt>, <tt>format_arg</tt>, <tt>non_null</tt>,
497 <tt>constructor</tt>, <tt>destructor</tt>, <tt>unused</tt>,
498 <tt>deprecated</tt>, <tt>warn_unused_result</tt>, <tt>weak</tt><br>
500 <b>Ignored:</b> <tt>noreturn</tt>, <tt>noinline</tt>,
501 <tt>always_inline</tt>, <tt>pure</tt>, <tt>const</tt>, <tt>nothrow</tt>,
502 <tt>malloc</tt>, <tt>no_instrument_function</tt>, <tt>cdecl</tt><br>
504 <b>Unsupported:</b> <tt>used</tt>, <tt>section</tt>, <tt>alias</tt>,
505 <tt>visibility</tt>, <tt>regparm</tt>, <tt>stdcall</tt>,
506 <tt>fastcall</tt>, all other target specific attributes</li>
508 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Variable-Attributes.html#Variable%20Attributes">Variable Attributes</a>:
509 Specifying attributes of variables.<br>
510 <b>Supported:</b> <tt>cleanup</tt>, <tt>common</tt>, <tt>nocommon</tt>,
511 <tt>deprecated</tt>, <tt>transparent_union</tt>,
512 <tt>unused</tt>, <tt>weak</tt><br>
514 <b>Unsupported:</b> <tt>aligned</tt>, <tt>mode</tt>, <tt>packed</tt>,
515 <tt>section</tt>, <tt>shared</tt>, <tt>tls_model</tt>,
516 <tt>vector_size</tt>, <tt>dllimport</tt>,
517 <tt>dllexport</tt>, all target specific attributes.</li>
519 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Type-Attributes.html#Type%20Attributes">Type Attributes</a>: Specifying attributes of types.<br>
520 <b>Supported:</b> <tt>transparent_union</tt>, <tt>unused</tt>,
521 <tt>deprecated</tt>, <tt>may_alias</tt><br>
523 <b>Unsupported:</b> <tt>aligned</tt>, <tt>packed</tt>,
524 all target specific attributes.</li>
526 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Other-Builtins.html#Other%20Builtins">Other Builtins</a>:
527 Other built-in functions.<br>
528 We support all builtins which have a C language equivalent (e.g.,
529 <tt>__builtin_cos</tt>), <tt>__builtin_alloca</tt>,
530 <tt>__builtin_types_compatible_p</tt>, <tt>__builtin_choose_expr</tt>,
531 <tt>__builtin_constant_p</tt>, and <tt>__builtin_expect</tt>
532 (currently ignored). We also support builtins for ISO C99 floating
533 point comparison macros (e.g., <tt>__builtin_islessequal</tt>).</li>
536 <p>The following extensions <b>are</b> known to be supported:</p>
539 <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>
540 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Statement-Exprs.html#Statement%20Exprs">Statement Exprs</a>: Putting statements and declarations inside expressions.</li>
541 <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>
542 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Lvalues.html#Lvalues">Lvalues</a>: Using <code>?:</code>, "<code>,</code>" and casts in lvalues.</li>
543 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Conditionals.html#Conditionals">Conditionals</a>: Omitting the middle operand of a <code>?:</code> expression.</li>
544 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Long-Long.html#Long%20Long">Long Long</a>: Double-word integers.</li>
545 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Complex.html#Complex">Complex</a>: Data types for complex numbers.</li>
546 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Hex-Floats.html#Hex%20Floats">Hex Floats</a>:Hexadecimal floating-point constants.</li>
547 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Zero-Length.html#Zero%20Length">Zero Length</a>: Zero-length arrays.</li>
548 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Empty-Structures.html#Empty%20Structures">Empty Structures</a>: Structures with no members.</li>
549 <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>
550 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Escaped-Newlines.html#Escaped%20Newlines">Escaped Newlines</a>: Slightly looser rules for escaped newlines.</li>
551 <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>
552 <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>
553 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Initializers.html#Initializers">Initializers</a>: Non-constant initializers.</li>
554 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Compound-Literals.html#Compound%20Literals">Compound Literals</a>: Compound literals give structures, unions,
555 or arrays as values.</li>
556 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Designated-Inits.html#Designated%20Inits">Designated Inits</a>: Labeling elements of initializers.</li>
557 <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>
558 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Case-Ranges.html#Case%20Ranges">Case Ranges</a>: `case 1 ... 9' and such.</li>
559 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Mixed-Declarations.html#Mixed%20Declarations">Mixed Declarations</a>: Mixing declarations and code.</li>
560 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Function-Prototypes.html#Function%20Prototypes">Function Prototypes</a>: Prototype declarations and old-style definitions.</li>
561 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/C---Comments.html#C++%20Comments">C++ Comments</a>: C++ comments are recognized.</li>
562 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Dollar-Signs.html#Dollar%20Signs">Dollar Signs</a>: Dollar sign is allowed in identifiers.</li>
563 <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>
564 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Alignment.html#Alignment">Alignment</a>: Inquiring about the alignment of a type or variable.</li>
565 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Inline.html#Inline">Inline</a>: Defining inline functions (as fast as macros).</li>
566 <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>
567 <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>
568 <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>
569 <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>
570 <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>
571 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Attribute-Syntax.html#Attribute%20Syntax">Attribute Syntax</a>: Formal syntax for attributes.</li>
576 <p>If you run into GCC extensions which have not been included in any of these
577 lists, please let us know (also including whether or not they work).</p>
581 <!-- ======================================================================= -->
582 <div class="doc_subsection">
583 <a name="c++-fe">Known problems with the C++ front-end</a>
586 <div class="doc_text">
588 <p>For this release, the C++ front-end is considered to be fully functional but
589 has not been tested as thoroughly as the C front-end. It has been tested and
590 works for a number of non-trivial programs, but there may be lurking bugs.
591 Please report any bugs or problems.</p>
595 <!-- _______________________________________________________________________ -->
596 <div class="doc_subsubsection">Bugs</div>
598 <div class="doc_text">
601 <li>The C++ front-end inherits all problems afflicting the <a href="#c-fe">C
606 <!-- _______________________________________________________________________ -->
607 <div class="doc_subsubsection">
611 <div class="doc_text">
615 <li>The C++ front-end is based on a pre-release of the GCC 3.4 C++ parser. This
616 parser is significantly more standards compliant (and picky) than prior GCC
617 versions. For more information, see the C++ section of the <a
618 href="http://gcc.gnu.org/gcc-3.4/changes.html">GCC 3.4 release notes</a>.</li>
620 <li>Destructors for local objects are not always run when a <tt>longjmp</tt> is
621 performed. In particular, destructors for objects in the <tt>longjmp</tt>ing
622 function and in the <tt>setjmp</tt> receiver function may not be run.
623 Objects in intervening stack frames will be destroyed, however (which is
624 better than most compilers).</li>
626 <li>The LLVM C++ front-end follows the <a
627 href="http://www.codesourcery.com/cxx-abi">Itanium C++ ABI</a>.
628 This document, which is not Itanium specific, specifies a standard for name
629 mangling, class layout, v-table layout, RTTI formats, and other C++
630 representation issues. Because we use this API, code generated by the LLVM
631 compilers should be binary compatible with machine code generated by other
632 Itanium ABI C++ compilers (such as G++, the Intel and HP compilers, etc).
633 <i>However</i>, the exception handling mechanism used by LLVM is very
634 different from the model used in the Itanium ABI, so <b>exceptions will not
635 interact correctly</b>. </li>
641 <!-- ======================================================================= -->
642 <div class="doc_subsection">
643 <a name="x86-be">Known problems with the X86 back-end</a>
646 <div class="doc_text">
654 <!-- ======================================================================= -->
655 <div class="doc_subsection">
656 <a name="sparc-be">Known problems with the Sparc back-end</a>
659 <div class="doc_text">
662 <li>There are several programs in the LLVM testsuite that the Sparc code generator is known to miscompile.</li>
667 <!-- ======================================================================= -->
668 <div class="doc_subsection">
669 <a name="c-be">Known problems with the C back-end</a>
672 <div class="doc_text">
676 <li>The C back-end produces code that violates the ANSI C Type-Based Alias
677 Analysis rules. As such, special options may be necessary to compile the code
678 (for example, GCC requires the <tt>-fno-strict-aliasing</tt> option). This
679 problem probably cannot be fixed.</li>
681 <li><a href="http://llvm.cs.uiuc.edu/PR33">Initializers for global variables</a>
682 cannot include special floating point numbers like Not-A-Number or
685 <li><a href="http://llvm.cs.uiuc.edu/PR56">Zero arg vararg functions are not
686 supported</a>. This should not affect LLVM produced by the C or C++
693 <!-- *********************************************************************** -->
694 <div class="doc_section">
695 <a name="additionalinfo">Additional Information</a>
697 <!-- *********************************************************************** -->
699 <div class="doc_text">
701 <p>A wide variety of additional information is available on the LLVM web page,
702 including mailing lists and publications describing algorithms and components
703 implemented in LLVM. The web page also contains versions of the API
704 documentation which is up-to-date with the CVS version of the source code. You
705 can access versions of these documents specific to this release by going into
706 the "<tt>llvm/doc/</tt>" directory in the LLVM tree.</p>
708 <p>If you have any questions or comments about LLVM, please feel free to contact
709 us via the <a href="http://mail.cs.uiuc.edu/mailman/listinfo/llvmdev">mailing
714 <!-- *********************************************************************** -->
718 <a href="http://jigsaw.w3.org/css-validator/check/referer"><img
719 src="http://jigsaw.w3.org/css-validator/images/vcss" alt="Valid CSS!"></a>
720 <a href="http://validator.w3.org/check/referer"><img
721 src="http://www.w3.org/Icons/valid-html401" alt="Valid HTML 4.01!" /></a>
723 <a href="http://llvm.cs.uiuc.edu">The LLVM Compiler Infrastructure</a><br>
724 Last modified: $Date$