similar to: [LLVMdev] 3.2 Release Branching T-11 hours and counting

I can't find any release_32 branch at http://llvm.org/git/llvm.git or http://llvm.org/git/clang.git. /Patrik Hägglund -----Original Message----- From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] On Behalf Of Pawel Wodnicki Sent: den 12 november 2012 07:03 To: llvmdev; cfe-dev at cs.uiuc.edu Subject: [LLVMdev] 3.2 Release has branched :T+2 hours We have branched

We have branched for the 3.2 release! Some "sticky reminders": You can get all of the 3.2 code from the appropriate .../branches/release_32/ You can track state of the 3.2 release through so called "Umbrella bug" : http://llvm.org/bugs/show_bug.cgi?id=13893 Hopefully it will not "rain bugs" on us and we will not need it that much! After branching all patches

All subsystems are GO for the branching of the 3.2 release. And we are branching now. Pawel

Hello, B-Day Only 11 days left till we branch for the 3.2 release! However, considering that the dev meeting takes place next week there is not much time left for any significant changes to be incorporated into the 3.2 release. From my experience this is the best time to review all the enhancements, fixes and changes rather then try to get that patch checked-in at the last moment. We have

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

Alright, can you please pull in r169280? On Tue, Dec 4, 2012 at 12:56 PM, Pawel Wodnicki <root at 32bitmicro.com> wrote: > On 12/4/2012 10:14 AM, Justin Holewinski wrote: > > What is the procedure for updating the release notes? I've been > committing > > changes to the trunk version, should I be editing them elsewhere? Or > will > > the trunk version be

On 12/4/2012 10:14 AM, Justin Holewinski wrote: > What is the procedure for updating the release notes? I've been committing > changes to the trunk version, should I be editing them elsewhere? Or will > the trunk version be merged in? The exact procedure is not spelled out but I think the easiest would be to merge relevant "ReleaseNotes.html" changes from the trunk,

What is the procedure for updating the release notes? I've been committing changes to the trunk version, should I be editing them elsewhere? Or will the trunk version be merged in? On Mon, Dec 3, 2012 at 4:12 PM, 32bitmicro <root at 32bitmicro.com> wrote: > Hi, > > > Are we going to have a mingw release this time? > > As far as I know there is no change from 3.1

Hi, > Are we going to have a mingw release this time? As far as I know there is no change from 3.1 and Mignw is considered experimental. Incidentally RC2 mingw32 binaries have been uploaded and are available for download and testing. http://llvm.org/pre-releases/3.2/rc2/clang+llvm-3.2rc2-i386-mingw32-EXPERIMENTAL.tar.gz Pawel > > > On Mon, Dec 3, 2012 at 2:54 PM, 32bitmicro

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

Approved. Sorry for the delay. On Mon, Dec 3, 2012 at 8:27 PM, 32bitmicro <root at 32bitmicro.com> wrote: > > > 32bitmicro <root at 32bitmicro.com> writes: > >> - Release Candidate 3 (RC3) > >> > >> RC3 will be created on Wednesday Dec 5th 10 p.m. PST. Please let me > >> know if there are any patches for release stopping issues that

Hello, - State of the 3.2 release Release is progressing as scheduled, RC2 has been created and is being tested. RC2 sources and binaries can be downloaded from: http://llvm.org/pre-releases/3.2/rc2/ - Release notes and documentation With RC2 the 3.2 release has reached the point where it is feature complete and we can turn the attention to updating documentation, especially the release

Are we going to have a mingw release this time? On Mon, Dec 3, 2012 at 2:54 PM, 32bitmicro <root at 32bitmicro.com> wrote: > Hello, > > - State of the 3.2 release > > Release is progressing as scheduled, RC2 has > been created and is being tested. RC2 sources > and binaries can be downloaded from: > > http://llvm.org/pre-releases/3.2/rc2/ > > > -

> 32bitmicro <root at 32bitmicro.com> writes: >> - Release Candidate 3 (RC3) >> >> RC3 will be created on Wednesday Dec 5th 10 p.m. PST. Please let me >> know if there are any patches for release stopping issues that should >> be included in the RC3. > > Is the fix for 14465 important enough for the 3.2 release? It's an ICE > that I hit in RC1

On Nov 27, 2012, at 7:35 PM, Pawel Wodnicki <root at 32bitmicro.com> wrote: > 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

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*

Should be there. Please let me know if there are any problems with them On Wed, Nov 14, 2012 at 9:19 PM, Anton Korobeynikov <anton at korobeynikov.info> wrote: >> I can't find any release_32 branch at http://llvm.org/git/llvm.git or http://llvm.org/git/clang.git. > Unfortunately, this requires manual grafting, since git-svn does > really bad job here. > > I'm going

On Nov 13, 2012, at 11:16 AM, Pawel Wodnicki <pawel at 32bitmicro.com> wrote: > Bill, > >> Hi Pawel, >> >> Could you branch polly as well for the 3.2 release? We will need to contact the 'polly' guys to figure out how best to add it to the release (testing, etc.). > > Sure. > > But I do not know much about polly so 'polly' guys please

> I can't find any release_32 branch at http://llvm.org/git/llvm.git or http://llvm.org/git/clang.git. Unfortunately, this requires manual grafting, since git-svn does really bad job here. I'm going to work on this tonight. -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint Petersburg State University

On Sat, Nov 17, 2012 at 7:40 PM, Pawel Wodnicki <pawel at 32bitmicro.com>wrote: > On 11/17/2012 6:35 PM, Chris Lattner wrote: > > > > On Nov 17, 2012, at 9:57 AM, Nadav Rotem <nrotem at apple.com> wrote: > > > >> I think that the code owner process is becoming complicated and I am > not sure if it serves Chris's original intent. I don't think