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>
86 <!--=========================================================================-->
87 <div class="doc_subsubsection">
88 In this release, the following missing features were implemented:
91 <div class="doc_text">
99 <!--=========================================================================-->
100 <div class="doc_subsubsection">
101 <a name="qualityofimp">In this release, the following Quality of Implementation
102 issues were fixed:</a>
105 <div class="doc_text">
108 <li><a href="http://llvm.cs.uiuc.edu/PR448">Building LLVM in optimized mode
109 should no longer cause GCC to hit swap in the PowerPC backend.</a></li>
113 <!--=========================================================================-->
114 <div class="doc_subsubsection">
115 <a name="codequality">This release includes the following Code Quality
119 <div class="doc_text">
125 <!--=========================================================================-->
126 <div class="doc_subsubsection">
127 <a name="bugfix">In this release, the following bugs in the previous release
131 <div class="doc_text">
133 <p>Bugs fixed in the LLVM Core:</p>
136 <li><a href="http://llvm.cs.uiuc.edu/PR490">[cbackend] Logical constant
137 expressions (and/or/xor) not implemented</a></li>
138 <li><a href="http://llvm.cs.uiuc.edu/PR491">[dse] DSE deletes stores that
139 are partially overwritten by smaller stores</a></li>
142 <p>Bugs in the C/C++ front-end:</p>
145 <li><a href="http://llvm.cs.uiuc.edu/PR487">[llvmgcc] llvm-gcc incorrectly
146 rejects some constant initializers involving the addresses of array
152 <!-- *********************************************************************** -->
153 <div class="doc_section">
154 <a name="portability">Portability and Supported Platforms</a>
156 <!-- *********************************************************************** -->
158 <div class="doc_text">
160 <p>LLVM is known to work on the following platforms:</p>
163 <li>Intel and AMD machines running Red Hat Linux and FreeBSD (and probably
164 other unix-like systems).</li>
165 <li>Sun UltraSPARC workstations running Solaris 8.</li>
166 <li>Intel and AMD machines running on Win32 with the Cygwin libraries (limited
167 support is available for native builds with Visual C++).</li>
168 <li>PowerPC-based Mac OS X systems, running 10.2 and above.</li>
171 <p>The core LLVM infrastructure uses
172 <a href="http://www.gnu.org/software/autoconf/">GNU autoconf</a> to adapt itself
173 to the machine and operating system on which it is built. However, minor
174 porting may be required to get LLVM to work on new platforms. We welcome your
175 portability patches and reports of successful builds or error messages.</p>
179 <!-- *********************************************************************** -->
180 <div class="doc_section">
181 <a name="knownproblems">Known Problems</a>
183 <!-- *********************************************************************** -->
185 <div class="doc_text">
187 <p>This section contains all known problems with the LLVM system, listed by
188 component. As new problems are discovered, they will be added to these
189 sections. If you run into a problem, please check the <a
190 href="http://llvm.cs.uiuc.edu/bugs/">LLVM bug database</a> and submit a bug if
191 there isn't already one.</p>
195 <!-- ======================================================================= -->
196 <div class="doc_subsection">
197 <a name="experimental">Experimental features included with this release</a>
200 <div class="doc_text">
202 <p>The following components of this LLVM release are either untested, known to
203 be broken or unreliable, or are in early development. These components should
204 not be relied on, and bugs should not be filed against them, but they may be
205 useful to some people. In particular, if you would like to work on one of these
206 components, please contact us on the llvmdev list.</p>
209 <li>The following passes are incomplete or buggy, and may be removed in future
210 releases: <tt>-pgmdep, -memdep, -ipmodref, -cee, -branch-combine,
211 -instloops, -paths, -pre</tt></li>
212 <li>The <tt>llvm-db</tt> tool is in a very early stage of development, but can
213 be used to step through programs and inspect the stack.</li>
214 <li>The "iterative scan" register allocator (enabled with -regalloc=iterativescan)
220 <!-- ======================================================================= -->
221 <div class="doc_subsection">
222 <a name="core">Known problems with the LLVM Core</a>
225 <div class="doc_text">
228 <li>In the JIT, <tt>dlsym</tt> on a symbol compiled by the JIT will not work.
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><a href="http://llvm.cs.uiuc.edu/PR240">The lower-invoke pass does not
235 mark values live across a setjmp as volatile</a>. This missing feature
236 only affects targets whose setjmp/longjmp libraries do not save and restore
237 the entire register file.</li>
241 <!-- ======================================================================= -->
242 <div class="doc_subsection">
243 <a name="c-fe">Known problems with the C front-end</a>
246 <!-- _______________________________________________________________________ -->
247 <div class="doc_subsubsection">Bugs</div>
249 <div class="doc_text">
251 <li>C99 Variable sized arrays do not release stack memory when they go out of
252 scope. Thus, the following program may run out of stack space:
254 for (i = 0; i != 1000000; ++i) {
260 <li>Initialization of global union variables can only be done <a
261 href="http://llvm.cs.uiuc.edu/PR162">with the largest union member</a>.</li>
266 <!-- _______________________________________________________________________ -->
267 <div class="doc_subsubsection">
271 <div class="doc_text">
275 <li>Inline assembly is not yet supported.</li>
277 <li>"long double" is transformed by the front-end into "double". There is no
278 support for floating point data types of any size other than 32 and 64
281 <li>The following Unix system functionality has not been tested and may not
284 <li><tt>sigsetjmp</tt>, <tt>siglongjmp</tt> - These are not turned into the
285 appropriate <tt>invoke</tt>/<tt>unwind</tt> instructions. Note that
286 <tt>setjmp</tt> and <tt>longjmp</tt> <em>are</em> compiled correctly.
287 <li><tt>getcontext</tt>, <tt>setcontext</tt>, <tt>makecontext</tt>
288 - These functions have not been tested.
291 <li>Although many GCC extensions are supported, some are not. In particular,
292 the following extensions are known to <b>not be</b> supported:
294 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Local-Labels.html#Local%20Labels">Local Labels</a>: Labels local to a block.</li>
295 <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>
296 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Constructing-Calls.html#Constructing%20Calls">Constructing Calls</a>: Dispatching a call to another function.</li>
297 <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>
298 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Constraints.html#Constraints">Constraints</a>: Constraints for asm operands.</li>
299 <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>
300 <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>
301 <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>
302 <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>
303 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Thread_002dLocal.html">Thread-Local</a>: Per-thread variables.</li>
304 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Pragmas.html#Pragmas">Pragmas</a>: Pragmas accepted by GCC.</li>
307 <p>The following GCC extensions are <b>partially</b> supported. An ignored
308 attribute means that the LLVM compiler ignores the presence of the attribute,
309 but the code should still work. An unsupported attribute is one which is
310 ignored by the LLVM compiler and will cause a different interpretation of
314 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Variable-Length.html#Variable%20Length">Variable Length</a>:
315 Arrays whose length is computed at run time.<br>
316 Supported, but allocated stack space is not freed until the function returns (noted above).</li>
318 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Function-Attributes.html#Function%20Attributes">Function Attributes</a>:
320 Declaring that functions have no side effects or that they can never
323 <b>Supported:</b> <tt>format</tt>, <tt>format_arg</tt>, <tt>non_null</tt>,
324 <tt>noreturn</tt>, <tt>constructor</tt>, <tt>destructor</tt>,
326 <tt>deprecated</tt>, <tt>warn_unused_result</tt>, <tt>weak</tt><br>
328 <b>Ignored:</b> <tt>noinline</tt>,
329 <tt>always_inline</tt>, <tt>pure</tt>, <tt>const</tt>, <tt>nothrow</tt>,
330 <tt>malloc</tt>, <tt>no_instrument_function</tt>, <tt>cdecl</tt><br>
332 <b>Unsupported:</b> <tt>used</tt>, <tt>section</tt>, <tt>alias</tt>,
333 <tt>visibility</tt>, <tt>regparm</tt>, <tt>stdcall</tt>,
334 <tt>fastcall</tt>, all other target specific attributes</li>
336 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Variable-Attributes.html#Variable%20Attributes">Variable Attributes</a>:
337 Specifying attributes of variables.<br>
338 <b>Supported:</b> <tt>cleanup</tt>, <tt>common</tt>, <tt>nocommon</tt>,
339 <tt>deprecated</tt>, <tt>transparent_union</tt>,
340 <tt>unused</tt>, <tt>weak</tt><br>
342 <b>Unsupported:</b> <tt>aligned</tt>, <tt>mode</tt>, <tt>packed</tt>,
343 <tt>section</tt>, <tt>shared</tt>, <tt>tls_model</tt>,
344 <tt>vector_size</tt>, <tt>dllimport</tt>,
345 <tt>dllexport</tt>, all target specific attributes.</li>
347 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Type-Attributes.html#Type%20Attributes">Type Attributes</a>: Specifying attributes of types.<br>
348 <b>Supported:</b> <tt>transparent_union</tt>, <tt>unused</tt>,
349 <tt>deprecated</tt>, <tt>may_alias</tt><br>
351 <b>Unsupported:</b> <tt>aligned</tt>, <tt>packed</tt>,
352 all target specific attributes.</li>
354 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Other-Builtins.html#Other%20Builtins">Other Builtins</a>:
355 Other built-in functions.<br>
356 We support all builtins which have a C language equivalent (e.g.,
357 <tt>__builtin_cos</tt>), <tt>__builtin_alloca</tt>,
358 <tt>__builtin_types_compatible_p</tt>, <tt>__builtin_choose_expr</tt>,
359 <tt>__builtin_constant_p</tt>, and <tt>__builtin_expect</tt>
360 (currently ignored). We also support builtins for ISO C99 floating
361 point comparison macros (e.g., <tt>__builtin_islessequal</tt>).</li>
364 <p>The following extensions <b>are</b> known to be supported:</p>
367 <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>
368 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Statement-Exprs.html#Statement%20Exprs">Statement Exprs</a>: Putting statements and declarations inside expressions.</li>
369 <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>
370 <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>
371 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Conditionals.html#Conditionals">Conditionals</a>: Omitting the middle operand of a <code>?:</code> expression.</li>
372 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Long-Long.html#Long%20Long">Long Long</a>: Double-word integers.</li>
373 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Complex.html#Complex">Complex</a>: Data types for complex numbers.</li>
374 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Hex-Floats.html#Hex%20Floats">Hex Floats</a>:Hexadecimal floating-point constants.</li>
375 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Zero-Length.html#Zero%20Length">Zero Length</a>: Zero-length arrays.</li>
376 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Empty-Structures.html#Empty%20Structures">Empty Structures</a>: Structures with no members.</li>
377 <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>
378 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Escaped-Newlines.html#Escaped%20Newlines">Escaped Newlines</a>: Slightly looser rules for escaped newlines.</li>
379 <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>
380 <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>
381 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Initializers.html#Initializers">Initializers</a>: Non-constant initializers.</li>
382 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Compound-Literals.html#Compound%20Literals">Compound Literals</a>: Compound literals give structures, unions,
383 or arrays as values.</li>
384 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Designated-Inits.html#Designated%20Inits">Designated Inits</a>: Labeling elements of initializers.</li>
385 <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>
386 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Case-Ranges.html#Case%20Ranges">Case Ranges</a>: `case 1 ... 9' and such.</li>
387 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Mixed-Declarations.html#Mixed%20Declarations">Mixed Declarations</a>: Mixing declarations and code.</li>
388 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Function-Prototypes.html#Function%20Prototypes">Function Prototypes</a>: Prototype declarations and old-style definitions.</li>
389 <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>
390 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Dollar-Signs.html#Dollar%20Signs">Dollar Signs</a>: Dollar sign is allowed in identifiers.</li>
391 <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>
392 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Alignment.html#Alignment">Alignment</a>: Inquiring about the alignment of a type or variable.</li>
393 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Inline.html#Inline">Inline</a>: Defining inline functions (as fast as macros).</li>
394 <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>
395 <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>
396 <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>
397 <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>
398 <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>
399 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Attribute-Syntax.html#Attribute%20Syntax">Attribute Syntax</a>: Formal syntax for attributes.</li>
404 <p>If you run into GCC extensions which have not been included in any of these
405 lists, please let us know (also including whether or not they work).</p>
409 <!-- ======================================================================= -->
410 <div class="doc_subsection">
411 <a name="c++-fe">Known problems with the C++ front-end</a>
414 <div class="doc_text">
416 <p>For this release, the C++ front-end is considered to be fully
417 tested and works for a number of non-trivial programs, including LLVM
422 <!-- _______________________________________________________________________ -->
423 <div class="doc_subsubsection">Bugs</div>
425 <div class="doc_text">
428 <li>The C++ front-end inherits all problems afflicting the <a href="#c-fe">C
431 <li><b>IA-64 specific</b>: The C++ front-end does not use <a
432 href="http://llvm.cs.uiuc.edu/PR406">IA64 ABI compliant layout of v-tables</a>.
433 In particular, it just stores function pointers instead of function
434 descriptors in the vtable. This bug prevents mixing C++ code compiled with
435 LLVM with C++ objects compiled by other C++ compilers.</li>
441 <!-- _______________________________________________________________________ -->
442 <div class="doc_subsubsection">
446 <div class="doc_text">
450 <li>The C++ front-end is based on a pre-release of the GCC 3.4 C++ parser. This
451 parser is significantly more standards compliant (and picky) than prior GCC
452 versions. For more information, see the C++ section of the <a
453 href="http://gcc.gnu.org/gcc-3.4/changes.html">GCC 3.4 release notes</a>.</li>
455 <li>Destructors for local objects are not always run when a <tt>longjmp</tt> is
456 performed. In particular, destructors for objects in the <tt>longjmp</tt>ing
457 function and in the <tt>setjmp</tt> receiver function may not be run.
458 Objects in intervening stack frames will be destroyed, however (which is
459 better than most compilers).</li>
461 <li>The LLVM C++ front-end follows the <a
462 href="http://www.codesourcery.com/cxx-abi">Itanium C++ ABI</a>.
463 This document, which is not Itanium specific, specifies a standard for name
464 mangling, class layout, v-table layout, RTTI formats, and other C++
465 representation issues. Because we use this API, code generated by the LLVM
466 compilers should be binary compatible with machine code generated by other
467 Itanium ABI C++ compilers (such as G++, the Intel and HP compilers, etc).
468 <i>However</i>, the exception handling mechanism used by LLVM is very
469 different from the model used in the Itanium ABI, so <b>exceptions will not
470 interact correctly</b>. </li>
476 <!-- ======================================================================= -->
477 <div class="doc_subsection">
478 <a name="x86-be">Known problems with the X86 back-end</a>
481 <div class="doc_text">
489 <!-- ======================================================================= -->
490 <div class="doc_subsection">
491 <a name="sparcv9-be">Known problems with the SparcV9 back-end</a>
494 <div class="doc_text">
497 <li><a href="http://llvm.cs.uiuc.edu/PR60">[sparcv9] SparcV9 backend miscompiles
498 several programs in the LLVM test suite</a></li>
503 <!-- ======================================================================= -->
504 <div class="doc_subsection">
505 <a name="ppc-be">Known problems with the PowerPC back-end</a>
508 <div class="doc_text">
516 <!-- ======================================================================= -->
517 <div class="doc_subsection">
518 <a name="c-be">Known problems with the C back-end</a>
521 <div class="doc_text">
525 <li>The C back-end produces code that violates the ANSI C Type-Based Alias
526 Analysis rules. As such, special options may be necessary to compile the code
527 (for example, GCC requires the <tt>-fno-strict-aliasing</tt> option). This
528 problem probably cannot be fixed.</li>
530 <li><a href="http://llvm.cs.uiuc.edu/PR56">Zero arg vararg functions are not
531 supported</a>. This should not affect LLVM produced by the C or C++
538 <!-- *********************************************************************** -->
539 <div class="doc_section">
540 <a name="additionalinfo">Additional Information</a>
542 <!-- *********************************************************************** -->
544 <div class="doc_text">
546 <p>A wide variety of additional information is available on the LLVM web page,
547 including mailing lists and publications describing algorithms and components
548 implemented in LLVM. The web page also contains versions of the API
549 documentation which is up-to-date with the CVS version of the source code. You
550 can access versions of these documents specific to this release by going into
551 the "<tt>llvm/doc/</tt>" directory in the LLVM tree.</p>
553 <p>If you have any questions or comments about LLVM, please feel free to contact
554 us via the <a href="http://mail.cs.uiuc.edu/mailman/listinfo/llvmdev">mailing
559 <!-- *********************************************************************** -->
563 <a href="http://jigsaw.w3.org/css-validator/check/referer"><img
564 src="http://jigsaw.w3.org/css-validator/images/vcss" alt="Valid CSS!"></a>
565 <a href="http://validator.w3.org/check/referer"><img
566 src="http://www.w3.org/Icons/valid-html401" alt="Valid HTML 4.01!" /></a>
568 <a href="http://llvm.cs.uiuc.edu">The LLVM Compiler Infrastructure</a><br>
569 Last modified: $Date$