From d9ea017494c6895f04c5d79ccb990c831c67ef27 Mon Sep 17 00:00:00 2001
From: Chris Lattner This document contains the release notes for the LLVM compiler
-infrastructure, release 1.7. Here we describe the status of LLVM, including any
+infrastructure, release 1.8. Here we describe the status of LLVM, including any
known problems and major improvements from the previous release. The most
-up-to-date version of this document can be found on the LLVM releases web site. If you are
not reading this on the LLVM web pages, you should probably go there because
this document may be updated after the release. This is the eighth public release of the LLVM Compiler Infrastructure. This
release incorporates a large number of enhancements and new features,
-including vector support (Intel SSE and Altivec), a new GCC4.0-based
-C/C++ front-end, Objective C/C++ support, inline assembly support, and many
-other big features.
+including DWARF debugging support (C and C++ on Darwin/PPC), improved inline
+assembly support, a new nightly
+tester, llvm-config enhancments, many bugs
+fixed, and performance and compile time improvements.
LLVM 1.7 includes a brand new llvm-gcc, based on GCC 4.0.1. This version
-of llvm-gcc solves many serious long-standing problems with llvm-gcc, including
-all of those blocked by the llvm-gcc 4 meta
-bug. In addition, llvm-gcc4 implements support for many new features,
-including GCC inline assembly, generic vector support, SSE and Altivec
-intrinsics, and several new GCC attributes. Finally, llvm-gcc4 is
-significantly faster than llvm-gcc3, respects -O options, its -c/-S options
-correspond to GCC's (they emit native code), supports Objective C/C++, and
-it has debugging support well underway. If you can use it, llvm-gcc4 offers significant new functionality, and we
-hope that it will replace llvm-gcc3 completely in a future release.
-Unfortunately, it does not currently support C++ exception handling at all, and
-it only works on Apple Mac OS/X machines with X86 or PowerPC processors.
+ The llvm-gcc4 C front-end now generates debugging info for C and C++. This
+information is propagated through the compiler and the code generator can
+currently produce DWARF debugging information from it. DWARF is a standard
+debugging format used on many platforms, but currently LLVM only includes
+target support for Mac OS X targets for the 1.8 release.
The LLVM IR and llvm-gcc4 front-end now fully support arbitrary GCC inline assembly. The LLVM X86 and PowerPC
-code generators have initial support for it,
-being able to compile basic statements, but are missing some features. Please
-report any inline asm statements that crash the compiler or that are miscompiled
-as bugs. Inline assembly support is substantially improved in LLVM 1.8 over LLVM 1.7.
+Many unsupported features are now supported, and inline asm support in the X86
+backend is far better. llvm-gcc4 now supports global register variables as
+well. LLVM 1.7 includes a new, fully functional, SPARC backend built in the
-target-independent code generator. This SPARC backend includes support for
-SPARC V8 and SPARC V9 subtargets (controlling whether V9 features can be used),
-and targets the 32-bit SPARC ABI. The LLVM 1.7 release is the last release that will include the LLVM "SparcV9"
-backend, which was the very first LLVM native code generator. It will
-be removed in LLVM 1.8, being replaced with the new SPARC backend. LLVM now includes significantly extended support for SIMD vectors in its
-core instruction set. It now includes three new instructions for manipulating
-vectors: extractelement,
-insertelement, and
-shufflevector. Further,
-many bugs in vector handling have been fixed, and vectors are now supported by
-the target-independent code generator. For example, if a vector operation is
-not supported by a particular target, it will be correctly broken down and
-executed as scalar operations. Because llvm-gcc3 does not support GCC generic vectors or vector intrinsics,
-llvm-gcc4 must be used. The LLVM X86 backend now supports Intel SSE 1, 2, and 3, and now uses scalar
-SSE operations to implement scalar floating point math when the target supports
-SSE1 (for floats) or SSE2 (for doubles). Vector SSE instructions are generated
-by llvm-gcc4 when the generic vector mechanism or specific SSE intrinsics are
-used.
- The LLVM PowerPC backend now supports the Altivec instruction set, including
-both GCC -maltivec and -faltivec modes. Altivec instructions are generated
-by llvm-gcc4 when the generic vector mechanism or specific Altivec intrinsics
-are used.
+ The Loop Optimizer pass now used "Loop-Closed SSA Form", which makes it
+easier to update SSA form as loop transformations change the code. An
+immediate benefit of this is that the loop unswitching pass can now unswitch
+loops in more cases.
The code generator now lowers switch statements to jump tables, providing
+significant performance boosts for applications (e.g. interpreters) whose
+performance is highly correlated to switch statement performance. The LLVM JIT now allows clients to deallocate machine code JIT'd to its code
+buffer. This is important for long living applications that depend on the JIT.
+ This release includes many other improvements, including improvements to
+ the optimizers and code generators (improving the generated code) changes to
+ speed up the compiler in many ways (improving algorithms and fine tuning
+ code), and changes to reduce the code size of the compiler itself. More specific changes include:
-
+
+
-
+
+
-
-
-llvm-gcc3 has many significant problems that are fixed by llvm-gcc4. See - those blocked on the llvm-gcc4 meta bug. +llvm-gcc3 has many significant problems that are fixed by llvm-gcc4. Two major ones include:
llvm-gcc4 is far more stable and produces better code than llvm-gcc3, but +does not currently support Link-Time-Optimization or C++ Exception Handling, +which llvm-gcc3 does.
+