similar to: LLVM 2.0 Progress Report

LLVM 2.0 is done! Download it here: http://llvm.org/releases/ or view the release notes: http://llvm.org/releases/2.0/docs/ReleaseNotes.html LLVM 2.0 is a great release in many ways. It includes a wide range of new features, new optimizations, better codegen, and new targets. We were also able to signficantly revise several core aspects of the LLVM IR and design (such as the type system

Hi Everyone, It is getting to be that time again. I've scoured llvm-commits and collected a list of some of the major features we've developed since the last status update (from Feb 21). Please take a look and send me (off list) additions, feedback, corrections, etc. As usual, if I missed something, it's probably because there is such a huge amount of stuff happening,

Hi All, Here are my notes for the LLVM 1.8 release, please send me feedback :). I'm sure I've forgotten and overlooked something, if so, please let me know! <Note: we're back to 3-month release cycle: yay!> ----- 8< ----- 8< ----- High Level Changes: *. Jim has finished enough support for DWARF debugging information that it is now enabled by default in

LLVM 1.8 is available now! Download it here: http://llvm.org/releases/ Release notes here: http://llvm.org/releases/1.8/docs/ReleaseNotes.html This is a great new release with great new features and lots of refinements (better codegen, faster compiles, bugs fixed). One particularly nice feature of this release is that we're back to a regular 3-month release cycle, allowing users to have

Feedback below.. > <will insert overview blurb here> Big new things: llvm-gcc4, new sparc > backend, Generic vector/SSE/Altivec support, X86 Scalar SSE support, > debugging support, many target-independent codegen improvements, inline asm, > llvm.org/web-reg. > > > Core LLVM IR Improvements: > > * The LLVM IR now has full support for representing

Hi, i have compile and built the llvm-gcc4 and llvm 1.8a in my machine, but there is some problem about llvm-gcc4. It can not compile a cpp code like this: #include <iostream> using std::cout; using std::endl; int main() { cout << "Hello" << endl; } $llvm-g++ hello.cc -o hello /developer/zsth/llvm-gcc/install/bin/../lib/gcc/i686-pc-linux-gnu/4.0.1/../../..

LLVM 1.7 is available now! Download it here: http://llvm.org/releases/ Release notes here: http://llvm.org/releases/1.7/docs/ReleaseNotes.html This release is huge! It contains about twice the number of new features as any previous release, and includes some big-ticket items that people have been requesting for a long time. In particular, this release contains a completely rewritten llvm-gcc

Hi Everyone, Here are my notes on the LLVM 1.7 release, which will go into the final release announcement. As Tanya mentioned, it has been far too long since the last release, and there have been a lot of CVS commits since Novemeber. :) I went through them all and pulled out some of the major improvements, which I've listed below. I'm certain that I have forgotten some things, so

Aaron, On Thu, 2007-05-17 at 22:54 +0100, Aaron Gray wrote: > Tanya, > > I have done make check and nightly report tests on LLVM on the GCC 4.2.0 > release, on Linux x86 32 bit. > > On make check the bit intrinsics test is still failing but it works from the > command line, strange ? Can you be a bit more specific about which test is failing? Reid. > > What

Hi All, Here's the first draft of the release announcement for LLVM 1.9 that I'm working on. I'm sure I've forgotten and overlooked something, if so, please let me know! ----- 8< ------ 8< ----- <notes> Note: LLVM now correctly builds itself and passes all regression tests on Darwin X86 and Darwin PPC. No one has tried other targets to my knowledge. We hit

Reid Spencer wrote: >> If not, does it make >> sense to package the two in the two packages? >> Macports is a source-based >> packaging system, so it would seem odd to have to temporarily install >> llvm-gcc to build llvm, but then install llvm-gcc in a separate package. >> > > That issue goes away with llvm-gcc4. You would simply build llvm and

Hi Erick, On Fri, 2006-12-08 at 19:27 -0800, Erick Tryzelaar wrote: > Reid Spencer wrote: > > Yes, but its a bit verbose. The variables that control this are all > > defined in the Makefile.config file. The variables are: > > > > PROJ_prefix := /proj/llvm/install-1 > > PROJ_bindir := /proj/llvm/install-1/bin > > PROJ_libdir :=

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=utf-8" http-equiv="Content-Type"> <title></title> </head> <body bgcolor="#ffffff" text="#000000"> Reid,<br> <br> Here's the backtrace you asked for:<br> <br>

LLVM 1.9 is available now! Download it here: http://llvm.org/ releases/ or view the release here: http://llvm.org/releases/1.9/docs/ ReleaseNotes.html This is a huge new release with many improvements, new features, better codegen, faster compiles, and many bugs fixed. One telling feature is that LLVM now correctly builds itself and passes all its regression tests when self-hosted: an

All, Please welcome Zhou Sheng <zhousheng00 at gmail.com> to the LLVM development community. Sheng is from Beijing and is a Masters student at the University there. Sheng and I will be working together on some significant changes to LLVM in the coming months. Our first task is to implement integer types without signs in LLVM. You can read Chris Lattner's notes on this change at this

Hi John, llvm-gcc4 by default emits object files, just as gcc does. This is by design. If you want to get bytecode output you need to use the --emit- llvm-bc option. A complete list of the options that llvm-gcc4 supports can be obtained with "llvm-gcc -v --help" (lots of output). Here are the descriptions of the --emit-llvm options: -emit-llvm Emit LLVM code to the

On Thu, 16 Nov 2006, Tanya M. Lattner wrote: >> * I don't think this is ready for release. In particular the llvm-gcc4 >> binary >> seg faults on FC 5 for most of llvm-test programs. >> * I'm going to re-try without using the binaries and building >> everything from scratch. > > Does llvm-gcc4 seg fault for make check? I've done extensive

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=us-ascii" http-equiv="Content-Type"> <title></title> </head> <body bgcolor="#ffffff" text="#000000"> <b>Reid,<br> <br> I followed the steps but got stuck as described

Hi Robert, On Mon, 2006-11-06 at 12:45 -0800, Robert Mykland wrote: > Reid, > > Here's the backtrace you asked for: > > (gdb) bt > #0 0x0862d65c in llvm::LiveVariables::runOnMachineFunction () Hmm, this is a little strange. Your LLVM build is non-debug (there's no line numbers or arguments in any of the llvm related calls). However, your llvm-gcc build seems to have

Hi, I'm trying to track down some nasty glibc failures on Linux. I think the problem is that my system compiler (3.4.6) doesn't match llvm-gcc (4.0.x) so when the llc compiled programs run they don't quite get the right libstdc++. If I run a test program with: LD_LIBRARY_PATH=/path/to/my/llvm-gcc4/libs Output/sieve.llc then I get this: Output/sieve.llc: symbol lookup error: