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="#portability">Portability and Supported Platforms</a></li>
16 <li><a href="#install-instructions">Installation Instructions</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_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.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">
73 This is the fourth public release of the LLVM compiler infrastructure.
77 At this time, LLVM is known to correctly compile and run all C & C++ SPEC
78 CPU2000 benchmarks, the Olden benchmarks, and the Ptrdist benchmarks. It has
79 also been used to compile <b>many</b> other programs. LLVM now also works with
80 a broad variety of C++ programs, though it has still received less testing than
84 <!--=========================================================================-->
85 <div class="doc_subsubsection">
86 <a name="newfeatures">This release implements the following new features:</a>
90 <li>The LLVM <a href="LangRef.html#i_select"><tt>select</tt></a> instruction is
91 now fully implemented and supported by all targets.</li>
95 <!--=========================================================================-->
96 <div class="doc_subsubsection">
97 In this release, the following missing features were implemented:
101 <li><a href="http://llvm.cs.uiuc.edu/PR82">LLVM cannot handle structures with more than 256 elements</a></li>
105 <!--=========================================================================-->
106 <div class="doc_subsubsection">
107 <a name="qualityofimp">In this release, the following Quality of Implementation issues were fixed:</a>
111 <li><a href="http://llvm.cs.uiuc.edu/PR305">LLVM tools will happily spew bytecode onto your terminal</a></li>
114 <!--=========================================================================-->
115 <div class="doc_subsubsection">
116 In this release, the following build problems were fixed:
123 <!--=========================================================================-->
124 <div class="doc_subsubsection">
125 <a name="codequality">In this release, the following Code Quality issues were fixed:</a>
129 <li><a href="http://llvm.cs.uiuc.edu/PR309">[vmcore] Code quality problem due to long operand of getelementptr</a></li>
133 <!--=========================================================================-->
134 <div class="doc_subsubsection">
135 <a name="bugfix">In this release, the following bugs in the previous release were fixed:</a>
138 <p>Bugs in the LLVM Core:</p>
141 <li><a href="http://llvm.cs.uiuc.edu/PR306">[loopsimplify] Loop simplify incorrectly updates dominator information</a></li>
142 <li><a href="http://llvm.cs.uiuc.edu/PR310">[tailduplicate] DemoteRegToStack breaks SSA form</a></li>
147 <p>Bugs in the C/C++ front-end:</p>
155 <!-- *********************************************************************** -->
156 <div class="doc_section">
157 <a name="portability">Portability and Supported Platforms</a>
159 <!-- *********************************************************************** -->
161 <div class="doc_text">
163 <p>LLVM has been extensively tested on Intel and AMD machines running Red
164 Hat Linux and FreeBSD. It has also been tested on Sun UltraSPARC workstations running Solaris 8.
166 LLVM works on Mac OS X 10.3 and above, but only with the C backend or
167 interpreter (no native backend for the PowerPC is available yet).
168 The core LLVM infrastructure uses "autoconf" for portability, so hopefully we
169 work on more platforms than that. However, it is likely that we
170 missed something and that minor porting is required to get LLVM to work on
171 new platforms. We welcome portability patches and error messages.</p>
175 <!-- *********************************************************************** -->
176 <div class="doc_section">
177 <a name="knownproblems">Known Problems</a>
179 <!-- *********************************************************************** -->
181 <div class="doc_text">
183 <p>This section contains all known problems with the LLVM system, listed by
184 component. As new problems are discovered, they will be added to these
185 sections. If you run into a problem, please check the <a
186 href="http://llvm.cs.uiuc.edu/bugs/">LLVM bug database</a> and submit a bug if
187 there isn't already one.</p>
191 <!-- ======================================================================= -->
192 <div class="doc_subsection">
193 <a name="experimental">Experimental features included with this release</a>
196 <div class="doc_text">
199 The following components of this LLVM release are either untested, known to be
200 broken or unreliable, or are in early development. These components should not
201 be relied on, and bugs should not be filed against them, but they may be useful
202 to some people. In particular, if you would like to work on one of these
203 components, please contact us on the llvmdev list.
207 <li>The following passes are incomplete or buggy: <tt>-pgmdep, -memdep,
208 -ipmodref, -sortstructs, -swapstructs, -cee</tt></li>
210 <li>The <tt>-pre</tt> pass is incomplete (there are cases it doesn't handle that
211 it should) and not thoroughly tested.</li>
212 <li>The <tt>llvm-ar</tt> tool is incomplete and probably buggy.</li>
213 <li>The <tt>llvm-db</tt> tool is in a very early stage of development.</li>
218 <!-- ======================================================================= -->
219 <div class="doc_subsection">
220 <a name="core">Known problems with the LLVM Core</a>
223 <div class="doc_text">
227 <li>In the JIT, <tt>dlsym</tt> on a symbol compiled by the JIT will not
230 <li>The JIT does not use mutexes to protect its internal data structures. As
231 such, execution of a threaded program could cause these data structures to be
234 <li>It is not possible to <tt>dlopen</tt> an LLVM bytecode file in the JIT.</li>
236 <li>Linking in static archive files (.a files) is very slow (there is no symbol
237 table in the archive).</li>
239 <li>The gccld program <a href="http://llvm.cs.uiuc.edu/PR139">does not link objects/archives in the order specified on the command line.</a></li>
241 <li><a href="http://llvm.cs.uiuc.edu/PR240">The lower-invoke pass does not mark
242 values live across a setjmp as volatile</a>. This missing feature only affects
243 targets whose setjmp/longjmp libraries do not save and restore the entire
248 <!-- ======================================================================= -->
249 <div class="doc_subsection">
250 <a name="c-fe">Known problems with the C front-end</a>
253 <!-- _______________________________________________________________________ -->
254 <div class="doc_subsubsection">Bugs</div>
256 <div class="doc_text">
258 <li>C99 Variable sized arrays do not release stack memory when they go out of
259 scope. Thus, the following program may run out of stack space:
261 for (i = 0; i != 1000000; ++i) {
268 Initialization of global union variables can only be done
269 <a href="http://llvm.cs.uiuc.edu/bugs/show_bug.cgi?id=162">with the largest
273 <li><a href="http://llvm.cs.uiuc.edu/PR244">[llvm-gcc] Error when an implicitly external function is re-declared as static</a></li>
278 <!-- _______________________________________________________________________ -->
279 <div class="doc_subsubsection">
283 <div class="doc_text">
287 <li>Inline assembly is not yet supported.</li>
289 <li>"long double" is transformed by the front-end into "double". There is no
290 support for floating point data types of any size other than 32 and 64
293 <li>The following Unix system functionality has not been tested and may not
296 <li><tt>sigsetjmp</tt>, <tt>siglongjmp</tt> - These are not turned into the
297 appropriate <tt>invoke</tt>/<tt>unwind</tt> instructions. Note that
298 <tt>setjmp</tt> and <tt>longjmp</tt> <em>are</em> compiled correctly.
299 <li><tt>getcontext</tt>, <tt>setcontext</tt>, <tt>makecontext</tt>
300 - These functions have not been tested.
303 <li>Although many GCC extensions are supported, some are not. In particular,
304 the following extensions are known to <b>not be</b> supported:
306 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Local-Labels.html#Local%20Labels">Local Labels</a>: Labels local to a block.</li>
307 <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>
308 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Constructing-Calls.html#Constructing%20Calls">Constructing Calls</a>: Dispatching a call to another function.</li>
309 <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>
310 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Constraints.html#Constraints">Constraints</a>: Constraints for asm operands.</li>
311 <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>
312 <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>
313 <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>
314 <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>
315 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Thread-Local.html#Thread-Local">Thread-Local</a>: Per-thread variables.</li>
316 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Pragmas.html#Pragmas">Pragmas</a>: Pragmas accepted by GCC.</li>
319 <p>The following GCC extensions are <b>partially</b> supported. An ignored
320 attribute means that the LLVM compiler ignores the presence of the attribute,
321 but the code should still work. An unsupported attribute is one which is
322 ignored by the LLVM compiler and will cause a different interpretation of
326 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Variable-Length.html#Variable%20Length">Variable Length</a>:
327 Arrays whose length is computed at run time.<br>
328 Supported, but allocated stack space is not freed until the function returns (noted above).</li>
330 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Function-Attributes.html#Function%20Attributes">Function Attributes</a>:
332 Declaring that functions have no side effects or that they can never
335 <b>Supported:</b> <tt>format</tt>, <tt>format_arg</tt>, <tt>non_null</tt>,
336 <tt>constructor</tt>, <tt>destructor</tt>, <tt>unused</tt>,
337 <tt>deprecated</tt>, <tt>warn_unused_result</tt>, <tt>weak</tt><br>
339 <b>Ignored:</b> <tt>noreturn</tt>, <tt>noinline</tt>,
340 <tt>always_inline</tt>, <tt>pure</tt>, <tt>const</tt>, <tt>nothrow</tt>,
341 <tt>malloc</tt>, <tt>no_instrument_function</tt>, <tt>cdecl</tt><br>
343 <b>Unsupported:</b> <tt>used</tt>, <tt>section</tt>, <tt>alias</tt>,
344 <tt>visibility</tt>, <tt>regparm</tt>, <tt>stdcall</tt>,
345 <tt>fastcall</tt>, all other target specific attributes</li>
347 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Variable-Attributes.html#Variable%20Attributes">Variable Attributes</a>:
348 Specifying attributes of variables.<br>
349 <b>Supported:</b> <tt>cleanup</tt>, <tt>common</tt>, <tt>nocommon</tt>,
350 <tt>deprecated</tt>, <tt>transparent_union</tt>,
351 <tt>unused</tt>, <tt>weak</tt><br>
353 <b>Unsupported:</b> <tt>aligned</tt>, <tt>mode</tt>, <tt>packed</tt>,
354 <tt>section</tt>, <tt>shared</tt>, <tt>tls_model</tt>,
355 <tt>vector_size</tt>, <tt>dllimport</tt>,
356 <tt>dllexport</tt>, all target specific attributes.</li>
358 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Type-Attributes.html#Type%20Attributes">Type Attributes</a>: Specifying attributes of types.<br>
359 <b>Supported:</b> <tt>transparent_union</tt>, <tt>unused</tt>,
360 <tt>deprecated</tt>, <tt>may_alias</tt><br>
362 <b>Unsupported:</b> <tt>aligned</tt>, <tt>packed</tt>,
363 all target specific attributes.</li>
365 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Other-Builtins.html#Other%20Builtins">Other Builtins</a>:
366 Other built-in functions.<br>
367 We support all builtins which have a C language equivalent (e.g.,
368 <tt>__builtin_cos</tt>), <tt>__builtin_alloca</tt>,
369 <tt>__builtin_types_compatible_p</tt>, <tt>__builtin_choose_expr</tt>,
370 <tt>__builtin_constant_p</tt>, and <tt>__builtin_expect</tt> (ignored).</li>
374 <p>The following extensions <b>are</b> known to be supported:</p>
377 <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>
378 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Statement-Exprs.html#Statement%20Exprs">Statement Exprs</a>: Putting statements and declarations inside expressions.</li>
379 <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>
380 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Lvalues.html#Lvalues">Lvalues</a>: Using <code>?:</code>, "<code>,</code>" and casts in lvalues.</li>
381 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Conditionals.html#Conditionals">Conditionals</a>: Omitting the middle operand of a <code>?:</code> expression.</li>
382 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Long-Long.html#Long%20Long">Long Long</a>: Double-word integers.</li>
383 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Complex.html#Complex">Complex</a>: Data types for complex numbers.</li>
384 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Hex-Floats.html#Hex%20Floats">Hex Floats</a>:Hexadecimal floating-point constants.</li>
385 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Zero-Length.html#Zero%20Length">Zero Length</a>: Zero-length arrays.</li>
386 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Empty-Structures.html#Empty%20Structures">Empty Structures</a>: Structures with no members.</li>
387 <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>
388 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Escaped-Newlines.html#Escaped%20Newlines">Escaped Newlines</a>: Slightly looser rules for escaped newlines.</li>
389 <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>
390 <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>
391 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Initializers.html#Initializers">Initializers</a>: Non-constant initializers.</li>
392 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Compound-Literals.html#Compound%20Literals">Compound Literals</a>: Compound literals give structures, unions,
393 or arrays as values.</li>
394 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Designated-Inits.html#Designated%20Inits">Designated Inits</a>: Labeling elements of initializers.</li>
395 <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>
396 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Case-Ranges.html#Case%20Ranges">Case Ranges</a>: `case 1 ... 9' and such.</li>
397 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Mixed-Declarations.html#Mixed%20Declarations">Mixed Declarations</a>: Mixing declarations and code.</li>
398 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Function-Prototypes.html#Function%20Prototypes">Function Prototypes</a>: Prototype declarations and old-style definitions.</li>
399 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/C---Comments.html#C++%20Comments">C++ Comments</a>: C++ comments are recognized.</li>
400 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Dollar-Signs.html#Dollar%20Signs">Dollar Signs</a>: Dollar sign is allowed in identifiers.</li>
401 <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>
402 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Alignment.html#Alignment">Alignment</a>: Inquiring about the alignment of a type or variable.</li>
403 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Inline.html#Inline">Inline</a>: Defining inline functions (as fast as macros).</li>
404 <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>
405 <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>
406 <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>
407 <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>
408 <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>
409 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Attribute-Syntax.html#Attribute%20Syntax">Attribute Syntax</a>: Formal syntax for attributes.</li>
414 <p>If you run into GCC extensions which have not been included in any of these
415 lists, please let us know (also including whether or not they work).</p>
419 <!-- ======================================================================= -->
420 <div class="doc_subsection">
421 <a name="c++-fe">Known problems with the C++ front-end</a>
424 <div class="doc_text">
426 <p>For this release, the C++ front-end is considered to be fully functional but
427 has not been tested as thoroughly as the C front-end. It has been tested and
428 works for a number of non-trivial programs, but there may be lurking bugs.
429 Please report any bugs or problems.</p>
433 <!-- _______________________________________________________________________ -->
434 <div class="doc_subsubsection">Bugs</div>
436 <div class="doc_text">
439 <li>The C++ front-end inherits all problems afflicting the <a href="#c-fe">C
444 <!-- _______________________________________________________________________ -->
445 <div class="doc_subsubsection">
449 <div class="doc_text">
453 <li>The C++ front-end is based on a pre-release of the GCC 3.4 C++ parser. This
454 parser is significantly more standards compliant (and picky) than prior GCC
455 versions. For more information, see the C++ section of the <a
456 href="http://gcc.gnu.org/gcc-3.4/changes.html">GCC 3.4 release notes</a>.</li>
458 <li>Destructors for local objects are not always run when a <tt>longjmp</tt> is
459 performed. In particular, destructors for objects in the <tt>longjmp</tt>ing
460 function and in the <tt>setjmp</tt> receiver function may not be run.
461 Objects in intervening stack frames will be destroyed, however (which is
462 better than most compilers).</li>
464 <li>The LLVM C++ front-end follows the <a
465 href="http://www.codesourcery.com/cxx-abi">Itanium C++ ABI</a>.
466 This document, which is not Itanium specific, specifies a standard for name
467 mangling, class layout, v-table layout, RTTI formats, and other C++
468 representation issues. Because we use this API, code generated by the LLVM
469 compilers should be binary compatible with machine code generated by other
470 Itanium ABI C++ compilers (such as G++, the Intel and HP compilers, etc).
471 <i>However</i>, the exception handling mechanism used by LLVM is very
472 different from the model used in the Itanium ABI, so <b>exceptions will not
473 interact correctly</b>. </li>
479 <!-- ======================================================================= -->
480 <div class="doc_subsection">
481 <a name="x86-be">Known problems with the X86 back-end</a>
484 <div class="doc_text">
492 <!-- ======================================================================= -->
493 <div class="doc_subsection">
494 <a name="sparc-be">Known problems with the Sparc back-end</a>
497 <div class="doc_text">
500 <li>There are several programs in the LLVM testsuite that the Sparc code generator is known to miscompile.</li>
505 <!-- ======================================================================= -->
506 <div class="doc_subsection">
507 <a name="c-be">Known problems with the C back-end</a>
510 <div class="doc_text">
514 <li>The C back-end produces code that violates the ANSI C Type-Based Alias
515 Analysis rules. As such, special options may be necessary to compile the code
516 (for example, GCC requires the <tt>-fno-strict-aliasing</tt> option). This
517 problem probably cannot be fixed.</li>
519 <li><a href="http://llvm.cs.uiuc.edu/PR33">Initializers for global variables</a>
520 cannot include special floating point numbers like Not-A-Number or
523 <li><a href="http://llvm.cs.uiuc.edu/PR56">Zero arg vararg functions are not
524 supported</a>. This should not affect LLVM produced by the C or C++
531 <!-- *********************************************************************** -->
532 <div class="doc_section">
533 <a name="additionalinfo">Additional Information</a>
535 <!-- *********************************************************************** -->
537 <div class="doc_text">
539 <p>A wide variety of additional information is available on the LLVM web page,
540 including mailing lists and publications describing algorithms and components
541 implemented in LLVM. The web page also contains versions of the API
542 documentation which is up-to-date with the CVS version of the source code. You
543 can access versions of these documents specific to this release by going into
544 the "<tt>llvm/doc/</tt>" directory in the LLVM tree.</p>
546 <p>If you have any questions or comments about LLVM, please feel free to contact
547 us via the <a href="http://mail.cs.uiuc.edu/mailman/listinfo/llvmdev">mailing
552 <!-- *********************************************************************** -->
556 <a href="http://jigsaw.w3.org/css-validator/check/referer"><img
557 src="http://jigsaw.w3.org/css-validator/images/vcss" alt="Valid CSS!"></a>
558 <a href="http://validator.w3.org/check/referer"><img
559 src="http://www.w3.org/Icons/valid-html401" alt="Valid HTML 4.01!" /></a>
561 <a href="http://llvm.cs.uiuc.edu">The LLVM Compiler Infrastructure</a><br>
562 Last modified: $Date$