X-Git-Url: http://plrg.eecs.uci.edu/git/?a=blobdiff_plain;f=docs%2FReleaseNotes.html;h=b0e3ba28e54ba3170be5d6151a381dd749476c24;hb=d051f7a13d8345ced6e409b3fe0313b9f865f1e0;hp=7fc4ead6001de6b4122006a3da049a7cb99fadb5;hpb=8497764d703aa5361790eaf72e64da33e31f2503;p=oota-llvm.git diff --git a/docs/ReleaseNotes.html b/docs/ReleaseNotes.html index 7fc4ead6001..b0e3ba28e54 100644 --- a/docs/ReleaseNotes.html +++ b/docs/ReleaseNotes.html @@ -4,11 +4,11 @@
-Written by the LLVM Team
+
This document contains the release notes for the LLVM compiler -infrastructure, release 2.1. Here we describe the status of LLVM, including +infrastructure, release 2.3. Here we describe the status of LLVM, including major improvements from the previous release and any known problems. All LLVM releases may be downloaded from the LLVM releases web site.
@@ -58,103 +61,69 @@ current one. To see the release notes for a specific releases, please see theThis is the twelfth public release of the LLVM Compiler Infrastructure. -It includes many features and refinements from LLVM 2.0.
+This is the fourteenth public release of the LLVM Compiler Infrastructure. +It includes many features and refinements from LLVM 2.2.
LLVM 2.1 brings two new beta C front-ends. First, Duncan, Anton and Devang -start syncing up llvm-gcc with GCC 4.2, yielding "llvm-gcc 4.2" (creative, -huh?). llvm-gcc 4.2 has the promise to bring much better FORTRAN and Ada -support to LLVM as well as features like atomic builtins, OpenMP, and many other -things. Check it out!
- -Second, LLVM now includes its own native C and Objective-C front-end (C++ is -in progress, but is not very far along) code named "clang". This front-end has a number of great -features, primarily aimed at source-level analysis and speeding up compile-time. -At this point though, the LLVM Code Generator component is still very early in -development, so it's mostly useful for people looking to build source-level -analysis tools or source-to-source translators.
+LLVM 2.2 was the last LLVM release to support llvm-gcc 4.0 and llvm-upgrade. +llvm-gcc 4.0 has been replaced with llvm-gcc 4.2. llvm-upgrade was useful for +upgrading llvm 1.9 files to llvm 2.x syntax, but you can always use a previous +llvm release to do this.
Some of the most noticable improvements this release have been in the -optimizer, speeding it up and making it more aggressive
- -LLVM 2.3 fully supports llvm-gcc 4.2 front-end.
-The clang project is an effort to build +a set of new 'llvm native' front-end technologies for the LLVM optimizer +and code generator. Currently, its C and Objective-C support is maturing +nicely, and it has advanced source-to-source analysis and transformation +capabilities. If you are interested in building source-level tools for C and +Objective-C (and eventually C++), you should take a look. However, note that +clang is not an official part of the LLVM 2.3 release. If you are interested in +this project, please see its web site.
foo
+LLVM 2.3 includes several major new capabilities:
New features include: -
+ +We put a significant amount of work into the code generator infrastructure, +which allows us to implement more aggressive algorithms and make it run +faster:
In addition to a huge array of bug fixes and minor performance tweaks, the +LLVM 2.3 optimizers support a few major enhancements:
-New features include: +
New target-specific features include:
llvm-gcc4 does not currently support Link-Time -Optimization on most platforms "out-of-the-box". Please inquire on the +
llvm-gcc does not currently support Link-Time +Optimization on most platforms "out-of-the-box". Please inquire on the llvmdev mailing list if you are interested.
"long double" is silently transformed by the front-end into "double". There -is no support for floating point data types of any size other than 32 and 64 -bits.
llvm-gcc does not support __builtin_apply yet. See Constructing Calls: Dispatching a call to another function.
llvm-gcc partially supports these GCC extensions:
llvm-gcc supports the vast majority of GCC extensions, including:
- -typeof
: referring to the type of an expression.?:
, ",
" and casts in lvalues.?:
expression.void
-pointers and function pointers.\e
stands for the character <ESC>.__const__
, __asm__
, etc., for header files.enum foo;
, with details to follow.If you run into GCC extensions which have not been included in any of these @@ -574,30 +477,57 @@ tested and works for a number of non-trivial programs, including LLVM itself, Qt, Mozilla, etc.