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.5 Release Notes</title>
11 <div class="doc_title">LLVM 1.5 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>
19 <li><a href="#additionalinfo">Additional Information</a></li>
22 <div class="doc_author">
23 <p>Written by the <a href="http://llvm.cs.uiuc.edu">LLVM Team</a><p>
26 <!-- *********************************************************************** -->
27 <div class="doc_section">
28 <a name="intro">Introduction</a>
30 <!-- *********************************************************************** -->
32 <div class="doc_text">
34 <p>This document contains the release notes for the LLVM compiler
35 infrastructure, release 1.5. Here we describe the status of LLVM, including any
36 known problems and improvements from the previous release. The most up-to-date
37 version of this document can be found on the <a
38 href="http://llvm.cs.uiuc.edu/releases/1.5/">LLVM 1.5 web site</a>. If you are
39 not reading this on the LLVM web pages, you should probably go there because
40 this document may be updated after the release.</p>
42 <p>For more information about LLVM, including information about the latest
43 release, please check out the <a href="http://llvm.cs.uiuc.edu">main LLVM
44 web site</a>. If you have questions or comments, the <a
45 href="http://mail.cs.uiuc.edu/mailman/listinfo/llvmdev">LLVM developer's mailing
46 list</a> is a good place to send them.</p>
48 <p>Note that if you are reading this file from CVS or the main LLVM web page,
49 this document applies to the <i>next</i> release, not the current one. To see
50 the release notes for the current or previous releases, see the <a
51 href="http://llvm.cs.uiuc.edu/releases/">releases page</a>.</p>
55 <!-- *********************************************************************** -->
56 <div class="doc_section">
57 <a name="whatsnew">What's New?</a>
59 <!-- *********************************************************************** -->
61 <div class="doc_text">
63 <p>This is the sixth public release of the LLVM compiler infrastructure.</p>
65 <p> At this time, LLVM is known to correctly compile a broad range of C and
66 C++ programs, including the SPEC CPU95 & 2000 suite. TODO. It also includes
67 bug fixes for those problems found since the 1.4 release.</p>
71 <!--=========================================================================-->
72 <div class="doc_subsubsection">
73 <a name="newfeatures">This release implements the following new features:</a>
76 <div class="doc_text">
78 <li>LLVM now includes an <a href="http://llvm.cs.uiuc.edu/PR415">
79 Interprocedural Sparse Conditional Constant Propagation</a> pass, named
80 -ipsccp, which is run by default at link-time.</li>
81 <li>LLVM 1.5 is now about 15% faster than LLVM 1.4 and its core data structures
82 use about 30% less memory.</li>
83 <li>LLVM includes new experimental native code generators for SparcV8 and
85 <li>Support for Microsoft Visual Studio is improved, and <a
86 href="GettingStartedVS.html">now documented</a>.</li>
92 <!--=========================================================================-->
93 <div class="doc_subsubsection">
94 In this release, the following missing features were implemented:
97 <div class="doc_text">
105 <!--=========================================================================-->
106 <div class="doc_subsubsection">
107 <a name="qualityofimp">In this release, the following Quality of Implementation
108 issues were fixed:</a>
111 <div class="doc_text">
114 <li><a href="http://llvm.cs.uiuc.edu/PR448">Building LLVM in optimized mode
115 should no longer cause GCC to hit swap in the PowerPC backend.</a></li>
119 <!--=========================================================================-->
120 <div class="doc_subsubsection">
121 <a name="codequality">This release includes the following Code Quality
125 <div class="doc_text">
131 <!--=========================================================================-->
132 <div class="doc_subsubsection">
133 <a name="bugfix">In this release, the following bugs in the previous release
137 <div class="doc_text">
140 <p>Bugs fixed in the LLVM Core:</p>
142 <li><a href="http://llvm.cs.uiuc.edu/PR491">[dse] DSE deletes stores that
143 are partially overwritten by smaller stores</a></li>
146 <p>Code Generator Bugs:</p>
148 <li><a href="http://llvm.cs.uiuc.edu/PR490">[cbackend] Logical constant
149 expressions (and/or/xor) not implemented</a></li>
150 <li><a href="http://llvm.cs.uiuc.edu/PR511">[cbackend] C backend does not
151 respect 'volatile'</a></li>
154 <p>Bugs in the C/C++ front-end:</p>
156 <li><a href="http://llvm.cs.uiuc.edu/PR487">[llvmgcc] llvm-gcc incorrectly
157 rejects some constant initializers involving the addresses of array
159 <li><a href="http://llvm.cs.uiuc.edu/PR501">[llvm-g++] Crash compiling
160 anonymous union</a></li>
161 <li><a href="http://llvm.cs.uiuc.edu/PR509">[llvm-g++] Do not use dynamic
162 initialization where static init will do</a></li>
168 <!-- *********************************************************************** -->
169 <div class="doc_section">
170 <a name="portability">Portability and Supported Platforms</a>
172 <!-- *********************************************************************** -->
174 <div class="doc_text">
176 <p>LLVM is known to work on the following platforms:</p>
179 <li>Intel and AMD machines running Red Hat Linux and FreeBSD (and probably
180 other unix-like systems).</li>
181 <li>Sun UltraSPARC workstations running Solaris 8.</li>
182 <li>Intel and AMD machines running on Win32 with the Cygwin libraries (limited
183 support is available for native builds with Visual C++).</li>
184 <li>PowerPC-based Mac OS X systems, running 10.2 and above.</li>
187 <p>The core LLVM infrastructure uses
188 <a href="http://www.gnu.org/software/autoconf/">GNU autoconf</a> to adapt itself
189 to the machine and operating system on which it is built. However, minor
190 porting may be required to get LLVM to work on new platforms. We welcome your
191 portability patches and reports of successful builds or error messages.</p>
195 <!-- *********************************************************************** -->
196 <div class="doc_section">
197 <a name="knownproblems">Known Problems</a>
199 <!-- *********************************************************************** -->
201 <div class="doc_text">
203 <p>This section contains all known problems with the LLVM system, listed by
204 component. As new problems are discovered, they will be added to these
205 sections. If you run into a problem, please check the <a
206 href="http://llvm.cs.uiuc.edu/bugs/">LLVM bug database</a> and submit a bug if
207 there isn't already one.</p>
211 <!-- ======================================================================= -->
212 <div class="doc_subsection">
213 <a name="experimental">Experimental features included with this release</a>
216 <div class="doc_text">
218 <p>The following components of this LLVM release are either untested, known to
219 be broken or unreliable, or are in early development. These components should
220 not be relied on, and bugs should not be filed against them, but they may be
221 useful to some people. In particular, if you would like to work on one of these
222 components, please contact us on the llvmdev list.</p>
225 <li>The following passes are incomplete or buggy, and may be removed in future
226 releases: <tt>-cee, -branch-combine, -instloops, -paths, -pre</tt></li>
227 <li>The <tt>llvm-db</tt> tool is in a very early stage of development, but can
228 be used to step through programs and inspect the stack.</li>
229 <li>The "iterative scan" register allocator (enabled with -regalloc=iterativescan)
231 <li>The SparcV8 and Alpha ports are experimental.</li>
236 <!-- ======================================================================= -->
237 <div class="doc_subsection">
238 <a name="core">Known problems with the LLVM Core</a>
241 <div class="doc_text">
244 <li>In the JIT, <tt>dlsym</tt> on a symbol compiled by the JIT will not work.
246 <li>The JIT does not use mutexes to protect its internal data structures. As
247 such, execution of a threaded program could cause these data structures to be
250 <li><a href="http://llvm.cs.uiuc.edu/PR240">The lower-invoke pass does not
251 mark values live across a setjmp as volatile</a>. This missing feature
252 only affects targets whose setjmp/longjmp libraries do not save and restore
253 the entire register file.</li>
257 <!-- ======================================================================= -->
258 <div class="doc_subsection">
259 <a name="c-fe">Known problems with the C front-end</a>
262 <!-- _______________________________________________________________________ -->
263 <div class="doc_subsubsection">Bugs</div>
265 <div class="doc_text">
267 <li>C99 Variable sized arrays do not release stack memory when they go out of
268 scope. Thus, the following program may run out of stack space:
270 for (i = 0; i != 1000000; ++i) {
276 <li>Initialization of global union variables can only be done <a
277 href="http://llvm.cs.uiuc.edu/PR162">with the largest union member</a>.</li>
282 <!-- _______________________________________________________________________ -->
283 <div class="doc_subsubsection">
287 <div class="doc_text">
291 <li>Inline assembly is not yet supported.</li>
293 <li>"long double" is transformed by the front-end into "double". There is no
294 support for floating point data types of any size other than 32 and 64
297 <li>The following Unix system functionality has not been tested and may not
300 <li><tt>sigsetjmp</tt>, <tt>siglongjmp</tt> - These are not turned into the
301 appropriate <tt>invoke</tt>/<tt>unwind</tt> instructions. Note that
302 <tt>setjmp</tt> and <tt>longjmp</tt> <em>are</em> compiled correctly.
303 <li><tt>getcontext</tt>, <tt>setcontext</tt>, <tt>makecontext</tt>
304 - These functions have not been tested.
307 <li>Although many GCC extensions are supported, some are not. In particular,
308 the following extensions are known to <b>not be</b> supported:
310 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Local-Labels.html#Local%20Labels">Local Labels</a>: Labels local to a block.</li>
311 <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>
312 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Constructing-Calls.html#Constructing%20Calls">Constructing Calls</a>: Dispatching a call to another function.</li>
313 <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>
314 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Constraints.html#Constraints">Constraints</a>: Constraints for asm operands.</li>
315 <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>
316 <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>
317 <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>
318 <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>
319 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Thread_002dLocal.html">Thread-Local</a>: Per-thread variables.</li>
320 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Pragmas.html#Pragmas">Pragmas</a>: Pragmas accepted by GCC.</li>
323 <p>The following GCC extensions are <b>partially</b> supported. An ignored
324 attribute means that the LLVM compiler ignores the presence of the attribute,
325 but the code should still work. An unsupported attribute is one which is
326 ignored by the LLVM compiler and will cause a different interpretation of
330 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Variable-Length.html#Variable%20Length">Variable Length</a>:
331 Arrays whose length is computed at run time.<br>
332 Supported, but allocated stack space is not freed until the function returns (noted above).</li>
334 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Function-Attributes.html#Function%20Attributes">Function Attributes</a>:
336 Declaring that functions have no side effects or that they can never
339 <b>Supported:</b> <tt>format</tt>, <tt>format_arg</tt>, <tt>non_null</tt>,
340 <tt>noreturn</tt>, <tt>constructor</tt>, <tt>destructor</tt>,
342 <tt>deprecated</tt>, <tt>warn_unused_result</tt>, <tt>weak</tt><br>
344 <b>Ignored:</b> <tt>noinline</tt>,
345 <tt>always_inline</tt>, <tt>pure</tt>, <tt>const</tt>, <tt>nothrow</tt>,
346 <tt>malloc</tt>, <tt>no_instrument_function</tt>, <tt>cdecl</tt><br>
348 <b>Unsupported:</b> <tt>used</tt>, <tt>section</tt>, <tt>alias</tt>,
349 <tt>visibility</tt>, <tt>regparm</tt>, <tt>stdcall</tt>,
350 <tt>fastcall</tt>, all other target specific attributes</li>
352 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Variable-Attributes.html#Variable%20Attributes">Variable Attributes</a>:
353 Specifying attributes of variables.<br>
354 <b>Supported:</b> <tt>cleanup</tt>, <tt>common</tt>, <tt>nocommon</tt>,
355 <tt>deprecated</tt>, <tt>transparent_union</tt>,
356 <tt>unused</tt>, <tt>weak</tt><br>
358 <b>Unsupported:</b> <tt>aligned</tt>, <tt>mode</tt>, <tt>packed</tt>,
359 <tt>section</tt>, <tt>shared</tt>, <tt>tls_model</tt>,
360 <tt>vector_size</tt>, <tt>dllimport</tt>,
361 <tt>dllexport</tt>, all target specific attributes.</li>
363 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Type-Attributes.html#Type%20Attributes">Type Attributes</a>: Specifying attributes of types.<br>
364 <b>Supported:</b> <tt>transparent_union</tt>, <tt>unused</tt>,
365 <tt>deprecated</tt>, <tt>may_alias</tt><br>
367 <b>Unsupported:</b> <tt>aligned</tt>, <tt>packed</tt>,
368 all target specific attributes.</li>
370 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Other-Builtins.html#Other%20Builtins">Other Builtins</a>:
371 Other built-in functions.<br>
372 We support all builtins which have a C language equivalent (e.g.,
373 <tt>__builtin_cos</tt>), <tt>__builtin_alloca</tt>,
374 <tt>__builtin_types_compatible_p</tt>, <tt>__builtin_choose_expr</tt>,
375 <tt>__builtin_constant_p</tt>, and <tt>__builtin_expect</tt>
376 (currently ignored). We also support builtins for ISO C99 floating
377 point comparison macros (e.g., <tt>__builtin_islessequal</tt>).</li>
380 <p>The following extensions <b>are</b> known to be supported:</p>
383 <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>
384 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Statement-Exprs.html#Statement%20Exprs">Statement Exprs</a>: Putting statements and declarations inside expressions.</li>
385 <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>
386 <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>
387 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Conditionals.html#Conditionals">Conditionals</a>: Omitting the middle operand of a <code>?:</code> expression.</li>
388 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Long-Long.html#Long%20Long">Long Long</a>: Double-word integers.</li>
389 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Complex.html#Complex">Complex</a>: Data types for complex numbers.</li>
390 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Hex-Floats.html#Hex%20Floats">Hex Floats</a>:Hexadecimal floating-point constants.</li>
391 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Zero-Length.html#Zero%20Length">Zero Length</a>: Zero-length arrays.</li>
392 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Empty-Structures.html#Empty%20Structures">Empty Structures</a>: Structures with no members.</li>
393 <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>
394 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Escaped-Newlines.html#Escaped%20Newlines">Escaped Newlines</a>: Slightly looser rules for escaped newlines.</li>
395 <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>
396 <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>
397 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Initializers.html#Initializers">Initializers</a>: Non-constant initializers.</li>
398 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Compound-Literals.html#Compound%20Literals">Compound Literals</a>: Compound literals give structures, unions,
399 or arrays as values.</li>
400 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Designated-Inits.html#Designated%20Inits">Designated Inits</a>: Labeling elements of initializers.</li>
401 <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>
402 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Case-Ranges.html#Case%20Ranges">Case Ranges</a>: `case 1 ... 9' and such.</li>
403 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Mixed-Declarations.html#Mixed%20Declarations">Mixed Declarations</a>: Mixing declarations and code.</li>
404 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Function-Prototypes.html#Function%20Prototypes">Function Prototypes</a>: Prototype declarations and old-style definitions.</li>
405 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/C_002b_002b-Comments.html#C_002b_002b-Comments">C++ Comments</a>: C++ comments are recognized.</li>
406 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Dollar-Signs.html#Dollar%20Signs">Dollar Signs</a>: Dollar sign is allowed in identifiers.</li>
407 <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>
408 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Alignment.html#Alignment">Alignment</a>: Inquiring about the alignment of a type or variable.</li>
409 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Inline.html#Inline">Inline</a>: Defining inline functions (as fast as macros).</li>
410 <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>
411 <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>
412 <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>
413 <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>
414 <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>
415 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Attribute-Syntax.html#Attribute%20Syntax">Attribute Syntax</a>: Formal syntax for attributes.</li>
420 <p>If you run into GCC extensions which have not been included in any of these
421 lists, please let us know (also including whether or not they work).</p>
425 <!-- ======================================================================= -->
426 <div class="doc_subsection">
427 <a name="c++-fe">Known problems with the C++ front-end</a>
430 <div class="doc_text">
432 <p>For this release, the C++ front-end is considered to be fully
433 tested and works for a number of non-trivial programs, including LLVM
438 <!-- _______________________________________________________________________ -->
439 <div class="doc_subsubsection">Bugs</div>
441 <div class="doc_text">
444 <li>The C++ front-end inherits all problems afflicting the <a href="#c-fe">C
447 <li><b>IA-64 specific</b>: The C++ front-end does not use <a
448 href="http://llvm.cs.uiuc.edu/PR406">IA64 ABI compliant layout of v-tables</a>.
449 In particular, it just stores function pointers instead of function
450 descriptors in the vtable. This bug prevents mixing C++ code compiled with
451 LLVM with C++ objects compiled by other C++ compilers.</li>
457 <!-- _______________________________________________________________________ -->
458 <div class="doc_subsubsection">
462 <div class="doc_text">
466 <li>The C++ front-end is based on a pre-release of the GCC 3.4 C++ parser. This
467 parser is significantly more standards compliant (and picky) than prior GCC
468 versions. For more information, see the C++ section of the <a
469 href="http://gcc.gnu.org/gcc-3.4/changes.html">GCC 3.4 release notes</a>.</li>
471 <li>Destructors for local objects are not always run when a <tt>longjmp</tt> is
472 performed. In particular, destructors for objects in the <tt>longjmp</tt>ing
473 function and in the <tt>setjmp</tt> receiver function may not be run.
474 Objects in intervening stack frames will be destroyed, however (which is
475 better than most compilers).</li>
477 <li>The LLVM C++ front-end follows the <a
478 href="http://www.codesourcery.com/cxx-abi">Itanium C++ ABI</a>.
479 This document, which is not Itanium specific, specifies a standard for name
480 mangling, class layout, v-table layout, RTTI formats, and other C++
481 representation issues. Because we use this API, code generated by the LLVM
482 compilers should be binary compatible with machine code generated by other
483 Itanium ABI C++ compilers (such as G++, the Intel and HP compilers, etc).
484 <i>However</i>, the exception handling mechanism used by LLVM is very
485 different from the model used in the Itanium ABI, so <b>exceptions will not
486 interact correctly</b>. </li>
492 <!-- ======================================================================= -->
493 <div class="doc_subsection">
494 <a name="x86-be">Known problems with the X86 back-end</a>
497 <div class="doc_text">
505 <!-- ======================================================================= -->
506 <div class="doc_subsection">
507 <a name="sparcv9-be">Known problems with the SparcV9 back-end</a>
510 <div class="doc_text">
513 <li><a href="http://llvm.cs.uiuc.edu/PR60">[sparcv9] SparcV9 backend miscompiles
514 several programs in the LLVM test suite</a></li>
519 <!-- ======================================================================= -->
520 <div class="doc_subsection">
521 <a name="ppc-be">Known problems with the PowerPC back-end</a>
524 <div class="doc_text">
532 <!-- ======================================================================= -->
533 <div class="doc_subsection">
534 <a name="c-be">Known problems with the C back-end</a>
537 <div class="doc_text">
541 <li>The C back-end produces code that violates the ANSI C Type-Based Alias
542 Analysis rules. As such, special options may be necessary to compile the code
543 (for example, GCC requires the <tt>-fno-strict-aliasing</tt> option). This
544 problem probably cannot be fixed.</li>
546 <li><a href="http://llvm.cs.uiuc.edu/PR56">Zero arg vararg functions are not
547 supported</a>. This should not affect LLVM produced by the C or C++
554 <!-- *********************************************************************** -->
555 <div class="doc_section">
556 <a name="additionalinfo">Additional Information</a>
558 <!-- *********************************************************************** -->
560 <div class="doc_text">
562 <p>A wide variety of additional information is available on the LLVM web page,
563 including mailing lists and publications describing algorithms and components
564 implemented in LLVM. The web page also contains versions of the API
565 documentation which is up-to-date with the CVS version of the source code. You
566 can access versions of these documents specific to this release by going into
567 the "<tt>llvm/doc/</tt>" directory in the LLVM tree.</p>
569 <p>If you have any questions or comments about LLVM, please feel free to contact
570 us via the <a href="http://mail.cs.uiuc.edu/mailman/listinfo/llvmdev">mailing
575 <!-- *********************************************************************** -->
579 <a href="http://jigsaw.w3.org/css-validator/check/referer"><img
580 src="http://jigsaw.w3.org/css-validator/images/vcss" alt="Valid CSS!"></a>
581 <a href="http://validator.w3.org/check/referer"><img
582 src="http://www.w3.org/Icons/valid-html401" alt="Valid HTML 4.01!" /></a>
584 <a href="http://llvm.cs.uiuc.edu">The LLVM Compiler Infrastructure</a><br>
585 Last modified: $Date$