| LLVM 1.1 Release Notes | -
Written by Chris Lattner
+
Written by the LLVM team
+
| -Introduction - |
+
This document contains the release notes for the LLVM compiler +infrastructure, release 1.2. 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.2 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.
-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.+
Note that if you are reading this file from CVS, this document applies +to the next release, not the current one. To see the release notes for +the current or previous releases, see the releases page.
+ +| -What's New? - |
+
This is the third public release of the LLVM compiler infrastructure. +
+ +At this time, LLVM is known to correctly compile and run all non-unwinding C +& C++ SPEC CPU2000 benchmarks, the Olden benchmarks, and the Ptrdist +benchmarks. It has also been used to compile many other programs. LLVM +now also works with a broad variety of C++ programs, though it has still +received much less testing than the C front-end. +
+ ++The LLVM native code generators are very stable but do not currently support +unwinding (exception throwing or longjmping), which prevent them from +working with programs like the 253.perlbmk in SPEC CPU2000. The C +backend and the rest of LLVM supports these programs, so you can +still use LLVM with them. Support for unwinding will be added in a future +release. +
+ + + ++
+ + + -In this release, the following Quality of Implementation issues were fixed:+ +
+
+ + -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, 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.
+
Bugs in the LLVM Core:
+ +Bugs in the C/C++ front-end:
+ + + +| -Portability and Supported Platforms - |
LLVM has been extensively tested on Intel and AMD machines running Red +Hat Linux and FreeBSD. It has also been tested on Sun UltraSPARC workstations running Solaris 8. +Additionally, +LLVM works on Mac OS X 10.3 and above, but only with the C backend or +interpreter (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 extremely likely that we -missed something. We welcome portability patches and error messages.
+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. If you run into a problem, please check the LLVM bug database and submit a bug if +there isn't already one.
++
+such, execution of a threaded program could cause these data structures to be +corrupted.
+
+ +
-+ +
@@ -159,150 +262,224 @@ table in the archive).
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.
+ ignored by the LLVM compiler and will cause a different interpretation of + 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 +has not been tested as thoroughly as the C front-end. It has been tested and +works for a number of non-trivial programs, but there may be lurking bugs. +Please report any bugs or problems.
+ ++ front-end.
+href="http://gcc.gnu.org/gcc-3.4/changes.html">GCC 3.4 release notes.
+ Objects in intervening stack frames will be destroyed, however (which is + 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.
+cannot include special floating point numbers like Not-A-Number or +Infinity.
- -
+frontends.
| -Additional Information - |
A wide variety of additional information is available on the LLVM web page, +including mailing lists and 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/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.
+
+