| LLVM 1.0 Release Notes | -
Written by Chris Lattner
+
Written by Chris Lattner
+
| -Introduction - |
This document contains the release notes for the LLVM compiler +infrastructure, release 1.1. Here we describe the status of LLVM, including any +known problems, and bug fixes from the previous release. The most up-to-date +version of this document can be found on the LLVM 1.1 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 document may be updated after the release.
-For more information about LLVM, including information about potentially more +For more information about LLVM, including information about potentially more current releases, please check out the main web site. If you have questions or comments, the LLVM developer's mailing -list is a good place to send them.
+list is a good place to send them.
+ +Note that if you are reading this file from CVS, that this document applies +to the next release, not the previous one. To see the release notes for +the previous release, see the releases page.
+| -What's New? - |
+
+
This is the second public release of the LLVM compiler infrastructure. This +release implements the following new features:
+
+
In this release, the following missing features were implemented:
+
-TODO: Works on: Olden/Ptrdist benchmarks
+
- -It would be useful to give a pointer to a list of the available passes (at least -for the standard compiler techniques).
+ +
In this release, the following Quality of Implementation issues were +fixed:
- -| -Portability and Supported Platforms - |
+
In this release, the following bugs in the previous release were fixed:
++ +
At this time, LLVM is known to work properly with SPEC CPU 2000 (X86 only), +the Olden benchmarks, and the Ptrdist benchmarks among many other programs. +Note however that the Sparc and X86 backends do not currently support exception +throwing or long jumping (including 253.perlbmk in SPEC). For these programs, +you must use the C backend.
+ +| -Installation Instructions - |
LLVM has been extensively tested on Intel and AMD machines running Red +Hat Linux, and Sun UltraSPARC workstations running Solaris 8. Additionally, +LLVM works on Mac OS/X 10.3 and above, but only with the C back-end (no native +backend for the PowerPC is available yet). +The core LLVM infrastructure uses "autoconf" for portability, so hopefully we +work on more platforms than that. However, it is likely that we +missed something, and that minor porting is required to get LLVM to work on +new platforms. We welcome portability patches and error messages.
+| -Known Problems - |
This section contains all known problems with the LLVM system, listed by component. As new problems are discovered, they will be added to these -sections. +sections.
++
+such, execution of a threaded program could cause these data structures to be +corrupted.
+
+
@@ -180,132 +279,189 @@ sections.
int X[n];
foo(X);
}
-+
+
+
- - The following GCC extensions are partially supported. An ignored +
The following GCC extensions are partially supported. An ignored attribute means that the LLVM compiler ignores the presence of the attribute, but the code should still work. An unsupported attribute is one which is ignored by the LLVM compiler, which will cause a different interpretation of - the program.
+ the program.
+ __builtin_constant_p, and __builtin_expect (ignored). + + +
The following extensions are known to be supported:
- The following extensions are known to be supported: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 - lists, please let us know (also including whether or not they work). +
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 +lists, please let us know (also including whether or not they work).
+ +For this release, the C++ front-end is considered to be fully functional but +of beta quality. It has been tested and works for a number of simple +programs that collectively exercise most of the language. Nevertheless, it has +not been in use as long as the C front-end. Please report any bugs or +problems.
+ ++
+ front-end
performed. In particular, destructors for objects in the longjmping function and in the setjmp receiver function may not be run. Objects in intervening stack frames will be destroyed however (which is - better than most compilers).
+ better than most compilers).
Itanium ABI C++ compilers (such as G++, the Intel and HP compilers, etc). However, the exception handling mechanism used by LLVM is very different from the model used in the Itanium ABI, so exceptions will not - interact correctly . + interact correctly.
+or calls the C longjmp function will abort.
+
+or calls the C longjmp function will abort.
+problem probably cannot be fixed.
+
+
| -Additional Information - |
A wide variety of additional information is available on the LLVM web page, including mailing lists publications describing algorithms and components implemented in LLVM. The web page also contains versions of the API documentation which is up-to-date with the CVS version of the source code. You can access versions of these documents specific to this release by going into -the "llvm/www/doc/" directory in the LLVM tree.
+the "llvm/doc/" directory in the LLVM tree.
-If you have any questions or comments about LLVM, please feel free to contact us -via the mailing lists.+
If you have any questions or comments about LLVM, please feel free to contact +us via the mailing lists.
+
+