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 2.5 Release Notes</title>
11 <div class="doc_title">LLVM 2.5 Release Notes</div>
14 <li><a href="#intro">Introduction</a></li>
15 <li><a href="#subproj">Sub-project Status Update</a></li>
16 <li><a href="#externalproj">External Projects Using LLVM 2.5</a></li>
17 <li><a href="#whatsnew">What's New in LLVM 2.5?</a></li>
18 <li><a href="GettingStarted.html">Installation Instructions</a></li>
19 <li><a href="#portability">Portability and Supported Platforms</a></li>
20 <li><a href="#knownproblems">Known Problems</a></li>
21 <li><a href="#additionalinfo">Additional Information</a></li>
24 <div class="doc_author">
25 <p>Written by the <a href="http://llvm.org">LLVM Team</a></p>
28 <!-- *********************************************************************** -->
29 <div class="doc_section">
30 <a name="intro">Introduction</a>
32 <!-- *********************************************************************** -->
34 <div class="doc_text">
36 <p>This document contains the release notes for the LLVM Compiler
37 Infrastructure, release 2.5. Here we describe the status of LLVM, including
38 major improvements from the previous release and significant known problems.
39 All LLVM releases may be downloaded from the <a
40 href="http://llvm.org/releases/">LLVM releases web site</a>.</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 a Subversion checkout or the
49 main LLVM web page, this document applies to the <i>next</i> release, not the
50 current one. To see the release notes for a specific release, please see the
51 <a href="http://llvm.org/releases/">releases page</a>.</p>
55 <!-- Unfinished features in 2.5:
58 target-specific intrinsics
60 pre-alloc splitter, strong phi elim
61 llc -enable-value-prop, propagation of value info (sign/zero ext info) from
63 debug info for optimized code
65 postalloc scheduler: anti dependence breaking, hazard recognizer?
67 initial support for debug line numbers when optimization enabled, not useful in
68 2.5 but will be for 2.6.
72 <!-- for announcement email:
75 <!-- *********************************************************************** -->
76 <div class="doc_section">
77 <a name="subproj">Sub-project Status Update</a>
79 <!-- *********************************************************************** -->
81 <div class="doc_text">
83 The LLVM 2.5 distribution currently consists of code from the core LLVM
84 repository (which roughly includes the LLVM optimizers, code generators and
85 supporting tools) and the llvm-gcc repository. In addition to this code, the
86 LLVM Project includes other sub-projects that are in development. The two which
87 are the most actively developed are the <a href="#clang">Clang Project</a> and
88 the <a href="#vmkit">VMKit Project</a>.
94 <!--=========================================================================-->
95 <div class="doc_subsection">
96 <a name="clang">Clang: C/C++/Objective-C Frontend Toolkit</a>
99 <div class="doc_text">
101 <p>The <a href="http://clang.llvm.org/">Clang project</a> is an effort to build
102 a set of new 'LLVM native' front-end technologies for the LLVM optimizer
103 and code generator. While Clang is not included in the LLVM 2.5 release, it
104 is continuing to make major strides forward in all areas. Its C and Objective-C
105 parsing and code generation support is now very solid. For example, it is
106 capable of successfully building many real applications for X86-32 and X86-64,
107 including <a href="http://wiki.freebsd.org/BuildingFreeBSDWithClang">the FreeBSD
108 kernel</a>. C++ is also making <a
109 href="http://clang.llvm.org/cxx_status.html">incredible progress</a>, and work
110 on templates has recently started.</p>
112 <p>While Clang is not yet production quality, it is progressing very nicely and
113 is quite usable for building many C and Objective-C applications. If you are
114 interested in fast compiles and good diagnostics, we encourage you to try it out
115 by <a href="http://clang.llvm.org/get_started.html">building from mainline</a>
116 and reporting any issues you hit to the <a
117 href="http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev">Clang front-end mailing
120 <p>In the LLVM 2.5 time-frame, the Clang team has made many improvements:</p>
123 <li>Clang now has a new driver, which is focused on providing a GCC-compatible
125 <li>The X86-64 ABI is now supported.</li>
126 <li>Precompiled header support is now implemented.</li>
127 <li>Objective-C support is significantly improved beyond LLVM 2.4, supporting
128 many features, such as Objective-C Garbage Collection.</li>
129 <li>Many many bugs are fixed and many features have been added.</li>
132 <!--=========================================================================-->
133 <div class="doc_subsection">
134 <a name="clangsa">Clang Static Analyzer</a>
137 <div class="doc_text">
139 <p>Previously announced in the last LLVM release, the Clang project also
140 includes an early stage static source code analysis tool for <a
141 href="http://clang.llvm.org/StaticAnalysis.html">automatically finding bugs</a>
142 in C and Objective-C programs. The tool performs a growing set of checks to find
143 bugs that occur on a specific path within a program.</p>
145 <p>In the LLVM 2.5 time-frame there have been many significant improvements to
146 the analyzer's core path simulation engine and machinery for generating
147 path-based bug reports to end-users. Particularly noteworthy improvements
148 include experimental support for full field-sensitivity and reasoning about heap
149 objects as well as an improved value-constraints subengine that does a much
150 better job of reasoning about inequality relationships (e.g., <tt>x > 2</tt>)
151 between variables and constants.
153 <p>The set of checks performed by the static analyzer continue to expand, and
154 future plans for the tool include full source-level inter-procedural analysis
155 and deeper checks such as buffer overrun detection. There are many opportunities
156 to extend and enhance the static analyzer, and anyone interested in working on
157 this project is encouraged to get involved!</p>
161 <!--=========================================================================-->
162 <div class="doc_subsection">
163 <a name="vmkit">VMKit: JVM/CLI Virtual Machine Implementation</a>
166 <div class="doc_text">
168 The <a href="http://vmkit.llvm.org/">VMKit project</a> is an implementation of
169 a JVM and a CLI Virtual Machines (Microsoft .NET is an
170 implementation of the CLI) using the Just-In-Time compiler of LLVM.</p>
172 <p>Following LLVM 2.5, VMKit has its first release that you can find on its
173 <a href="http://vmkit.llvm.org/releases/">webpage</a>. The release includes
174 bug fixes, cleanup and new features. The major changes are:</p>
178 <li>Ahead of Time compiler: compiles .class files to llvm .bc. VMKit uses this
179 functionality to native compile the standard classes (eg java.lang.String).
180 Users can compile AOT .class files into dynamic libraries and run them with the
183 <li>New exception model: the dwarf exception model is very slow for
184 exception-intensive applications, so the JVM has had a new implementation of
185 exceptions which check at each function call if an exception happened. There is
186 a low performance penalty on applications without exceptions, but it is a big
187 gain for exception-intensive applications. For example the jack benchmark in
188 Spec JVM98 is 6x faster (performance gain of 83%).</li>
190 <li>New support for OSX/X64, Linux/X64 (with the Boehm GC), Linux/ppc32.</li>
195 <!-- *********************************************************************** -->
196 <div class="doc_section">
197 <a name="externalproj">External Projects Using LLVM 2.5</a>
199 <!-- *********************************************************************** -->
201 <!--=========================================================================-->
202 <div class="doc_subsection">
203 <a name="pure">Pure</a>
206 <div class="doc_text">
208 <a href="http://pure-lang.googlecode.com/">Pure</a>
209 is an algebraic/functional programming language based on term rewriting.
210 Programs are collections of equations which are used to evaluate expressions in
211 a symbolic fashion. Pure offers dynamic typing, eager and lazy evaluation,
212 lexical closures, a hygienic macro system (also based on term rewriting),
213 built-in list and matrix support (including list and matrix comprehensions) and
214 an easy-to-use C interface. The interpreter uses LLVM as a backend to
215 JIT-compile Pure programs to fast native code.</p>
217 <p>In addition to the usual algebraic data structures, Pure also has
218 MATLAB-style matrices in order to support numeric computations and signal
219 processing in an efficient way. Pure is mainly aimed at mathematical
220 applications right now, but it has been designed as a general purpose language.
221 The dynamic interpreter environment and the C interface make it possible to use
222 it as a kind of functional scripting language for many application areas.
227 <!--=========================================================================-->
228 <div class="doc_subsection">
229 <a name="ldc">LLVM D Compiler</a>
232 <div class="doc_text">
234 <a href="http://www.dsource.org/projects/ldc">LDC</a> is an implementation of
235 the D Programming Language using the LLVM optimizer and code generator.
236 LDC project works great with the LLVM 2.5 release. General improvmenets in this
237 cycle have included new inline asm constraint handling, better debug info
238 support, general bugfixes, and better x86-64 support. This has allowed
239 some major improvements in LDC, getting us much closer to being as
240 fully featured as the original DMD compiler from DigitalMars.
244 <!--=========================================================================-->
245 <div class="doc_subsection">
246 <a name="RoadsendPHP">Roadsend PHP</a>
249 <div class="doc_text">
250 <p><a href="http://code.roadsend.com/rphp">Roadsend PHP</a> (rphp) is an open
251 source compiler for the PHP programming language that uses LLVM for its
252 optimizer, JIT, and static compiler. This is a reimplementation of an earlier
253 project that is now based on the LLVM.</p>
257 <!-- *********************************************************************** -->
258 <div class="doc_section">
259 <a name="whatsnew">What's New in LLVM 2.5?</a>
261 <!-- *********************************************************************** -->
263 <div class="doc_text">
265 <p>This release includes a huge number of bug fixes, performance tweaks, and
266 minor improvements. Some of the major improvements and new features are listed
271 <!--=========================================================================-->
272 <div class="doc_subsection">
273 <a name="majorfeatures">Major New Features</a>
276 <div class="doc_text">
278 <p>LLVM 2.5 includes several major new capabilities:</p>
281 <li>LLVM 2.5 includes a brand new <a
282 href="http://en.wikipedia.org/wiki/XCore">XCore</a> backend.</li>
284 <li>llvm-gcc now generally supports the GFortan front-end, and the precompiled
285 release binaries now support Fortran, even on Mac OS/X.</li>
287 <li>CMake is now used by the <a href="GettingStartedVS.html">LLVM build process
288 on Windows</a>. It automatically generates Visual Studio project files (and
289 more) from a set of simple text files. This makes it much easier to
290 maintain. In time, we'd like to standardize on CMake for everything.</li>
292 <li>LLVM 2.5 now uses (and includes) Google Test for unit testing.</li>
294 <li>The LLVM native code generator now supports arbitrary precision integers.
295 Types like <tt>i33</tt> have long been valid in the LLVM IR, but were previously
296 only supported by the interpreter. Note that the C backend still does not
299 <li>LLVM 2.5 no longer uses 'bison', so it is easier to build on Windows.</li>
305 <!--=========================================================================-->
306 <div class="doc_subsection">
307 <a name="llvm-gcc">llvm-gcc 4.2 Improvements</a>
310 <div class="doc_text">
312 <p>LLVM fully supports the llvm-gcc 4.2 front-end, which marries the GCC
313 front-ends and driver with the LLVM optimizer and code generator. It currently
314 includes support for the C, C++, Objective-C, Ada, and Fortran front-ends.</p>
317 <li>In this release, the GCC inliner is completely disabled. Previously the GCC
318 inliner was used to handle always-inline functions and other cases. This caused
319 problems with code size growth, and it is completely disabled in this
322 <li>llvm-gcc (and LLVM in general) now support code generation for stack
323 canaries, which is an effective form of <a
324 href="http://en.wikipedia.org/wiki/Stack-smashing_protection">buffer overflow
325 protection</a>. llvm-gcc supports this with the <tt>-fstack-protector</tt>
326 command line option (just like GCC). In LLVM IR, you can request code
327 generation for stack canaries with function attributes.
334 <!--=========================================================================-->
335 <div class="doc_subsection">
336 <a name="coreimprovements">LLVM IR and Core Improvements</a>
339 <div class="doc_text">
340 <p>LLVM IR has several new features that are used by our existing front-ends and
341 can be useful if you are writing a front-end for LLVM:</p>
344 <li>The <a href="LangRef.html#i_shufflevector">shufflevector</a> instruction
345 has been generalized to allow different shuffle mask width than its input
346 vectors. This allows you to use shufflevector to combine two
347 "<4 x float>" vectors into a "<8 x float>" for example.</li>
349 <li>LLVM IR now supports new intrinsics for computing and acting on <a
350 href="LangRef.html#int_overflow">overflow of integer operations</a>. This allows
351 efficient code generation for languages that must trap or throw an exception on
352 overflow. While these intrinsics work on all targets, they only generate
353 efficient code on X86 so far.</li>
355 <li>LLVM IR now supports a new <a href="LangRef.html#linkage">private
356 linkage</a> type to produce labels that are stripped by the assembler before it
357 produces a .o file (thus they are invisible to the linker).</li>
359 <li>LLVM IR supports two new attributes for better alias analysis. The <a
360 href="LangRef.html#paramattrs">noalias</a> attribute can now be used on the
361 return value of a function to indicate that it returns new memory (e.g.
362 'malloc', 'calloc', etc).</li>
364 <li>The new <a href="LangRef.html#paramattrs">nocapture</a> attribute can be
365 used on pointer arguments to functions that access through but do not return the
366 pointer in a data structure that out lives the call (e.g. 'strlen', 'memcpy',
367 and many others). The simplifylibcalls pass applies these attributes to
368 standard libc functions.</li>
370 <li>The parser for ".ll" files in lib/AsmParser is now completely rewritten as a
371 recursive descent parser. This parser produces better error messages (including
372 caret diagnostics) is less fragile (less likely to crash on strange things) does
373 not leak memory, is more efficient, and eliminates LLVM's last use of the
376 <li>Debug information representation and manipulation internals have been
377 consolidated to use a new set of classes in
378 <tt>llvm/Analysis/DebugInfo.h</tt> classes. These routines are more
379 efficient, robust, and extensible and replace the older mechanisms.
380 llvm-gcc, clang, and the code generator now use them to create and process
381 debug information.</li>
387 <!--=========================================================================-->
388 <div class="doc_subsection">
389 <a name="optimizer">Optimizer Improvements</a>
392 <div class="doc_text">
394 <p>In addition to a huge array of bug fixes and minor performance tweaks, this
395 release includes a few major enhancements and additions to the optimizers:</p>
399 <li>The loop optimizer now improves floating point induction variables in
400 several ways, including adding shadow induction variables to avoid
401 "integer <-> floating point" conversions in loops when safe.</li>
403 <li>The "-mem2reg" pass is now much faster on code with huge basic blocks.</li>
405 <li>The "-jump-threading" pass is more powerful: it is iterative
406 and handles threading based on values with fully and partially redundant
409 <li>The "-memdep" memory dependence analysis pass (used by GVN and memcpyopt) is
410 both faster and more aggressive.</li>
412 <li>The "-scalarrepl" scalar replacement of aggregates pass is more aggressive
413 about promoting unions to registers.</li>
420 <!--=========================================================================-->
421 <div class="doc_subsection">
422 <a name="codegen">Target Independent Code Generator Improvements</a>
425 <div class="doc_text">
427 <p>We have put a significant amount of work into the code generator
428 infrastructure, which allows us to implement more aggressive algorithms and make
432 <li>The <a href="WritingAnLLVMBackend.html">Writing an LLVM Compiler
433 Backend</a> document has been greatly expanded and is substantially more
436 <li>The SelectionDAG type legalization logic has been completely rewritten, is
437 now more powerful (it supports arbitrary precision integer types for example),
438 and more correct in several corner cases. The type legalizer converts
439 operations on types that are not natively supported by the target machine into
440 equivalent code sequences that only use natively supported types. The old type
441 legalizer is still available (for now) and will be used if
442 <tt>-disable-legalize-types</tt> is passed to the code generator.
445 <li>The code generator now supports widening illegal vectors to larger legal
446 ones (for example, converting operations on <3 x float> to work on
447 <4 x float>) which is very important for common graphics
450 <li>The assembly printers for each target are now split out into their own
451 libraries that are separate from the main code generation logic. This reduces
452 code size of JIT compilers by not requiring them to be linked in.</li>
454 <li>The 'fast' instruction selection path (used at -O0 and for fast JIT
455 compilers) now supports accelerating codegen for code that uses exception
456 handling constructs.</li>
458 <li>The optional PBQP register allocator now supports register coalescing.</li>
462 <!--=========================================================================-->
463 <div class="doc_subsection">
464 <a name="x86">X86-32 and X86-64 Target Improvements</a>
467 <div class="doc_text">
468 <p>New features of the X86 target include:
472 <li>The "<a href="LangRef.html#int_returnaddress">llvm.returnaddress</a>"
473 intrinsic (which is used to implement "__builtin_return_address") now supports
474 non-zero stack depths on X86.</li>
476 <li>The X86 backend now supports code generation of vector shift operations
477 using SSE instructions.</li>
479 <li>X86-64 code generation now takes advantage of red zone (unless
480 -mno-red-zone option is specified).</li>
482 <li>The X86 backend now supports using address space #256 in LLVM IR as a way of
483 performing memory references off the GS segment register. This allows a
484 front-end to take advantage of very low-level programming techniques when
485 targetting X86 CPUs. See test/CodeGen/X86/movgs.ll for a simple example.</li>
487 <li>The X86 backend now supports a <tt>-disable-mmx</tt> command line option to
488 prevent use of MMX even on chips that support it. This is important for cases
489 where code does not contain the proper "llvm.x86.mmx.emms" intrinsics.</li>
491 <li>The X86 JIT now detects the new Intel "<a
492 href="http://en.wikipedia.org/wiki/Intel_Core_i7">Core i7</a>" and <a
493 href="http://en.wikipedia.org/wiki/Intel_Atom">Atom</a>" chips,
494 auto-configuring itself appropriately for the features of these chips.</li>
496 <li>The JIT now supports exception handling constructs on Linux/X86-64 and
498 <li>The JIT supports Thread Local Storage (TLS) on Linux/X86-32 but not yet on
505 <!--=========================================================================-->
506 <div class="doc_subsection">
507 <a name="pic16">PIC16 Target Improvements</a>
510 <div class="doc_text">
511 <p>New features of the PIC16 target include:
515 <li>Both direct and indirect load/stores work now.</li>
516 <li>Logical, bitwise and conditional operations now work for integer data
518 <li>Function calls involving basic types work now.</li>
519 <li>Support for integer arrays.</li>
520 <li>Compiler can now emit libcalls for operations not support by m/c insns.</li>
521 <li>Support for both data and rom address spaces.</li>
525 <p>Things not yet supported:</p>
528 <li>Floating point.</li>
529 <li>Passing/returning aggregate types to/from functions.</li>
530 <li>Variable arguments.</li>
531 <li>Indirect function calls.</li>
532 <li>Interrupts/programs.</li>
540 <!--=========================================================================-->
541 <div class="doc_subsection">
542 <a name="llvmc">Improvements in LLVMC</a>
545 <div class="doc_text">
546 <p>New features include:</p>
549 <li>Beginning with LLVM 2.5, <tt>llvmc2</tt> is known as
550 just <tt>llvmc</tt>. The old <tt>llvmc</tt> driver was removed.</li>
552 <li>The Clang plugin was substantially improved and is now enabled
553 by default. The command <tt>llvmc --clang</tt> can be now used as a
554 synonym to <tt>ccc</tt>.</li>
556 <li>There is now a <tt>--check-graph</tt> option which is supposed to catch
557 common errors like multiple default edges, mismatched output/input language
558 names and cycles. In general, these checks can't be done at compile-time
559 because of the need to support plugins.</li>
561 <li>Plugins are now more flexible and can refer to compilation graph nodes and
562 options defined in other plugins. To manage dependencies, a priority-sorting
563 mechanism was introduced. This change affects the TableGen file syntax; see the
564 documentation for details.</li>
566 <li>Hooks can now be provided with arguments. The syntax is "<tt>$CALL(MyHook,
567 'Arg1', 'Arg2', 'Arg #3')</tt>".</li>
569 <li>A new option type: multi-valued option, for options that take more than one
570 argument (for example, "<tt>-foo a b c</tt>").</li>
572 <li>New option properties: '<tt>one_or_more</tt>', '<tt>zero_or_more</tt>',
573 '<tt>hidden</tt>' and '<tt>really_hidden</tt>'.</li>
575 <li>The '<tt>case</tt>' expression gained an '<tt>error</tt>' action and
576 an '<tt>empty</tt>' test (equivalent to "<tt>(not (not_empty ...))</tt>").</li>
578 <li>Documentation now looks more consistent to the rest of the LLVM
579 docs. There is also a man page now.</li>
586 <!--=========================================================================-->
587 <div class="doc_subsection">
588 <a name="otherimprovements">Other Improvements</a>
591 <div class="doc_text">
592 <p>New features include:
602 <!--=========================================================================-->
603 <div class="doc_subsection">
604 <a name="changes">Major Changes and Removed Features</a>
607 <div class="doc_text">
609 <p>If you're already an LLVM user or developer with out-of-tree changes based
610 on LLVM 2.4, this section lists some "gotchas" that you may run into upgrading
611 from the previous release.</p>
615 <li>llvm-gcc defaults to -fno-math-errno on all X86 targets.</li>
619 <p>In addition, many APIs have changed in this release. Some of the major LLVM
633 <!-- *********************************************************************** -->
634 <div class="doc_section">
635 <a name="portability">Portability and Supported Platforms</a>
637 <!-- *********************************************************************** -->
639 <div class="doc_text">
641 <p>LLVM is known to work on the following platforms:</p>
644 <li>Intel and AMD machines (IA32, X86-64, AMD64, EMT-64) running Red Hat
645 Linux, Fedora Core and FreeBSD (and probably other unix-like systems).</li>
646 <li>PowerPC and X86-based Mac OS X systems, running 10.3 and above in 32-bit
647 and 64-bit modes.</li>
648 <li>Intel and AMD machines running on Win32 using MinGW libraries (native).</li>
649 <li>Intel and AMD machines running on Win32 with the Cygwin libraries (limited
650 support is available for native builds with Visual C++).</li>
651 <li>Sun UltraSPARC workstations running Solaris 10.</li>
652 <li>Alpha-based machines running Debian GNU/Linux.</li>
653 <li>Itanium-based (IA64) machines running Linux and HP-UX.</li>
656 <p>The core LLVM infrastructure uses GNU autoconf to adapt itself
657 to the machine and operating system on which it is built. However, minor
658 porting may be required to get LLVM to work on new platforms. We welcome your
659 portability patches and reports of successful builds or error messages.</p>
663 <!-- *********************************************************************** -->
664 <div class="doc_section">
665 <a name="knownproblems">Known Problems</a>
667 <!-- *********************************************************************** -->
669 <div class="doc_text">
671 <p>This section contains significant known problems with the LLVM system,
672 listed by component. If you run into a problem, please check the <a
673 href="http://llvm.org/bugs/">LLVM bug database</a> and submit a bug if
674 there isn't already one.</p>
678 <!-- ======================================================================= -->
679 <div class="doc_subsection">
680 <a name="experimental">Experimental features included with this release</a>
683 <div class="doc_text">
685 <p>The following components of this LLVM release are either untested, known to
686 be broken or unreliable, or are in early development. These components should
687 not be relied on, and bugs should not be filed against them, but they may be
688 useful to some people. In particular, if you would like to work on one of these
689 components, please contact us on the <a
690 href="http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev">LLVMdev list</a>.</p>
693 <li>The MSIL, IA64, Alpha, SPU, MIPS, and PIC16 backends are experimental.</li>
694 <li>The llc "<tt>-filetype=asm</tt>" (the default) is the only supported
695 value for this option.</li>
700 <!-- ======================================================================= -->
701 <div class="doc_subsection">
702 <a name="x86-be">Known problems with the X86 back-end</a>
705 <div class="doc_text">
708 <li>The X86 backend does not yet support
709 all <a href="http://llvm.org/PR879">inline assembly that uses the X86
710 floating point stack</a>. It supports the 'f' and 't' constraints, but not
712 <li>The X86 backend generates inefficient floating point code when configured
713 to generate code for systems that don't have SSE2.</li>
714 <li>Win64 code generation wasn't widely tested. Everything should work, but we
715 expect small issues to happen. Also, llvm-gcc cannot build mingw64 runtime
717 to <a href="http://llvm.org/PR2255">several</a>
718 <a href="http://llvm.org/PR2257">bugs</a> due to lack of support for the
719 'u' inline assembly constraint and X87 floating point inline assembly.</li>
720 <li>The X86-64 backend does not yet support the LLVM IR instruction
721 <tt>va_arg</tt>. Currently, the llvm-gcc and front-ends support variadic
722 argument constructs on X86-64 by lowering them manually.</li>
727 <!-- ======================================================================= -->
728 <div class="doc_subsection">
729 <a name="ppc-be">Known problems with the PowerPC back-end</a>
732 <div class="doc_text">
735 <li>The Linux PPC32/ABI support needs testing for the interpreter and static
736 compilation, and lacks support for debug information.</li>
741 <!-- ======================================================================= -->
742 <div class="doc_subsection">
743 <a name="arm-be">Known problems with the ARM back-end</a>
746 <div class="doc_text">
749 <li>Thumb mode works only on ARMv6 or higher processors. On sub-ARMv6
750 processors, thumb programs can crash or produce wrong
751 results (<a href="http://llvm.org/PR1388">PR1388</a>).</li>
752 <li>Compilation for ARM Linux OABI (old ABI) is supported, but not fully tested.
754 <li>There is a bug in QEMU-ARM (<= 0.9.0) which causes it to incorrectly
756 programs compiled with LLVM. Please use more recent versions of QEMU.</li>
761 <!-- ======================================================================= -->
762 <div class="doc_subsection">
763 <a name="sparc-be">Known problems with the SPARC back-end</a>
766 <div class="doc_text">
769 <li>The SPARC backend only supports the 32-bit SPARC ABI (-m32), it does not
770 support the 64-bit SPARC ABI (-m64).</li>
775 <!-- ======================================================================= -->
776 <div class="doc_subsection">
777 <a name="mips-be">Known problems with the MIPS back-end</a>
780 <div class="doc_text">
783 <li>The O32 ABI is not fully supported.</li>
784 <li>64-bit MIPS targets are not supported yet.</li>
789 <!-- ======================================================================= -->
790 <div class="doc_subsection">
791 <a name="alpha-be">Known problems with the Alpha back-end</a>
794 <div class="doc_text">
798 <li>On 21164s, some rare FP arithmetic sequences which may trap do not have the
799 appropriate nops inserted to ensure restartability.</li>
804 <!-- ======================================================================= -->
805 <div class="doc_subsection">
806 <a name="ia64-be">Known problems with the IA64 back-end</a>
809 <div class="doc_text">
812 <li>The Itanium backend is highly experimental, and has a number of known
813 issues. We are looking for a maintainer for the Itanium backend. If you
814 are interested, please contact the LLVMdev mailing list.</li>
819 <!-- ======================================================================= -->
820 <div class="doc_subsection">
821 <a name="c-be">Known problems with the C back-end</a>
824 <div class="doc_text">
827 <li><a href="http://llvm.org/PR802">The C backend has only basic support for
828 inline assembly code</a>.</li>
829 <li><a href="http://llvm.org/PR1658">The C backend violates the ABI of common
830 C++ programs</a>, preventing intermixing between C++ compiled by the CBE and
831 C++ code compiled with llc or native compilers.</li>
832 <li>The C backend does not support all exception handling constructs.</li>
833 <li>The C backend does not support arbitrary precision integers.</li>
839 <!-- ======================================================================= -->
840 <div class="doc_subsection">
841 <a name="c-fe">Known problems with the llvm-gcc C front-end</a>
844 <div class="doc_text">
846 <p>llvm-gcc does not currently support <a href="http://llvm.org/PR869">Link-Time
847 Optimization</a> on most platforms "out-of-the-box". Please inquire on the
848 LLVMdev mailing list if you are interested.</p>
850 <p>The only major language feature of GCC not supported by llvm-gcc is
851 the <tt>__builtin_apply</tt> family of builtins. However, some extensions
852 are only supported on some targets. For example, trampolines are only
853 supported on some targets (these are used when you take the address of a
854 nested function).</p>
856 <p>If you run into GCC extensions which are not supported, please let us know.
861 <!-- ======================================================================= -->
862 <div class="doc_subsection">
863 <a name="c++-fe">Known problems with the llvm-gcc C++ front-end</a>
866 <div class="doc_text">
868 <p>The C++ front-end is considered to be fully
869 tested and works for a number of non-trivial programs, including LLVM
870 itself, Qt, Mozilla, etc.</p>
873 <li>Exception handling works well on the X86 and PowerPC targets. Currently
874 only Linux and Darwin targets are supported (both 32 and 64 bit).</li>
879 <!-- ======================================================================= -->
880 <div class="doc_subsection">
881 <a name="fortran-fe">Known problems with the llvm-gcc Fortran front-end</a>
884 <div class="doc_text">
886 <li>Fortran support generally works, but there are still several unresolved bugs
887 in Bugzilla. Please see the tools/gfortran component for details.</li>
889 <li>The Fortran front-end currently does not build on Darwin (without tweaks)
890 due to unresolved dependencies on the C front-end.</li>
894 <!-- ======================================================================= -->
895 <div class="doc_subsection">
896 <a name="ada-fe">Known problems with the llvm-gcc Ada front-end</a>
899 <div class="doc_text">
900 The llvm-gcc 4.2 Ada compiler works fairly well, however this is not a mature
901 technology and problems should be expected.
903 <li>The Ada front-end currently only builds on X86-32. This is mainly due
904 to lack of trampoline support (pointers to nested functions) on other platforms,
905 however it <a href="http://llvm.org/PR2006">also fails to build on X86-64</a>
906 which does support trampolines.</li>
907 <li>The Ada front-end <a href="http://llvm.org/PR2007">fails to bootstrap</a>.
908 This is due to lack of LLVM support for <tt>setjmp</tt>/<tt>longjmp</tt> style
909 exception handling, which is used internally by the compiler.
910 Workaround: configure with --disable-bootstrap.</li>
911 <li>The c380004, <a href="http://llvm.org/PR2010">c393010</a>
912 and <a href="http://llvm.org/PR2421">cxg2021</a> ACATS tests fail
913 (c380004 also fails with gcc-4.2 mainline).
914 If the compiler is built with checks disabled then <a href="http://llvm.org/PR2010">c393010</a>
915 causes the compiler to go into an infinite loop, using up all system memory.</li>
916 <li>Some gcc specific Ada tests continue to crash the compiler.</li>
917 <li>The -E binder option (exception backtraces)
918 <a href="http://llvm.org/PR1982">does not work</a> and will result in programs
919 crashing if an exception is raised. Workaround: do not use -E.</li>
920 <li>Only discrete types <a href="http://llvm.org/PR1981">are allowed to start
921 or finish at a non-byte offset</a> in a record. Workaround: do not pack records
922 or use representation clauses that result in a field of a non-discrete type
923 starting or finishing in the middle of a byte.</li>
924 <li>The <tt>lli</tt> interpreter <a href="http://llvm.org/PR2009">considers
925 'main' as generated by the Ada binder to be invalid</a>.
926 Workaround: hand edit the file to use pointers for <tt>argv</tt> and
927 <tt>envp</tt> rather than integers.</li>
928 <li>The <tt>-fstack-check</tt> option <a href="http://llvm.org/PR2008">is
933 <!-- *********************************************************************** -->
934 <div class="doc_section">
935 <a name="additionalinfo">Additional Information</a>
937 <!-- *********************************************************************** -->
939 <div class="doc_text">
941 <p>A wide variety of additional information is available on the <a
942 href="http://llvm.org">LLVM web page</a>, in particular in the <a
943 href="http://llvm.org/docs/">documentation</a> section. The web page also
944 contains versions of the API documentation which is up-to-date with the
945 Subversion version of the source code.
946 You can access versions of these documents specific to this release by going
947 into the "<tt>llvm/doc/</tt>" directory in the LLVM tree.</p>
949 <p>If you have any questions or comments about LLVM, please feel free to contact
950 us via the <a href="http://llvm.org/docs/#maillist"> mailing
955 <!-- *********************************************************************** -->
959 <a href="http://jigsaw.w3.org/css-validator/check/referer"><img
960 src="http://jigsaw.w3.org/css-validator/images/vcss-blue" alt="Valid CSS"></a>
961 <a href="http://validator.w3.org/check/referer"><img
962 src="http://www.w3.org/Icons/valid-html401-blue" alt="Valid HTML 4.01"></a>
964 <a href="http://llvm.org/">LLVM Compiler Infrastructure</a><br>
965 Last modified: $Date$