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.2 Release Notes</title>
10 <div class="doc_title">
11 LLVM 1.2 Release Notes
15 <li><a href="#intro">Introduction</a></li>
16 <li><a href="#whatsnew">What's New?</a></li>
17 <li><a href="#portability">Portability and Supported Platforms</a></li>
18 <li><a href="#install-instructions">Installation Instructions</a></li>
19 <li><a href="#knownproblems">Known Problems</a>
21 <li><a href="#core">Known problems with the LLVM Core</a>
22 <li><a href="#c-fe">Known problems with the C Front-end</a>
23 <li><a href="#c++-fe">Known problems with the C++ Front-end</a>
24 <li><a href="#x86-be">Known problems with the X86 Back-end</a>
25 <li><a href="#sparc-be">Known problems with the Sparc Back-end</a>
26 <li><a href="#c-be">Known problems with the C back-end</a>
28 <li><a href="#additionalinfo">Additional Information</a></li>
31 <div class="doc_text">
32 <p><b>Written by the <a href="http://llvm.cs.uiuc.edu">LLVM team</a></b><p>
35 <!-- *********************************************************************** -->
36 <div class="doc_section">
37 <a name="intro">Introduction</a>
39 <!-- *********************************************************************** -->
41 <div class="doc_text">
43 <p>This document contains the release notes for the LLVM compiler
44 infrastructure, release 1.2. 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.2/">LLVM 1.2 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 third public release of the LLVM compiler infrastructure.
75 <p>At this time, LLVM is known to correctly compile and run all non-unwinding C
76 & C++ SPEC CPU2000 benchmarks, the Olden benchmarks, and the Ptrdist
77 benchmarks. It has also been used to compile <b>many</b> other programs. LLVM
78 now also works with a broad variety of C++ programs, though it has still
79 received much less testing than the C front-end.
83 The LLVM native code generators are very stable but do not currently support
84 unwinding (exception throwing or <tt>longjmp</tt>ing), which prevent them from
85 working with programs like the <tt>253.perlbmk</tt> in SPEC CPU2000. The C
86 backend and the rest of LLVM supports these programs, so you can
87 still use LLVM with them. Support for unwinding will be added in a future
92 <!--=========================================================================-->
93 <div class="doc_subsubsection">
94 This release implements the following new features:
103 <!--=========================================================================-->
104 <div class="doc_subsubsection">
105 In this release, the following missing features were implemented:
114 <!--=========================================================================-->
115 <div class="doc_subsubsection">
116 In this release, the following Quality of Implementation issues were fixed:
121 <li><a href="http://llvm.cs.uiuc.edu/PR135">JIT should lazily initialize global variables</a></li>
122 <li><a href="http://llvm.cs.uiuc.edu/PR192">[X86] X86 Backend never releases memory for machine code structures</a></li>
123 <li><a href="http://llvm.cs.uiuc.edu/PR196">[vmcore] OpaqueType objects memory leak</a></li>
124 <li><a href="http://llvm.cs.uiuc.edu/PR182">[llvmgcc] C front-end does not compile "extern inline" into linkonce</a></li>
125 <li><a href="http://llvm.cs.uiuc.edu/PR73">Bytecode format inconsistent</a></li>
128 <!--=========================================================================-->
129 <div class="doc_subsubsection">
130 In this release, the following Code Quality issues were fixed:
135 <li><a href="http://llvm.cs.uiuc.edu/PR187">[loopsimplify] Many pointless phi nodes are created</a></li>
141 <!--=========================================================================-->
142 <div class="doc_subsubsection">
143 In this release, the following bugs in the previous release were fixed:
146 <p>Bugs in the LLVM Core:</p>
149 <li><a href="http://llvm.cs.uiuc.edu/PR179">[licm] LICM promotes volatile memory
150 locations to registers</a></li>
151 <li><a href="http://llvm.cs.uiuc.edu/PR191">[licm] Memory read after free causes
152 infrequent crash</a></li>
153 <li><a href="http://llvm.cs.uiuc.edu/PR194">[indvars] Induction variable
154 canonicalization always makes 32-bit indvars</a></li>
155 <li><a href="http://llvm.cs.uiuc.edu/PR193">[constantmerge] Merging globals can
156 cause use of invalid pointers!</a></li>
161 <p>Bugs in the C/C++ front-end:</p>
164 <li><a href="http://llvm.cs.uiuc.edu/PR186">Need weak linkage on memory
165 management functions in libc runtime to allow them to be overriden</a></li>
166 <li><a href="http://llvm.cs.uiuc.edu/PR202">[llvm-gcc] asserts when an extern inline function is redefined</a></li>
167 <li><a href="http://llvm.cs.uiuc.edu/PR204">[llvmg++] Dynamically initialized constants cannot be marked 'constant'</a></li>
172 <!-- *********************************************************************** -->
173 <div class="doc_section">
174 <a name="portability">Portability and Supported Platforms</a>
176 <!-- *********************************************************************** -->
178 <div class="doc_text">
180 <p>LLVM has been extensively tested on Intel and AMD machines running Red
181 Hat Linux and FreeBSD. It has also been tested on Sun UltraSPARC workstations running Solaris 8.
183 LLVM works on Mac OS X 10.3 and above, but only with the C backend or
184 interpreter (no native backend for the PowerPC is available yet).
185 The core LLVM infrastructure uses "autoconf" for portability, so hopefully we
186 work on more platforms than that. However, it is likely that we
187 missed something and that minor porting is required to get LLVM to work on
188 new platforms. We welcome portability patches and error messages.</p>
192 <!-- *********************************************************************** -->
193 <div class="doc_section">
194 <a name="knownproblems">Known Problems</a>
196 <!-- *********************************************************************** -->
198 <div class="doc_text">
200 <p>This section contains all known problems with the LLVM system, listed by
201 component. As new problems are discovered, they will be added to these
202 sections. If you run into a problem, please check the <a
203 href="http://llvm.cs.uiuc.edu/bugs/">LLVM bug database</a> and submit a bug if
204 there isn't already one.</p>
208 <!-- _______________________________________________________________________ -->
210 </ul><h4><a name="portability"><hr size=0>Portability Problems</h4><ul>
214 <!-- ======================================================================= -->
215 <div class="doc_subsection">
216 <a name="core">Known problems with the LLVM Core</a>
219 <div class="doc_text">
223 <li>In the JIT, <tt>dlsym</tt> on a symbol compiled by the JIT will not
226 <li>The JIT does not use mutexes to protect its internal data structures. As
227 such, execution of a threaded program could cause these data structures to be
230 <li>It is not possible to <tt>dlopen</tt> an LLVM bytecode file in the JIT.</li>
232 <li>Linking in static archive files (.a files) is very slow (there is no symbol
233 table in the archive).</li>
235 <li><a href="http://llvm.cs.uiuc.edu/PR82">LLVM cannot handle structures with
236 more than 256 elements</a>.</li>
240 <a href="http://llvm.cs.uiuc.edu/bugs/show_bug.cgi?id=139">
241 does not link objects/archives in the order specified on the command line.
246 <a href="http://llvm.cs.uiuc.edu/bugs/show_bug.cgi?id=174">
247 Tail duplication does not update SSA form correctly.
254 <!-- ======================================================================= -->
255 <div class="doc_subsection">
256 <a name="c-fe">Known problems with the C front-end</a>
259 <!-- _______________________________________________________________________ -->
260 <div class="doc_subsubsection">Bugs</div>
262 <div class="doc_text">
264 <li>C99 Variable sized arrays do not release stack memory when they go out of
265 scope. Thus, the following program may run out of stack space:
267 for (i = 0; i != 1000000; ++i) {
274 Initialization of global union variables can only be done
275 <a href="http://llvm.cs.uiuc.edu/bugs/show_bug.cgi?id=162">with the largest
280 <a href="http://llvm.cs.uiuc.edu/bugs/show_bug.cgi?id=182">
281 Functions marked "extern inline" are not compiled into LLVM with linkonce
288 The memory management functions in the libc runtime
289 <a href="http://llvm.cs.uiuc.edu/PR186">need weak linkage so that they can be
296 <!-- _______________________________________________________________________ -->
297 <div class="doc_subsubsection">
301 <div class="doc_text">
305 <li>Inline assembly is not yet supported.</li>
307 <li>"long double" is transformed by the front-end into "double". There is no
308 support for floating point data types of any size other than 32 and 64
311 <li>The following Unix system functionality has not been tested and may not
314 <li><tt>sigsetjmp</tt>, <tt>siglongjmp</tt> - These are not turned into the
315 appropriate <tt>invoke</tt>/<tt>unwind</tt> instructions. Note that
316 <tt>setjmp</tt> and <tt>longjmp</tt> <em>are</em> compiled correctly.
317 <li><tt>getcontext</tt>, <tt>setcontext</tt>, <tt>makecontext</tt>
318 - These functions have not been tested.
321 <li>Although many GCC extensions are supported, some are not. In particular,
322 the following extensions are known to <b>not be</b> supported:
324 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Local-Labels.html#Local%20Labels">Local Labels</a>: Labels local to a block.</li>
325 <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>
326 <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>
327 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Constructing-Calls.html#Constructing%20Calls">Constructing Calls</a>: Dispatching a call to another function.</li>
328 <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>
329 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Constraints.html#Constraints">Constraints</a>: Constraints for asm operands.</li>
330 <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>
331 <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>
332 <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>
333 <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>
334 <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>
335 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Thread-Local.html#Thread-Local">Thread-Local</a>: Per-thread variables.</li>
336 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Pragmas.html#Pragmas">Pragmas</a>: Pragmas accepted by GCC.</li>
339 <p>The following GCC extensions are <b>partially</b> supported. An ignored
340 attribute means that the LLVM compiler ignores the presence of the attribute,
341 but the code should still work. An unsupported attribute is one which is
342 ignored by the LLVM compiler and will cause a different interpretation of
346 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Variable-Length.html#Variable%20Length">Variable Length</a>:
347 Arrays whose length is computed at run time.<br>
348 Supported, but allocated stack space is not freed until the function returns (noted above).</li>
350 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Function-Attributes.html#Function%20Attributes">Function Attributes</a>:
352 Declaring that functions have no side effects or that they can never
355 <b>Supported:</b> <tt>format</tt>, <tt>format_arg</tt>, <tt>non_null</tt>,
356 <tt>constructor</tt>, <tt>destructor</tt>, <tt>unused</tt>,
357 <tt>deprecated</tt>, <tt>warn_unused_result</tt>, <tt>weak</tt><br>
359 <b>Ignored:</b> <tt>noreturn</tt>, <tt>noinline</tt>,
360 <tt>always_inline</tt>, <tt>pure</tt>, <tt>const</tt>, <tt>nothrow</tt>,
361 <tt>malloc</tt>, <tt>no_instrument_function</tt>, <tt>cdecl</tt><br>
363 <b>Unsupported:</b> <tt>used</tt>, <tt>section</tt>, <tt>alias</tt>,
364 <tt>visibility</tt>, <tt>regparm</tt>, <tt>stdcall</tt>,
365 <tt>fastcall</tt>, all other target specific attributes</li>
367 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Variable-Attributes.html#Variable%20Attributes">Variable Attributes</a>:
368 Specifying attributes of variables.<br>
369 <b>Supported:</b> <tt>cleanup</tt>, <tt>common</tt>, <tt>nocommon</tt>,
370 <tt>deprecated</tt>, <tt>transparent_union</tt>,
371 <tt>unused</tt>, <tt>weak</tt><br>
373 <b>Unsupported:</b> <tt>aligned</tt>, <tt>mode</tt>, <tt>packed</tt>,
374 <tt>section</tt>, <tt>shared</tt>, <tt>tls_model</tt>,
375 <tt>vector_size</tt>, <tt>dllimport</tt>,
376 <tt>dllexport</tt>, all target specific attributes.</li>
378 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Type-Attributes.html#Type%20Attributes">Type Attributes</a>: Specifying attributes of types.<br>
379 <b>Supported:</b> <tt>transparent_union</tt>, <tt>unused</tt>,
380 <tt>deprecated</tt>, <tt>may_alias</tt><br>
382 <b>Unsupported:</b> <tt>aligned</tt>, <tt>packed</tt>,
383 all target specific attributes.</li>
385 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Other-Builtins.html#Other%20Builtins">Other Builtins</a>:
386 Other built-in functions.<br>
387 We support all builtins which have a C language equivalent (e.g.,
388 <tt>__builtin_cos</tt>), <tt>__builtin_alloca</tt>,
389 <tt>__builtin_types_compatible_p</tt>, <tt>__builtin_choose_expr</tt>,
390 <tt>__builtin_constant_p</tt>, and <tt>__builtin_expect</tt> (ignored).</li>
394 <p>The following extensions <b>are</b> known to be supported:</p>
397 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Statement-Exprs.html#Statement%20Exprs">Statement Exprs</a>: Putting statements and declarations inside expressions.</li>
398 <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>
399 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Lvalues.html#Lvalues">Lvalues</a>: Using <code>?:</code>, "<code>,</code>" and casts in lvalues.</li>
400 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Conditionals.html#Conditionals">Conditionals</a>: Omitting the middle operand of a <code>?:</code> expression.</li>
401 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Long-Long.html#Long%20Long">Long Long</a>: Double-word integers.</li>
402 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Complex.html#Complex">Complex</a>: Data types for complex numbers.</li>
403 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Hex-Floats.html#Hex%20Floats">Hex Floats</a>:Hexadecimal floating-point constants.</li>
404 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Zero-Length.html#Zero%20Length">Zero Length</a>: Zero-length arrays.</li>
405 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Empty-Structures.html#Empty%20Structures">Empty Structures</a>: Structures with no members.</li>
406 <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>
407 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Escaped-Newlines.html#Escaped%20Newlines">Escaped Newlines</a>: Slightly looser rules for escaped newlines.</li>
408 <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>
409 <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>
410 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Initializers.html#Initializers">Initializers</a>: Non-constant initializers.</li>
411 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Compound-Literals.html#Compound%20Literals">Compound Literals</a>: Compound literals give structures, unions,
412 or arrays as values.</li>
413 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Designated-Inits.html#Designated%20Inits">Designated Inits</a>: Labeling elements of initializers.</li>
414 <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>
415 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Case-Ranges.html#Case%20Ranges">Case Ranges</a>: `case 1 ... 9' and such.</li>
416 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Mixed-Declarations.html#Mixed%20Declarations">Mixed Declarations</a>: Mixing declarations and code.</li>
417 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Function-Prototypes.html#Function%20Prototypes">Function Prototypes</a>: Prototype declarations and old-style definitions.</li>
418 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/C---Comments.html#C++%20Comments">C++ Comments</a>: C++ comments are recognized.</li>
419 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Dollar-Signs.html#Dollar%20Signs">Dollar Signs</a>: Dollar sign is allowed in identifiers.</li>
420 <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>
421 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Alignment.html#Alignment">Alignment</a>: Inquiring about the alignment of a type or variable.</li>
422 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Inline.html#Inline">Inline</a>: Defining inline functions (as fast as macros).</li>
423 <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>
424 <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>
425 <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>
426 <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>
427 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Attribute-Syntax.html#Attribute%20Syntax">Attribute Syntax</a>: Formal syntax for attributes.</li>
432 <p>If you run into GCC extensions which have not been included in any of these
433 lists, please let us know (also including whether or not they work).</p>
437 <!-- ======================================================================= -->
438 <div class="doc_subsection">
439 <a name="c++-fe">Known problems with the C++ front-end</a>
442 <div class="doc_text">
444 <p>For this release, the C++ front-end is considered to be fully functional but
445 has not been tested as thoroughly as the C front-end. It has been tested and
446 works for a number of non-trivial programs, but there may be lurking bugs.
447 Please report any bugs or problems.</p>
451 <!-- _______________________________________________________________________ -->
452 <div class="doc_subsubsection">
456 <div class="doc_text">
459 <li>The C++ front-end inherits all problems afflicting the <a href="#c-fe">C
463 <a href="http://llvm.cs.uiuc.edu/bugs/show_bug.cgi?id=137">
464 Code is generated for empty classes.
470 <!-- _______________________________________________________________________ -->
471 <div class="doc_subsubsection">
475 <div class="doc_text">
479 <li>The C++ front-end is based on a pre-release of the GCC 3.4 C++ parser. This
480 parser is significantly more standards compliant (and picky) than prior GCC
481 versions. For more information, see the C++ section of the <a
482 href="http://gcc.gnu.org/gcc-3.4/changes.html">GCC 3.4 release notes</a>.</li>
484 <li>Destructors for local objects are not always run when a <tt>longjmp</tt> is
485 performed. In particular, destructors for objects in the <tt>longjmp</tt>ing
486 function and in the <tt>setjmp</tt> receiver function may not be run.
487 Objects in intervening stack frames will be destroyed, however (which is
488 better than most compilers).</li>
490 <li>The LLVM C++ front-end follows the <a
491 href="http://www.codesourcery.com/cxx-abi">Itanium C++ ABI</a>.
492 This document, which is not Itanium specific, specifies a standard for name
493 mangling, class layout, v-table layout, RTTI formats, and other C++
494 representation issues. Because we use this API, code generated by the LLVM
495 compilers should be binary compatible with machine code generated by other
496 Itanium ABI C++ compilers (such as G++, the Intel and HP compilers, etc).
497 <i>However</i>, the exception handling mechanism used by LLVM is very
498 different from the model used in the Itanium ABI, so <b>exceptions will not
499 interact correctly</b>. </li>
505 <!-- ======================================================================= -->
506 <div class="doc_subsection">
507 <a name="x86-be">Known problems with the X86 back-end</a>
510 <div class="doc_text">
514 <li>The X86 code generator <a
515 href="http://llvm.cs.uiuc.edu/PR16">does not currently
516 support the <tt>unwind</tt> instruction</a>, so code that throws a C++ exception
517 or calls the C <tt>longjmp</tt> function will abort.</li>
523 <!-- ======================================================================= -->
524 <div class="doc_subsection">
525 <a name="sparc-be">Known problems with the Sparc back-end</a>
528 <div class="doc_text">
532 <li>The Sparc code generator <a
533 href="http://llvm.cs.uiuc.edu/PR15">does not currently
534 support the <tt>unwind</tt> instruction</a>, so code that throws a C++ exception
535 or calls the C <tt>longjmp</tt> function will abort.</li>
538 <a href="http://llvm.cs.uiuc.edu/bugs/show_bug.cgi?id=167">
539 The llc program can crash on legal code.
546 <!-- ======================================================================= -->
547 <div class="doc_subsection">
548 <a name="c-be">Known problems with the C back-end</a>
551 <div class="doc_text">
555 <li>The C back-end produces code that violates the ANSI C Type-Based Alias
556 Analysis rules. As such, special options may be necessary to compile the code
557 (for example, GCC requires the <tt>-fno-strict-aliasing</tt> option). This
558 problem probably cannot be fixed.</li>
560 <li><a href="http://llvm.cs.uiuc.edu/PR33">Initializers for global variables</a>
561 cannot include special floating point numbers like Not-A-Number or
564 <li><a href="http://llvm.cs.uiuc.edu/PR56">Zero arg vararg functions are not
565 supported</a>. This should not affect LLVM produced by the C or C++
572 <!-- *********************************************************************** -->
573 <div class="doc_section">
574 <a name="additionalinfo">Additional Information</a>
576 <!-- *********************************************************************** -->
578 <div class="doc_text">
580 <p>A wide variety of additional information is available on the LLVM web page,
581 including mailing lists and publications describing algorithms and components
582 implemented in LLVM. The web page also contains versions of the API
583 documentation which is up-to-date with the CVS version of the source code. You
584 can access versions of these documents specific to this release by going into
585 the "<tt>llvm/doc/</tt>" directory in the LLVM tree.</p>
587 <p>If you have any questions or comments about LLVM, please feel free to contact
588 us via the <a href="http://mail.cs.uiuc.edu/mailman/listinfo/llvmdev">mailing
593 <!-- *********************************************************************** -->
597 <a href="http://jigsaw.w3.org/css-validator/check/referer"><img
598 src="http://jigsaw.w3.org/css-validator/images/vcss" alt="Valid CSS!"></a>
599 <a href="http://validator.w3.org/check/referer"><img
600 src="http://www.w3.org/Icons/valid-html401" alt="Valid HTML 4.01!" /></a>
602 <a href="http://llvm.cs.uiuc.edu">The LLVM Compiler Infrastructure</a><br>
603 Last modified: $Date$