similar to: [LLVMdev] 2.7 Pre-Release2 Available!

Is there are chance to get http://llvm.org/bugs/show_bug.cgi?id=5081 fixed in 2.6? The affected application did compile with with LLVM 2.5. I haven't yet checked whether TOT fixed this already, however, but will do this if necessary. Thanks, Torvald On Saturday 17 October 2009 20:51:05 Tanya Lattner wrote: > LLVMers, > > 2.6 pre-release2 is ready to be tested by the community.

Hi Tanya, glad to see that 2.6 release is coming. :) After doing some testing with valgrind on this release, I have find a little "undefined memory" error in DefaultJITMemoryManager related to the PoisonMemory field. This bug has been corrected in trunk with revision r80192. Attached is a patch which cleanly apply same correction on the release-2.6 branch. Thanks, Olivier. On Sat,

On Fri, Feb 20, 2009 at 11:45 PM, Tanya Lattner <tonic at nondot.org> wrote: > LLVMers, > > The 2.5 pre-release2 is finally available for testing: > http://llvm.org/prereleases/2.5/ > > If you have time, I'd appreciate anyone who can help test the release. > Please do the following: > > 1) Download/compile llvm source, and either compile llvm-gcc source or use

LLVMers, The 2.5 pre-release2 is finally available for testing: http://llvm.org/prereleases/2.5/ If you have time, I'd appreciate anyone who can help test the release. Please do the following: 1) Download/compile llvm source, and either compile llvm-gcc source or use llvm-gcc binary (please compile llvm-gcc with fortran if you can). 2) Run make check, send me the testrun.log 3) Run

On Fri, Feb 20, 2009 at 11:45 PM, Tanya Lattner <tonic at nondot.org> wrote: > LLVMers, > > The 2.5 pre-release2 is finally available for testing: > http://llvm.org/prereleases/2.5/ > > If you have time, I'd appreciate anyone who can help test the release. > Please do the following: > > 1) Download/compile llvm source, and either compile llvm-gcc source or

On Sat, Feb 21, 2009 at 9:54 PM, Aaron Gray <aaronngray.lists at googlemail.com > wrote: > On Fri, Feb 20, 2009 at 11:45 PM, Tanya Lattner <tonic at nondot.org> wrote: > >> LLVMers, >> >> The 2.5 pre-release2 is finally available for testing: >> http://llvm.org/prereleases/2.5/ >> >> If you have time, I'd appreciate anyone who can help

LLVMers, 2.6 pre-release1 is ready to be tested by the community. http://llvm.org/prereleases/2.6/ You will notice that we have quite a few pre-compiled binaries (of both clang and llvm-gcc). We have identified several bugs that will be fixed in pre-release2, so please search the bug database before filing a new bug. If you have time, I'd appreciate anyone who can help test the

Tanya Lattner wrote: > LLVMers, > > 2.6 pre-release1 is ready to be tested by the community. > http://llvm.org/prereleases/2.6/ > > You will notice that we have quite a few pre-compiled binaries (of > both clang and llvm-gcc). We have identified several bugs that will be > fixed in pre-release2, so please search the bug database before filing > a new bug. > >

> 2.6 pre-release2 is ready to be tested by the community. Excellent! Would you care to update the "LLVM 2.6 release schedule" on the front page of the web site? Thanks, Jay.

On 2009-08-31 08:50, Tanya Lattner wrote: > LLVMers, > > 2.6 pre-release1 is ready to be tested by the community. > http://llvm.org/prereleases/2.6/ > Hi Tanya, Here are the results for x86_64 Linux (Debian unstable): > You will notice that we have quite a few pre-compiled binaries (of > both clang and llvm-gcc). We have identified several bugs that will be > fixed in

Just a reminder that today is the last day for pre-release2 testing. Thanks, Tanya

The 2.7 pre-release testing ends tomorrow March 24th (11:59PM PDT). I've updated the 2.7 release schedule to include a one week regression fixing week. This is only for regressions found in 2.7 and not for miscellaneous bug fixes. I will no longer be merging in patches that are not a regression as defined in our release process (http://llvm.org/docs/HowToReleaseLLVM.html#release-qualify).

All, There has been a huge lack of response to the release. We need people to help fix regressions and to participate in testing the release. Without this support, I see no reason that the release team should spend their time qualifying a release. We need to get all regressions fixed before 2.7 can continue onto pre-release2. Please take a look at all release blockers:

On Oct 21, 2009, at 3:44 PM, Tanya Lattner wrote: > Just a reminder that today is the last day for pre-release2 testing. > Hi Tanya, Attached are the log files for Mac OS X 10.5.8 on PowerPC. There are these failures for clang: ******************** Failing Tests (20): /Volumes/SandBox/2.6/llvm-2.6/tools/clang/test/CodeGen/ always_inline.c

Hi Tanya, The sources weren't updated for this pre-release testing. So I had the same problems on PPC. -bw On Sun, Aug 30, 2009 at 10:50 PM, Tanya Lattner<lattner at apple.com> wrote: > LLVMers, > 2.6 pre-release1 is ready to be tested by the community. > http://llvm.org/prereleases/2.6/ > You will notice that we have quite a few pre-compiled binaries (of both > clang

On Sun, Feb 22, 2009 at 2:56 AM, Aaron Gray <aaronngray.lists at googlemail.com > wrote: > On Sat, Feb 21, 2009 at 9:54 PM, Aaron Gray < > aaronngray.lists at googlemail.com> wrote: > >> On Fri, Feb 20, 2009 at 11:45 PM, Tanya Lattner <tonic at nondot.org>wrote: >> >>> LLVMers, >>> >>> The 2.5 pre-release2 is finally available

Just a reminder that the 2.7 code freeze is on Feb 21st. All major changes should be committed approximately 1 week before the code freeze to ensure adequate testing. Please do your part to keep the tree stable in the days leading up to the code freeze. Thanks! -Tanya 2/21 - Code Freeze (9PM PST) 2/27 - Pre-release1 released & community testing begins 3/6 - Pre-release1 testing ends 3/13

On Feb 12, 2010, at 3:02 PM, Douglas Gregor wrote: > > On Feb 12, 2010, at 8:25 AM, David Greene wrote: > >> On Thursday 11 February 2010 18:17:33 Tanya Lattner wrote: >>> Just a reminder that the 2.7 code freeze is on Feb 21st. >>> >>> All major changes should be committed approximately 1 week before the code >>> freeze to ensure adequate

I am definitely in favor of this if it is ok with Tanya. I hope to spend some time in the next few weeks on tracking down miscompiles, and it would be great to get Clang to the "early-but-usable-beta" stage so it makes sense to roll binaries for 2.7. Tanya, I can also do the x86-32-pc-linux release testing if no one else steps up. - Daniel On Fri, Feb 12, 2010 at 3:02 PM, Douglas

On Feb 12, 2010, at 8:25 AM, David Greene wrote: > On Thursday 11 February 2010 18:17:33 Tanya Lattner wrote: >> Just a reminder that the 2.7 code freeze is on Feb 21st. >> >> All major changes should be committed approximately 1 week before the code >> freeze to ensure adequate testing. Please do your part to keep the tree >> stable in the days leading up to the