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.7cvs Release Notes</title>
11 <div class="doc_title">LLVM 1.7 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.org">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.7. Here we describe the status of LLVM, including any
36 known problems and major improvements from the previous release. The most
37 up-to-date version of this document can be found on the <a
38 href="http://llvm.org/releases/">LLVM releases 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.org/">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.org/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 seventh public release of the LLVM Compiler Infrastructure. This
64 release incorporates a large number of enhancements and additions (primarily in
65 the code generator), which combine to improve the quality of the code generated
66 by LLVM by up to 30% in some cases. This release is also the first release to
67 have first-class support for Mac OS X: all of the major bugs have been shaken
68 out and it is now as well supported as Linux on X86.</p>
72 <!--=========================================================================-->
73 <div class="doc_subsection">
74 <a name="newfeatures">New Features in LLVM 1.7cvs</a>
77 <div class="doc_text">
79 <li>New C front-end.</li>
80 <li>New SPARC backend.</li>
81 <li>Inline assembly support.</li>
85 <!--=========================================================================-->
86 <div class="doc_subsection">
87 <a name="changes">Significant changes in LLVM 1.7cvs</a>
90 <div class="doc_text">
92 <li>Removed the llvm.readport/llvm.writeport/llvm.readio/llvm.writeio
94 <li>Separated the other intrinsics based on type.</li>
99 <!-- *********************************************************************** -->
100 <div class="doc_section">
101 <a name="portability">Portability and Supported Platforms</a>
103 <!-- *********************************************************************** -->
105 <div class="doc_text">
107 <p>LLVM is known to work on the following platforms:</p>
110 <li>Intel and AMD machines running Red Hat Linux, Fedora Core and FreeBSD
111 (and probably other unix-like systems).</li>
112 <li>Sun UltraSPARC workstations running Solaris 8.</li>
113 <li>Intel and AMD machines running on Win32 with the Cygwin libraries (limited
114 support is available for native builds with Visual C++).</li>
115 <li>PowerPC and X86-based Mac OS X systems, running 10.2 and above.</li>
116 <li>Alpha-based machines running Debian GNU/Linux.</li>
117 <li>Itanium-based machines running Linux and HP-UX.</li>
120 <p>The core LLVM infrastructure uses
121 <a href="http://www.gnu.org/software/autoconf/">GNU autoconf</a> to adapt itself
122 to the machine and operating system on which it is built. However, minor
123 porting may be required to get LLVM to work on new platforms. We welcome your
124 portability patches and reports of successful builds or error messages.</p>
128 <!-- *********************************************************************** -->
129 <div class="doc_section">
130 <a name="knownproblems">Known Problems</a>
132 <!-- *********************************************************************** -->
134 <div class="doc_text">
136 <p>This section contains all known problems with the LLVM system, listed by
137 component. As new problems are discovered, they will be added to these
138 sections. If you run into a problem, please check the <a
139 href="http://llvm.org/bugs/">LLVM bug database</a> and submit a bug if
140 there isn't already one.</p>
144 <!-- ======================================================================= -->
145 <div class="doc_subsection">
146 <a name="experimental">Experimental features included with this release</a>
149 <div class="doc_text">
151 <p>The following components of this LLVM release are either untested, known to
152 be broken or unreliable, or are in early development. These components should
153 not be relied on, and bugs should not be filed against them, but they may be
154 useful to some people. In particular, if you would like to work on one of these
155 components, please contact us on the llvmdev list.</p>
158 <li>The following passes are incomplete or buggy, and may be removed in future
159 releases: <tt>-cee</tt></li>
160 <li>The <tt>llvm-db</tt> tool is in a very early stage of development, but can
161 be used to step through programs and inspect the stack.</li>
162 <li>The IA64 code generator is experimental.</li>
163 <li>The Alpha JIT is experimental.</li>
168 <!-- ======================================================================= -->
169 <div class="doc_subsection">
170 <a name="build">Known problems with the Build System</a>
173 <div class="doc_text">
176 <li>The <a href="http://llvm.org/PR656">configure script sometimes fails on Solaris/Sparc</a>. A work around is documented in <a href="http://llvm.org/PR656">PR656.</a></li>
181 <!-- ======================================================================= -->
182 <div class="doc_subsection">
183 <a name="core">Known problems with the LLVM Core</a>
186 <div class="doc_text">
189 <li>In the JIT, <tt>dlsym()</tt> on a symbol compiled by the JIT will not
194 <!-- ======================================================================= -->
195 <div class="doc_subsection">
196 <a name="c-fe">Known problems with the C front-end</a>
199 <!-- _______________________________________________________________________ -->
200 <div class="doc_subsubsection">Bugs</div>
202 <div class="doc_text">
204 These bugs are known for the old front-end. The new GCC-4-based C front-end
205 suffers from none of these.
208 <li>C99 Variable sized arrays do not release stack memory when they go out of
209 scope. Thus, the following program may run out of stack space:
211 for (i = 0; i != 1000000; ++i) {
217 <li>Initialization of global union variables can only be done <a
218 href="http://llvm.org/PR162">with the largest union member</a>.</li>
223 <!-- _______________________________________________________________________ -->
224 <div class="doc_subsubsection">
228 <div class="doc_text">
232 <li>"long double" is transformed by the front-end into "double". There is no
233 support for floating point data types of any size other than 32 and 64
236 <li>The following Unix system functionality has not been tested and may not
239 <li><tt>sigsetjmp</tt>, <tt>siglongjmp</tt> - These are not turned into the
240 appropriate <tt>invoke</tt>/<tt>unwind</tt> instructions. Note that
241 <tt>setjmp</tt> and <tt>longjmp</tt> <em>are</em> compiled correctly.
242 <li><tt>getcontext</tt>, <tt>setcontext</tt>, <tt>makecontext</tt>
243 - These functions have not been tested.
246 <li>Although many GCC extensions are supported, some are not. In particular,
247 the following extensions are known to <b>not be</b> supported:
249 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Local-Labels.html#Local%20Labels">Local Labels</a>: Labels local to a block.</li>
250 <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>
251 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Constructing-Calls.html#Constructing%20Calls">Constructing Calls</a>: Dispatching a call to another function.</li>
252 <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>
253 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Constraints.html#Constraints">Constraints</a>: Constraints for asm operands.</li>
254 <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>
255 <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>
256 <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>
257 <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>
258 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Thread_002dLocal.html">Thread-Local</a>: Per-thread variables.</li>
259 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Pragmas.html#Pragmas">Pragmas</a>: Pragmas accepted by GCC.</li>
262 <p>The following GCC extensions are <b>partially</b> supported. An ignored
263 attribute means that the LLVM compiler ignores the presence of the attribute,
264 but the code should still work. An unsupported attribute is one which is
265 ignored by the LLVM compiler and will cause a different interpretation of
269 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Variable-Length.html#Variable%20Length">Variable Length</a>:
270 Arrays whose length is computed at run time.<br>
271 Supported, but allocated stack space is not freed until the function returns (noted above).</li>
273 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Function-Attributes.html#Function%20Attributes">Function Attributes</a>:
275 Declaring that functions have no side effects or that they can never
278 <b>Supported:</b> <tt>format</tt>, <tt>format_arg</tt>, <tt>non_null</tt>,
279 <tt>noreturn</tt>, <tt>constructor</tt>, <tt>destructor</tt>,
280 <tt>unused</tt>, <tt>used</tt>,
281 <tt>deprecated</tt>, <tt>warn_unused_result</tt>, <tt>weak</tt><br>
283 <b>Ignored:</b> <tt>noinline</tt>,
284 <tt>always_inline</tt>, <tt>pure</tt>, <tt>const</tt>, <tt>nothrow</tt>,
285 <tt>malloc</tt>, <tt>no_instrument_function</tt>, <tt>cdecl</tt><br>
287 <b>Unsupported:</b> <tt>section</tt>, <tt>alias</tt>,
288 <tt>visibility</tt>, <tt>regparm</tt>, <tt>stdcall</tt>,
289 <tt>fastcall</tt>, all other target specific attributes</li>
291 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Variable-Attributes.html#Variable%20Attributes">Variable Attributes</a>:
292 Specifying attributes of variables.<br>
293 <b>Supported:</b> <tt>cleanup</tt>, <tt>common</tt>, <tt>nocommon</tt>,
294 <tt>deprecated</tt>, <tt>transparent_union</tt>,
295 <tt>unused</tt>, <tt>used</tt>, <tt>weak</tt><br>
297 <b>Unsupported:</b> <tt>aligned</tt>, <tt>mode</tt>, <tt>packed</tt>,
298 <tt>section</tt>, <tt>shared</tt>, <tt>tls_model</tt>,
299 <tt>vector_size</tt>, <tt>dllimport</tt>,
300 <tt>dllexport</tt>, all target specific attributes.</li>
302 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Type-Attributes.html#Type%20Attributes">Type Attributes</a>: Specifying attributes of types.<br>
303 <b>Supported:</b> <tt>transparent_union</tt>, <tt>unused</tt>,
304 <tt>deprecated</tt>, <tt>may_alias</tt><br>
306 <b>Unsupported:</b> <tt>aligned</tt>, <tt>packed</tt>,
307 all target specific attributes.</li>
309 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Other-Builtins.html#Other%20Builtins">Other Builtins</a>:
310 Other built-in functions.<br>
311 We support all builtins which have a C language equivalent (e.g.,
312 <tt>__builtin_cos</tt>), <tt>__builtin_alloca</tt>,
313 <tt>__builtin_types_compatible_p</tt>, <tt>__builtin_choose_expr</tt>,
314 <tt>__builtin_constant_p</tt>, and <tt>__builtin_expect</tt>
315 (currently ignored). We also support builtins for ISO C99 floating
316 point comparison macros (e.g., <tt>__builtin_islessequal</tt>),
317 <tt>__builtin_prefetch</tt>, <tt>__builtin_popcount[ll]</tt>,
318 <tt>__builtin_clz[ll]</tt>, and <tt>__builtin_ctz[ll]</tt>.</li>
321 <p>The following extensions <b>are</b> known to be supported:</p>
324 <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>
325 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Statement-Exprs.html#Statement%20Exprs">Statement Exprs</a>: Putting statements and declarations inside expressions.</li>
326 <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>
327 <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>
328 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Conditionals.html#Conditionals">Conditionals</a>: Omitting the middle operand of a <code>?:</code> expression.</li>
329 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Long-Long.html#Long%20Long">Long Long</a>: Double-word integers.</li>
330 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Complex.html#Complex">Complex</a>: Data types for complex numbers.</li>
331 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Hex-Floats.html#Hex%20Floats">Hex Floats</a>:Hexadecimal floating-point constants.</li>
332 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Zero-Length.html#Zero%20Length">Zero Length</a>: Zero-length arrays.</li>
333 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Empty-Structures.html#Empty%20Structures">Empty Structures</a>: Structures with no members.</li>
334 <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>
335 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Escaped-Newlines.html#Escaped%20Newlines">Escaped Newlines</a>: Slightly looser rules for escaped newlines.</li>
336 <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>
337 <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>
338 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Initializers.html#Initializers">Initializers</a>: Non-constant initializers.</li>
339 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Compound-Literals.html#Compound%20Literals">Compound Literals</a>: Compound literals give structures, unions,
340 or arrays as values.</li>
341 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Designated-Inits.html#Designated%20Inits">Designated Inits</a>: Labeling elements of initializers.</li>
342 <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>
343 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Case-Ranges.html#Case%20Ranges">Case Ranges</a>: `case 1 ... 9' and such.</li>
344 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Mixed-Declarations.html#Mixed%20Declarations">Mixed Declarations</a>: Mixing declarations and code.</li>
345 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Function-Prototypes.html#Function%20Prototypes">Function Prototypes</a>: Prototype declarations and old-style definitions.</li>
346 <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>
347 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Dollar-Signs.html#Dollar%20Signs">Dollar Signs</a>: Dollar sign is allowed in identifiers.</li>
348 <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>
349 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Alignment.html#Alignment">Alignment</a>: Inquiring about the alignment of a type or variable.</li>
350 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Inline.html#Inline">Inline</a>: Defining inline functions (as fast as macros).</li>
351 <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>
352 <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>
353 <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>
354 <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>
355 <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>
356 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Attribute-Syntax.html#Attribute%20Syntax">Attribute Syntax</a>: Formal syntax for attributes.</li>
361 <p>If you run into GCC extensions which have not been included in any of these
362 lists, please let us know (also including whether or not they work).</p>
366 <!-- ======================================================================= -->
367 <div class="doc_subsection">
368 <a name="c++-fe">Known problems with the C++ front-end</a>
371 <div class="doc_text">
373 <p>For this release, the C++ front-end is considered to be fully
374 tested and works for a number of non-trivial programs, including LLVM
379 <!-- _______________________________________________________________________ -->
380 <div class="doc_subsubsection">Bugs</div>
382 <div class="doc_text">
385 <li>The C++ front-end inherits all problems afflicting the <a href="#c-fe">C
392 <!-- _______________________________________________________________________ -->
393 <div class="doc_subsubsection">
397 <div class="doc_text">
401 <li>The C++ front-end is based on a pre-release of the GCC 3.4 C++ parser. This
402 parser is significantly more standards compliant (and picky) than prior GCC
403 versions. For more information, see the C++ section of the <a
404 href="http://gcc.gnu.org/gcc-3.4/changes.html">GCC 3.4 release notes</a>.</li>
406 <li>Destructors for local objects are not always run when a <tt>longjmp</tt> is
407 performed. In particular, destructors for objects in the <tt>longjmp</tt>ing
408 function and in the <tt>setjmp</tt> receiver function may not be run.
409 Objects in intervening stack frames will be destroyed, however (which is
410 better than most compilers).</li>
412 <li>The LLVM C++ front-end follows the <a
413 href="http://www.codesourcery.com/cxx-abi">Itanium C++ ABI</a>.
414 This document, which is not Itanium specific, specifies a standard for name
415 mangling, class layout, v-table layout, RTTI formats, and other C++
416 representation issues. Because we use this API, code generated by the LLVM
417 compilers should be binary compatible with machine code generated by other
418 Itanium ABI C++ compilers (such as G++, the Intel and HP compilers, etc).
419 <i>However</i>, the exception handling mechanism used by LLVM is very
420 different from the model used in the Itanium ABI, so <b>exceptions will not
421 interact correctly</b>. </li>
427 <!-- ======================================================================= -->
428 <div class="doc_subsection">
429 <a name="c-be">Known problems with the C back-end</a>
432 <div class="doc_text">
436 <li>The C back-end produces code that violates the ANSI C Type-Based Alias
437 Analysis rules. As such, special options may be necessary to compile the code
438 (for example, GCC requires the <tt>-fno-strict-aliasing</tt> option). This
439 problem probably cannot be fixed.</li>
441 <li><a href="http://llvm.org/PR56">Zero arg vararg functions are not
442 supported</a>. This should not affect LLVM produced by the C or C++
449 <!-- ======================================================================= -->
450 <div class="doc_subsection">
451 <a name="x86-be">Known problems with the X86 back-end</a>
454 <div class="doc_text">
462 <!-- ======================================================================= -->
463 <div class="doc_subsection">
464 <a name="ppc-be">Known problems with the PowerPC back-end</a>
467 <div class="doc_text">
475 <!-- ======================================================================= -->
476 <div class="doc_subsection">
477 <a name="sparcv9-be">Known problems with the SparcV9 back-end</a>
480 <div class="doc_text">
483 <li><a href="http://llvm.org/PR60">[sparcv9] SparcV9 backend miscompiles
484 several programs in the LLVM test suite</a></li>
489 <!-- ======================================================================= -->
490 <div class="doc_subsection">
491 <a name="alpha-be">Known problems with the Alpha back-end</a>
494 <div class="doc_text">
498 <li>On 21164s, some rare FP arithmetic sequences which may trap do not have the
499 appropriate nops inserted to ensure restartability.</li>
505 <!-- ======================================================================= -->
506 <div class="doc_subsection">
507 <a name="ia64-be">Known problems with the IA64 back-end</a>
510 <div class="doc_text">
514 <li>C++ programs are likely to fail on IA64, as calls to <tt>setjmp</tt> are
515 made where the argument is not 16-byte aligned, as required on IA64. (Strictly
516 speaking this is not a bug in the IA64 back-end; it will also be encountered
517 when building C++ programs using the C back-end.)</li>
519 <li>The C++ front-end does not use <a href="http://llvm.org/PR406">IA64
520 ABI compliant layout of v-tables</a>. In particular, it just stores function
521 pointers instead of function descriptors in the vtable. This bug prevents
522 mixing C++ code compiled with LLVM with C++ objects compiled by other C++
525 <li>There are a few ABI violations which will lead to problems when mixing LLVM
526 output with code built with other compilers, particularly for floating-point
529 <li>Defining vararg functions is not supported (but calling them is ok).</li>
535 <!-- ======================================================================= -->
536 <div class="doc_subsection">
537 <a name="sparc">Known problems with the SPARC back-end</a>
540 <div class="doc_text">
547 <!-- *********************************************************************** -->
548 <div class="doc_section">
549 <a name="additionalinfo">Additional Information</a>
551 <!-- *********************************************************************** -->
553 <div class="doc_text">
555 <p>A wide variety of additional information is available on the <a
556 href="http://llvm.org">LLVM web page</a>, including <a
557 href="http://llvm.org/docs/">documentation</a> and <a
558 href="http://llvm.org/pubs/">publications describing algorithms and
559 components implemented in LLVM</a>. The web page also contains versions of the
560 API documentation which is up-to-date with the CVS version of the source code.
561 You can access versions of these documents specific to this release by going
562 into the "<tt>llvm/doc/</tt>" directory in the LLVM tree.</p>
564 <p>If you have any questions or comments about LLVM, please feel free to contact
565 us via the <a href="http://llvm.org/docs/#maillist"> mailing
570 <!-- *********************************************************************** -->
574 <a href="http://jigsaw.w3.org/css-validator/check/referer"><img
575 src="http://jigsaw.w3.org/css-validator/images/vcss" alt="Valid CSS!"></a>
576 <a href="http://validator.w3.org/check/referer"><img
577 src="http://www.w3.org/Icons/valid-html401" alt="Valid HTML 4.01!" /></a>
579 <a href="http://llvm.org/">The LLVM Compiler Infrastructure</a><br>
580 Last modified: $Date$