similar to: [LLVMdev] 2.7 Release Status

On 03/30/2010 09:15 PM, Tanya Lattner wrote: > > Thanks for testing the release! > >> Tests were run on x86-64, Debian unstable, Linux 2.6.33, gcc 4.4.3, >> 64-bit. I built srcdir == objdir, I have built llvm and clang myself, >> and used the binaries for llvm-gcc. >> >> 1. llvm-gcc 2.7 vs 2.6 >> compared to my results from Aug 31 2009, ignoring CBE

On Mar 24, 2010, at 2:47 PM, Török Edwin wrote: > On 03/17/2010 10:12 PM, Tanya Lattner wrote: >> The 2.7 binaries are available for testing: >> http://llvm.org/pre-releases/2.7/pre-release1/ >> >> You will also find the source tarballs there as well. >> >> We rely on the community to help make our releases great, so please help >> test 2.7 if you

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).

On 03/30/2010 09:21 PM, Török Edwin wrote: > On 03/30/2010 09:15 PM, Tanya Lattner wrote: >> Thanks for testing the release! >> >>> Tests were run on x86-64, Debian unstable, Linux 2.6.33, gcc 4.4.3, >>> 64-bit. I built srcdir == objdir, I have built llvm and clang myself, >>> and used the binaries for llvm-gcc. >>> >>> 1. llvm-gcc 2.7 vs

On 03/17/2010 10:12 PM, Tanya Lattner wrote: > The 2.7 binaries are available for testing: > http://llvm.org/pre-releases/2.7/pre-release1/ > > You will also find the source tarballs there as well. > > We rely on the community to help make our releases great, so please help > test 2.7 if you can. Please follow these instructions to test 2.7: > > /To test llvm-gcc:/

On Mar 30, 2010, at 3:45 PM, David Greene wrote: > On Tuesday 30 March 2010 16:09:03 Tanya Lattner wrote: > >> Please take a look at all release blockers: >> http://llvm.org/bugs/show_bug.cgi?id=6586 > > 5893 is not release-critical according to Doug. > Will take care of this. > 6640 appears to be a test system problem with a patch available (one of the >

Bah, headers still broken, sending to list this time: On Sat, Mar 13, 2010 at 6:30 PM, OvermindDL1 <overminddl1 at gmail.com> wrote: > On Sat, Mar 13, 2010 at 11:10 AM, Tanya Lattner <lattner at apple.com> wrote: >> >> On Mar 13, 2010, at 7:01 AM, R P Herrold wrote: >> >>> On Sat, 13 Mar 2010, Tanya Lattner wrote: >>> >>>>> I

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 Tue, 30 Mar 2010 14:09:03 -0700, Tanya Lattner <xzss at ____.com> wrote: > 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

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

These are all fixed. Sorry for the mistake.. I blame lack of sleep ;) -Tanya On Apr 27, 2010, at 8:58 AM, Pitr wrote: > Trying to download Release 2.7 i get the response: > > The requested URL /releases/2.7/clang-2.7.tar.gz was not found on this server. > The requested URL /releases/2.7/clang-2.7-amd64-freebsd8.tar.gz was > not found on this server. > The requested URL

On Fri, Feb 12, 2010 at 5:48 PM, Daniel Dunbar <daniel at zuster.org> wrote: > 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

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 Mar 30, 2010, at 4:04 PM, David Greene wrote: > On Tuesday 30 March 2010 17:45:16 David Greene wrote: >> On Tuesday 30 March 2010 16:09:03 Tanya Lattner wrote: >>> Please take a look at all release blockers: >>> http://llvm.org/bugs/show_bug.cgi?id=6586 >> >> 5893 is not release-critical according to Doug. >> >> 6640 appears to be a test

Ok, I have good news! Thanks for the help! On Jun 2, 2008, at 11:11 PM, Tanya Lattner wrote: > Many of you are probably wondering about the status of the 2.3 > release. Unfortunately, this release has been very difficult and > the list of regressions very high. The list has finally dwindled > down to the following regressions: > > Linux/x86: >

On Tuesday 30 March 2010 16:09:03 Tanya Lattner wrote: > Please take a look at all release blockers: > http://llvm.org/bugs/show_bug.cgi?id=6586 5893 is not release-critical according to Doug. 6640 appears to be a test system problem with a patch available (one of the ones you're working on?) Which bugs do you have patches for? I don't want to start looking at something if

The 2.7 pre-release2 is available for testing: http://llvm.org/pre-releases/2.7/pre-release2/ Please complete all testing by April 23rd EOD. We are shortening this testing period a bit to get the release out soon since its been delayed so far. The release team has done our qualifications and we think its of high quality and ready to go. As this is the last pre-release, we only accept fixes for

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

Hi LLVM Friends, Fans, Followers and Fanatics, LLVM 2.7 is live! You can download it here: http://llvm.org/releases/ and read about it here: http://llvm.org/releases/2.7/docs/ReleaseNotes.html This release includes approximately 6 months of development that provide major enhancements and new features over the LLVM 2.6 release. This includes significantly better generated code, improvements to

All, Thanks for those who have been helping fix regressions and warnings. Your hard work is appreciated and you have made great progress! Thank you again. The release is getting close. As a reminder, this is the master bug: http://llvm.org/bugs/show_bug.cgi?id=6586 In particular, we have one bug that needs attention: http://llvm.org/bugs/show_bug.cgi?id=6660 These are regressions in the