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.6 Release Notes</title>
11 <div class="doc_title">LLVM 1.6 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.6. 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.cs.uiuc.edu/releases/1.6/">LLVM 1.6 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 seventh public release of the LLVM Compiler Infrastructure.</p>
65 <p>LLVM 1.6 is known to correctly compile a wide range of C and C++ programs,
66 includes bug fixes for those problems found since the 1.5 release, and includes
67 a large number of new features and enhancements, described below.</p>
71 <!--=========================================================================-->
72 <div class="doc_subsection">
73 <a name="newfeatures">New Features in LLVM 1.6</a>
76 <div class="doc_text">
78 <li>The JIT now uses mutexes to protect its internal data structures. This
79 allows multi-threaded programs to be run from the JIT or interpreter without
80 corruption of the internal data structures. See
81 <a href="http://llvm.cs.uiuc.edu/PR418">PR418</a> and
82 <a href="http://llvm.cs.uiuc.edu/PR540">PR540</a> for the details.
87 <!--=========================================================================-->
88 <div class="doc_subsection">
89 <a name="codequality">Code Quality Improvements in LLVM 1.6</a>
92 <!--=========================================================================-->
93 <div class="doc_subsection">
94 <a name="codequality">Code Generator Improvements in LLVM 1.6</a>
97 <!--=========================================================================-->
98 <div class="doc_subsection">
99 <a name="bugfix">Significant Bugs Fixed in LLVM 1.6</a>
102 <div class="doc_text">
104 <li><a href="http://llvm.cs.uiuc.edu/PR591">[simplify-libcalls] The simplify-libcalls pass generates ill-formed LLVM code</a>.</li>
108 <!-- *********************************************************************** -->
109 <div class="doc_section">
110 <a name="portability">Portability and Supported Platforms</a>
112 <!-- *********************************************************************** -->
114 <div class="doc_text">
116 <p>LLVM is known to work on the following platforms:</p>
119 <li>Intel and AMD machines running Red Hat Linux, Fedora Core and FreeBSD
120 (and probably other unix-like systems).</li>
121 <li>Sun UltraSPARC workstations running Solaris 8.</li>
122 <li>Intel and AMD machines running on Win32 with the Cygwin libraries (limited
123 support is available for native builds with Visual C++).</li>
124 <li>PowerPC and X86-based Mac OS X systems, running 10.2 and above.</li>
125 <li>Alpha-based machines running Debian GNU/Linux.</li>
126 <li>Itanium-based machines running Linux and HP-UX.</li>
129 <p>The core LLVM infrastructure uses
130 <a href="http://www.gnu.org/software/autoconf/">GNU autoconf</a> to adapt itself
131 to the machine and operating system on which it is built. However, minor
132 porting may be required to get LLVM to work on new platforms. We welcome your
133 portability patches and reports of successful builds or error messages.</p>
137 <!-- *********************************************************************** -->
138 <div class="doc_section">
139 <a name="knownproblems">Known Problems</a>
141 <!-- *********************************************************************** -->
143 <div class="doc_text">
145 <p>This section contains all known problems with the LLVM system, listed by
146 component. As new problems are discovered, they will be added to these
147 sections. If you run into a problem, please check the <a
148 href="http://llvm.cs.uiuc.edu/bugs/">LLVM bug database</a> and submit a bug if
149 there isn't already one.</p>
153 <!-- ======================================================================= -->
154 <div class="doc_subsection">
155 <a name="experimental">Experimental features included with this release</a>
158 <div class="doc_text">
160 <p>The following components of this LLVM release are either untested, known to
161 be broken or unreliable, or are in early development. These components should
162 not be relied on, and bugs should not be filed against them, but they may be
163 useful to some people. In particular, if you would like to work on one of these
164 components, please contact us on the llvmdev list.</p>
167 <li>The following passes are incomplete or buggy, and may be removed in future
168 releases: <tt>-cee, -pre</tt></li>
169 <li>The <tt>llvm-db</tt> tool is in a very early stage of development, but can
170 be used to step through programs and inspect the stack.</li>
171 <li>The SparcV8 and IA64 code generators are experimental.</li>
176 <!-- ======================================================================= -->
177 <div class="doc_subsection">
178 <a name="core">Known problems with the LLVM Core</a>
181 <div class="doc_text">
184 <li>In the JIT, <tt>dlsym()</tt> on a symbol compiled by the JIT will not
189 <!-- ======================================================================= -->
190 <div class="doc_subsection">
191 <a name="c-fe">Known problems with the C front-end</a>
194 <!-- _______________________________________________________________________ -->
195 <div class="doc_subsubsection">Bugs</div>
197 <div class="doc_text">
199 <li>C99 Variable sized arrays do not release stack memory when they go out of
200 scope. Thus, the following program may run out of stack space:
202 for (i = 0; i != 1000000; ++i) {
208 <li>Initialization of global union variables can only be done <a
209 href="http://llvm.cs.uiuc.edu/PR162">with the largest union member</a>.</li>
214 <!-- _______________________________________________________________________ -->
215 <div class="doc_subsubsection">
219 <div class="doc_text">
223 <li>Inline assembly is not yet supported.</li>
225 <li>"long double" is transformed by the front-end into "double". There is no
226 support for floating point data types of any size other than 32 and 64
229 <li>The following Unix system functionality has not been tested and may not
232 <li><tt>sigsetjmp</tt>, <tt>siglongjmp</tt> - These are not turned into the
233 appropriate <tt>invoke</tt>/<tt>unwind</tt> instructions. Note that
234 <tt>setjmp</tt> and <tt>longjmp</tt> <em>are</em> compiled correctly.
235 <li><tt>getcontext</tt>, <tt>setcontext</tt>, <tt>makecontext</tt>
236 - These functions have not been tested.
239 <li>Although many GCC extensions are supported, some are not. In particular,
240 the following extensions are known to <b>not be</b> supported:
242 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Local-Labels.html#Local%20Labels">Local Labels</a>: Labels local to a block.</li>
243 <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>
244 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Constructing-Calls.html#Constructing%20Calls">Constructing Calls</a>: Dispatching a call to another function.</li>
245 <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>
246 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Constraints.html#Constraints">Constraints</a>: Constraints for asm operands.</li>
247 <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>
248 <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>
249 <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>
250 <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>
251 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Thread_002dLocal.html">Thread-Local</a>: Per-thread variables.</li>
252 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Pragmas.html#Pragmas">Pragmas</a>: Pragmas accepted by GCC.</li>
255 <p>The following GCC extensions are <b>partially</b> supported. An ignored
256 attribute means that the LLVM compiler ignores the presence of the attribute,
257 but the code should still work. An unsupported attribute is one which is
258 ignored by the LLVM compiler and will cause a different interpretation of
262 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Variable-Length.html#Variable%20Length">Variable Length</a>:
263 Arrays whose length is computed at run time.<br>
264 Supported, but allocated stack space is not freed until the function returns (noted above).</li>
266 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Function-Attributes.html#Function%20Attributes">Function Attributes</a>:
268 Declaring that functions have no side effects or that they can never
271 <b>Supported:</b> <tt>format</tt>, <tt>format_arg</tt>, <tt>non_null</tt>,
272 <tt>noreturn</tt>, <tt>constructor</tt>, <tt>destructor</tt>,
274 <tt>deprecated</tt>, <tt>warn_unused_result</tt>, <tt>weak</tt><br>
276 <b>Ignored:</b> <tt>noinline</tt>,
277 <tt>always_inline</tt>, <tt>pure</tt>, <tt>const</tt>, <tt>nothrow</tt>,
278 <tt>malloc</tt>, <tt>no_instrument_function</tt>, <tt>cdecl</tt><br>
280 <b>Unsupported:</b> <tt>used</tt>, <tt>section</tt>, <tt>alias</tt>,
281 <tt>visibility</tt>, <tt>regparm</tt>, <tt>stdcall</tt>,
282 <tt>fastcall</tt>, all other target specific attributes</li>
284 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Variable-Attributes.html#Variable%20Attributes">Variable Attributes</a>:
285 Specifying attributes of variables.<br>
286 <b>Supported:</b> <tt>cleanup</tt>, <tt>common</tt>, <tt>nocommon</tt>,
287 <tt>deprecated</tt>, <tt>transparent_union</tt>,
288 <tt>unused</tt>, <tt>weak</tt><br>
290 <b>Unsupported:</b> <tt>aligned</tt>, <tt>mode</tt>, <tt>packed</tt>,
291 <tt>section</tt>, <tt>shared</tt>, <tt>tls_model</tt>,
292 <tt>vector_size</tt>, <tt>dllimport</tt>,
293 <tt>dllexport</tt>, all target specific attributes.</li>
295 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Type-Attributes.html#Type%20Attributes">Type Attributes</a>: Specifying attributes of types.<br>
296 <b>Supported:</b> <tt>transparent_union</tt>, <tt>unused</tt>,
297 <tt>deprecated</tt>, <tt>may_alias</tt><br>
299 <b>Unsupported:</b> <tt>aligned</tt>, <tt>packed</tt>,
300 all target specific attributes.</li>
302 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Other-Builtins.html#Other%20Builtins">Other Builtins</a>:
303 Other built-in functions.<br>
304 We support all builtins which have a C language equivalent (e.g.,
305 <tt>__builtin_cos</tt>), <tt>__builtin_alloca</tt>,
306 <tt>__builtin_types_compatible_p</tt>, <tt>__builtin_choose_expr</tt>,
307 <tt>__builtin_constant_p</tt>, and <tt>__builtin_expect</tt>
308 (currently ignored). We also support builtins for ISO C99 floating
309 point comparison macros (e.g., <tt>__builtin_islessequal</tt>),
310 <tt>__builtin_prefetch</tt>, <tt>__builtin_popcount[ll]</tt>,
311 <tt>__builtin_clz[ll]</tt>, and <tt>__builtin_ctz[ll]</tt>.</li>
314 <p>The following extensions <b>are</b> known to be supported:</p>
317 <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>
318 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Statement-Exprs.html#Statement%20Exprs">Statement Exprs</a>: Putting statements and declarations inside expressions.</li>
319 <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>
320 <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>
321 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Conditionals.html#Conditionals">Conditionals</a>: Omitting the middle operand of a <code>?:</code> expression.</li>
322 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Long-Long.html#Long%20Long">Long Long</a>: Double-word integers.</li>
323 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Complex.html#Complex">Complex</a>: Data types for complex numbers.</li>
324 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Hex-Floats.html#Hex%20Floats">Hex Floats</a>:Hexadecimal floating-point constants.</li>
325 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Zero-Length.html#Zero%20Length">Zero Length</a>: Zero-length arrays.</li>
326 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Empty-Structures.html#Empty%20Structures">Empty Structures</a>: Structures with no members.</li>
327 <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>
328 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Escaped-Newlines.html#Escaped%20Newlines">Escaped Newlines</a>: Slightly looser rules for escaped newlines.</li>
329 <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>
330 <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>
331 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Initializers.html#Initializers">Initializers</a>: Non-constant initializers.</li>
332 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Compound-Literals.html#Compound%20Literals">Compound Literals</a>: Compound literals give structures, unions,
333 or arrays as values.</li>
334 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Designated-Inits.html#Designated%20Inits">Designated Inits</a>: Labeling elements of initializers.</li>
335 <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>
336 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Case-Ranges.html#Case%20Ranges">Case Ranges</a>: `case 1 ... 9' and such.</li>
337 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Mixed-Declarations.html#Mixed%20Declarations">Mixed Declarations</a>: Mixing declarations and code.</li>
338 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Function-Prototypes.html#Function%20Prototypes">Function Prototypes</a>: Prototype declarations and old-style definitions.</li>
339 <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>
340 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Dollar-Signs.html#Dollar%20Signs">Dollar Signs</a>: Dollar sign is allowed in identifiers.</li>
341 <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>
342 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Alignment.html#Alignment">Alignment</a>: Inquiring about the alignment of a type or variable.</li>
343 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Inline.html#Inline">Inline</a>: Defining inline functions (as fast as macros).</li>
344 <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>
345 <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>
346 <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>
347 <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>
348 <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>
349 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Attribute-Syntax.html#Attribute%20Syntax">Attribute Syntax</a>: Formal syntax for attributes.</li>
354 <p>If you run into GCC extensions which have not been included in any of these
355 lists, please let us know (also including whether or not they work).</p>
359 <!-- ======================================================================= -->
360 <div class="doc_subsection">
361 <a name="c++-fe">Known problems with the C++ front-end</a>
364 <div class="doc_text">
366 <p>For this release, the C++ front-end is considered to be fully
367 tested and works for a number of non-trivial programs, including LLVM
372 <!-- _______________________________________________________________________ -->
373 <div class="doc_subsubsection">Bugs</div>
375 <div class="doc_text">
378 <li>The C++ front-end inherits all problems afflicting the <a href="#c-fe">C
385 <!-- _______________________________________________________________________ -->
386 <div class="doc_subsubsection">
390 <div class="doc_text">
394 <li>The C++ front-end is based on a pre-release of the GCC 3.4 C++ parser. This
395 parser is significantly more standards compliant (and picky) than prior GCC
396 versions. For more information, see the C++ section of the <a
397 href="http://gcc.gnu.org/gcc-3.4/changes.html">GCC 3.4 release notes</a>.</li>
399 <li>Destructors for local objects are not always run when a <tt>longjmp</tt> is
400 performed. In particular, destructors for objects in the <tt>longjmp</tt>ing
401 function and in the <tt>setjmp</tt> receiver function may not be run.
402 Objects in intervening stack frames will be destroyed, however (which is
403 better than most compilers).</li>
405 <li>The LLVM C++ front-end follows the <a
406 href="http://www.codesourcery.com/cxx-abi">Itanium C++ ABI</a>.
407 This document, which is not Itanium specific, specifies a standard for name
408 mangling, class layout, v-table layout, RTTI formats, and other C++
409 representation issues. Because we use this API, code generated by the LLVM
410 compilers should be binary compatible with machine code generated by other
411 Itanium ABI C++ compilers (such as G++, the Intel and HP compilers, etc).
412 <i>However</i>, the exception handling mechanism used by LLVM is very
413 different from the model used in the Itanium ABI, so <b>exceptions will not
414 interact correctly</b>. </li>
420 <!-- ======================================================================= -->
421 <div class="doc_subsection">
422 <a name="c-be">Known problems with the C back-end</a>
425 <div class="doc_text">
429 <li>The C back-end produces code that violates the ANSI C Type-Based Alias
430 Analysis rules. As such, special options may be necessary to compile the code
431 (for example, GCC requires the <tt>-fno-strict-aliasing</tt> option). This
432 problem probably cannot be fixed.</li>
434 <li><a href="http://llvm.cs.uiuc.edu/PR56">Zero arg vararg functions are not
435 supported</a>. This should not affect LLVM produced by the C or C++
442 <!-- ======================================================================= -->
443 <div class="doc_subsection">
444 <a name="x86-be">Known problems with the X86 back-end</a>
447 <div class="doc_text">
450 <li><a href="http://llvm.cs.uiuc.edu/PR566">Memory Mapped I/O Intrinsics do not fence memory</a></li>
455 <!-- ======================================================================= -->
456 <div class="doc_subsection">
457 <a name="ppc-be">Known problems with the PowerPC back-end</a>
460 <div class="doc_text">
468 <!-- ======================================================================= -->
469 <div class="doc_subsection">
470 <a name="sparcv9-be">Known problems with the SparcV9 back-end</a>
473 <div class="doc_text">
476 <li><a href="http://llvm.cs.uiuc.edu/PR60">[sparcv9] SparcV9 backend miscompiles
477 several programs in the LLVM test suite</a></li>
482 <!-- ======================================================================= -->
483 <div class="doc_subsection">
484 <a name="alpha-be">Known problems with the Alpha back-end</a>
487 <div class="doc_text">
491 <li>On 21164s, some rare FP arithmetic sequences which may trap do not have the
492 appropriate nops inserted to ensure restartability.</li>
494 <li>Due to the vararg problems, C++ exceptions do not work. Small changes are required to the CFE (which break correctness in the exception handler) to compile the exception handling library (and thus the C++ standard library).</li>
500 <!-- ======================================================================= -->
501 <div class="doc_subsection">
502 <a name="ia64-be">Known problems with the IA64 back-end</a>
505 <div class="doc_text">
509 <li>C++ programs are likely to fail on IA64, as calls to <tt>setjmp</tt> are
510 made where the argument is not 16-byte aligned, as required on IA64. (Strictly
511 speaking this is not a bug in the IA64 back-end; it will also be encountered
512 when building C++ programs using the C back-end.)</li>
514 <li>The C++ front-end does not use <a href="http://llvm.cs.uiuc.edu/PR406">IA64
515 ABI compliant layout of v-tables</a>. In particular, it just stores function
516 pointers instead of function descriptors in the vtable. This bug prevents
517 mixing C++ code compiled with LLVM with C++ objects compiled by other C++
520 <li>There are a few ABI violations which will lead to problems when mixing LLVM
521 output with code built with other compilers, particularly for floating-point
524 <li>Defining vararg functions is not supported (but calling them is ok).</li>
530 <!-- ======================================================================= -->
531 <div class="doc_subsection">
532 <a name="sparcv8">Known problems with the SPARC-V8 back-end</a>
535 <div class="doc_text">
538 <li>Many features are still missing (e.g. support for 64-bit integer
539 arithmetic). This back-end is in pre-beta state.</li>
543 <!-- *********************************************************************** -->
544 <div class="doc_section">
545 <a name="additionalinfo">Additional Information</a>
547 <!-- *********************************************************************** -->
549 <div class="doc_text">
551 <p>A wide variety of additional information is available on the <a
552 href="http://llvm.cs.uiuc.edu">LLVM web page</a>, including <a
553 href="http://llvm.cs.uiuc.edu/docs/">documentation</a> and <a
554 href="http://llvm.cs.uiuc.edu/pubs/">publications describing algorithms and
555 components implemented in LLVM</a>. The web page also contains versions of the
556 API documentation which is up-to-date with the CVS version of the source code.
557 You can access versions of these documents specific to this release by going
558 into the "<tt>llvm/doc/</tt>" directory in the LLVM tree.</p>
560 <p>If you have any questions or comments about LLVM, please feel free to contact
561 us via the <a href="http://llvm.cs.uiuc.edu/docs/#maillist"> mailing
566 <!-- *********************************************************************** -->
570 <a href="http://jigsaw.w3.org/css-validator/check/referer"><img
571 src="http://jigsaw.w3.org/css-validator/images/vcss" alt="Valid CSS!"></a>
572 <a href="http://validator.w3.org/check/referer"><img
573 src="http://www.w3.org/Icons/valid-html401" alt="Valid HTML 4.01!" /></a>
575 <a href="http://llvm.cs.uiuc.edu">The LLVM Compiler Infrastructure</a><br>
576 Last modified: $Date$