similar to: [LLVMdev] [3.0 Release] Phase 1 Bug Fixing

The LLVM 2.8 branches have been created! We will be conducting several rounds of testing of this branch during September. See http://llvm.org/ for a tentative schedule. What this means for you As I mentioned in a previous e-mail, the branch is still open for code submissions. However there are a few rules that we need to adhere to: No new features are allowed, no matter how trivial they may be.

On Fri, Mar 25, 2011 at 15:07, Bill Wendling <wendling at apple.com> wrote: > Hi all, > > Well! we had a rather fruitful phase 1 testing round. Several issues were > addressed. After a bit of a delay, we are ready for phase 2 testing. > > This phase is to make sure that no patches submitted to fix problems and > complete features in phase 1 caused further difficulties.

Hi all, Well! we had a rather fruitful phase 1 testing round. Several issues were addressed. After a bit of a delay, we are ready for phase 2 testing. This phase is to make sure that no patches submitted to fix problems and complete features in phase 1 caused further difficulties. Please download the sources, compile them, and then compile as much as you can with both clang and llvm-gcc.

Not yet. That is, I don't think any have been filed at all for 3.0. I don't know whether to be happy or worried. :-) Any that are regressions should be marked with the 'regression' keyword and be a release blocker. -bw On Oct 20, 2011, at 8:40 AM, Jim Grosbach wrote: > Hi Bill, > > Do we have a list of which PRs have been filed that are considered release blockers?

Hi LLVM-cateers, The first phase of testing is nearing completion. (Actually, it's pretty much done.) You can find binaries here as well as the source code if you want to compile your own binaries: http://llvm.org/pre-releases/3.3/rc1/ We also have several bugs which have been reported. The umbrella bug report is here: http://llvm.org/bugs/show_bug.cgi?id=15999 Now we need your help!

Hi David, Yes. It was the main reason why I decided to do an RC3. :-) -bw On Mar 28, 2011, at 10:41 AM, David Terei wrote: > Hi Bill, > > Is the fix for Bug 9561 included? (http://llvm.org/bugs/show_bug.cgi?id=9561) > > Cheers, > David. > > On 26 March 2011 18:38, Bill Wendling <wendling at apple.com> wrote: >> Hi all, >> >> The good news:

On Mon, Mar 28, 2011 at 03:07:25PM -0700, Bill Wendling wrote: > Hi David, > > Yes. It was the main reason why I decided to do an RC3. :-) > > -bw Bill, Any chance we can squeeze http://llvm.org/bugs/show_bug.cgi?id=9571#c13 into llvm-gcc-4.2-2.9 for the final llvm-gcc release? Jack > > On Mar 28, 2011, at 10:41 AM, David Terei wrote: > > > Hi

Akira, > Pawel, > > Is it still not too late to merge these patches? > > r168471 > r168460 > r168458 > r168456 > r168455 > r168453 > r168450 > r168448 > > These patches fix a bug in mips backend's GOT implementation and add > support for big-GOT relocations. That's quite a list of patches! To get them into the 3.2 release you would first

Hi Bill, Is the fix for Bug 9561 included? (http://llvm.org/bugs/show_bug.cgi?id=9561) Cheers, David. On 26 March 2011 18:38, Bill Wendling <wendling at apple.com> wrote: > Hi all, > > The good news: RC2 testing was successful in that it uncovered a bad regression from 2.8 (which existed in top-of-tree). It also showed that there was an unincorporated fix that needed to go into

Pawel, Is it still not too late to merge these patches? r168471 r168460 r168458 r168456 r168455 r168453 r168450 r168448 These patches fix a bug in mips backend's GOT implementation and add support for big-GOT relocations. Thank you. On Tue, Nov 27, 2012 at 7:35 PM, Pawel Wodnicki <root at 32bitmicro.com> wrote: > Hello, > > Just a quick reminder that the November 29th

Hi Bill, Do we have a list of which PRs have been filed that are considered release blockers? -Jim On Oct 17, 2011, at 4:33 PM, Bill Wendling wrote: > Hi all, > > Testing for LLVM 3.0 release candidate 1 is now under way! We will soon have binaries available for you to download and try. Those who would like to compile things and try them out for themselves can grab the source

Hi all, Testing for LLVM 3.0 release candidate 1 is now under way! We will soon have binaries available for you to download and try. Those who would like to compile things and try them out for themselves can grab the source tarballs here: http://llvm.org/pre-releases/3.0/ A Word About Patches I neglected to send out instructions on how to get patches into the LLVM 3.0 branch. All patches must

It's that time again! (Well, it was that time yesterday, but I made a mistake.) The LLVM 2.9 release is now underway! 2.9 Will Be The Last llvm-gcc Release! That's right! It's the end of an era. The llvm-gcc front-end has served us very well over the years, but with the advent of Clang and DragonEgg it is starting to suffer from bit rot. Starting with the 3.0 release, Clang will be

Hi Developers, This is to clarify which patches may be merged into the 3.5 branch. * All doc changes may go in. In fact, you’re encouraged to update the branch's ReleaseNotes.rst file! :-) * All non-documentation patches should first receive approval from the appropriate code maintainer. (A blanket approval is acceptable for the first phase of testing.) * If your patch fixes a major bug,

Hi all, We branched for the 3.1 release! (Yay!) If there are any fixes which you think should go into the release, please contact the code owners (http://llvm.org/docs/DeveloperPolicy.html#owners) so that they can approve the patches. No patches will be accepted into the 3.1 release without prior approval! This should be a great release! :-) -bw

Hi all, The good news: RC2 testing was successful in that it uncovered a bad regression from 2.8 (which existed in top-of-tree). It also showed that there was an unincorporated fix that needed to go into the clang branch. The bad news: I'm truncating the RC2 testing phase and announcing the RC3 testing phase. Hopefully, because we caught the bugs in time this phase won't impact the

We have officially branched for the LLVM 3.4 release!! This means that we are now in the middle of a feature freeze. Here’s what will happen over the next several weeks: * Nov 19 - Nov 24: This is Phase I testing. During this time, you are still able to add code to the release branch. However, you will need to have the approval of the code owner before committing it. We are mostly looking for

On Apr 3, 2013, at 11:30 AM, Tom Stellard <tom at stellard.net> wrote: > On Tue, Apr 02, 2013 at 05:47:33PM -0700, Bill Wendling wrote: >> On Apr 2, 2013, at 2:10 PM, Tom Stellard <tom at stellard.net> wrote: >> >>> On Tue, Apr 02, 2013 at 11:52:09AM -0700, Bill Wendling wrote: >>>> On Apr 2, 2013, at 9:51 AM, Tom Stellard <tom at

how to get this branch? still svn co http://llvm.org/svn/llvm-project/llvm/trunk llvm? Thank you. On Tue, Apr 17, 2012 at 2:16 PM, Bill Wendling <wendling at apple.com> wrote: > Hi all, > > We branched for the 3.1 release! (Yay!) > > If there are any fixes which you think should go into the release, please > contact the code owners

Hello, Just a quick reminder that the November 29th (10p.m. PST) is the end of Phase 1 testing and Release Candidate 2 (RC2) deadline. After RC2 deadline, LLVM-Clang 3.2 release will be considered feature complete and no new functionality can be added. With 2 days left please use following guidelines when initiating request for patches before RC2 deadline. I will be happy to merge *approved*