similar to: [LLVMdev] [3.5 Release] Tentative Schedule

On Feb 19, 2011, at 8:05 PM, Yuri wrote: > On 02/19/2011 14:52, Yuri wrote: >> Will MC path for JNI be included in 2.9? >> > > Sorry. I meant: Will MC path for JIT be included in 2.9? While it would be nice, it doesn't seem like anyone is working on it at the moment. -Chris

On 02/19/2011 14:52, Yuri wrote: > Will MC path for JNI be included in 2.9? > Sorry. I meant: Will MC path for JIT be included in 2.9?

Hi, I would like to begin the 3.4.2 release process for LLVM. There have been two issues identified in 3.4.1, which there is interest in having fixed in a 3.4.x release: 1. Build failure with gcc 4.9 (This is not a regression, 3.4 also fails to build with gcc 4.9). 2. Accidental change of libLLVM's DT_SONAME from libLLVM-3.4 libLLVM-3.4.1.so I will also accept any other bug-fixes that

On Feb 24, 2011, at 4:05 AM, Jan Sjodin wrote: > On Feb 19, 2011, at 8:05 PM, Yuri wrote: >> >>> On 02/19/2011 14:52, Yuri wrote: >>>> Will MC path for JNI be included in 2.9? >>>> >>> >>> Sorry. I meant: Will MC path for JIT be included in 2.9? >> >> While it would be nice, it doesn't seem like anyone is working on

----- Original Message ---- > From: Chris Lattner <clattner at apple.com> > To: Yuri <yuri at rawbw.com> > Cc: llvmdev at cs.uiuc.edu > Sent: Sun, February 20, 2011 3:26:35 AM > Subject: Re: [LLVMdev] Announcing: LLVM 2.9 Tentative Release Schedule > > > On Feb 19, 2011, at 8:05 PM, Yuri wrote: > > > On 02/19/2011 14:52, Yuri wrote: > >>

I think we have located the revision which fixes this regression: r206094 (or commit 6bb00df in llvm-mirror on GitHub). I have attached a patch which can be applied to the current release_34 branch (tested against the release_34 branch in llvm-mirror). With this patch the attached reg-alloc-test.ll file doesn't fail with the "LLVM ERROR: ran out of registers during register

Hello LLVMers! Amazingly, it's been 4 months since the release of LLVM 2.8. And so much has changed since then! April will be six months since the previous release, so it's time to start thinking about LLVM 2.9! Here is a tentative schedule for the release (and, of course, our schedules never slip): March 6th - Branch for release. March 7th-14th - Testing Phase 1

The six month release time table is coming up soon, which means that it's ready to start planning for the next release! Here is the tentative schedule: October 14th – Create 3.0 Branch October 16th – First Round of Testing Starts October 23rd – First Round of Testing Ends / Bug Fixing Begins October 30th – Second Round of Testing Starts November 6th – Second Round of Testing Ends / Bug

Will MC path for JNI be included in 2.9? Yuri

On Sun, Feb 20, 2011 at 11:26 AM, Chris Lattner <clattner at apple.com> wrote: > > On Feb 19, 2011, at 8:05 PM, Yuri wrote: > > > On 02/19/2011 14:52, Yuri wrote: > >> Will MC path for JNI be included in 2.9? > >> > > > > Sorry. I meant: Will MC path for JIT be included in 2.9? > > While it would be nice, it doesn't seem like anyone is

> We will be branching for the 3.3 release one Monday, May 6th at 5PM PDT (Tuesday, May 7th 12:00 midnight GMT). I noticed there is a 3.3 branch in svn, but not in git. Anton, are you still the one managing the git repos? Also, I just added a note to the release info on trunk before noticing we had branched. I was about to port it over, but then noticed that

I will add release branches soon. I just decided to wait a bit in case of some emergency re-creation of branches, etc. On Tue, May 7, 2013 at 4:51 PM, Rafael Espíndola <rafael.espindola at gmail.com> wrote: >> We will be branching for the 3.3 release one Monday, May 6th at 5PM PDT (Tuesday, May 7th 12:00 midnight GMT). > > I noticed there is a 3.3 branch in svn, but not in git.

Could we aim for mid/late January? I'd like our target triple problems to be sorted out for LLVM 3.6 if I can and early-January doesn't leave many working days to get that finished. Especially given that many people take some holiday around Christmas and New Year. > -----Original Message----- > From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] > On

Hi LLVM-ites! I wanted to give you a "heads up" on the 3.3 release schedule. Branching [Important] --------------------- We will be branching for the 3.3 release one Monday, May 6th at 5PM PDT (Tuesday, May 7th 12:00 midnight GMT). Tentative Schedule ------------------ The remaining schedule will follow the normal test - bug fix - repeat process: May 6th - 11th --- Phase I

Hi, Here is schedule for upcoming stable releases: 3.5.2 - This will be the last 3.5.x release. There was a critical bug fix that did not make it into 3.5.1, which made it necessary to do 3.5.2. I will accept other fixes, but the merge window will be very short: March 16 - Tag 3.5.2-rc1 and begin testsing March 25 - 3.5.2 release (If no regressions found during testing). 3.6.1 - Bug fixes

Hi Tom, On 9 Jun 2014, at 15:36, Tom Stellard <tom at stellard.net> wrote: > Unfortunately, it is too late to get this into 3.4.2. With the 3.5 > release coming soon, I wasn't planning on doing another 3.4 point > release. We are likely to keep the llvm 3.4 port in FreeBSD for a while after 3.5 is released. We've only removed the llvm 3.1 port a couple of months ago. A

i Don't know if others have raised this issue, but I'm seeing *a lot* of llvm-dev emails and cfe emails landing in my spam folder in gmail. Are other people having this problem? On Mon, May 12, 2014 at 11:57 AM, Tom Stellard <tom at stellard.net> wrote: > Hi, > > I would like to begin the 3.4.2 release process for LLVM. There have > been two issues identified in

Hi Robert, Can you ping the code owners about these patches. It might be good to write a separate email per code owner and cc the appropriate -commits list. Thanks, Tom On Wed, Apr 02, 2014 at 06:16:44PM +0400, Robert Khasanov wrote: > Hi Tom, > > I would like to nominate the following patches to be backported to 3.4.1 > > Clang: > 1. r204742 - Zinovy Nis <zinovy.nis at

Hi, The number of stable patches has slowed down in the last few weeks, and we are approaching the halfway point between 3.3 and 3.4, so I think now is a good time to start planning for the 3.3.1 release. Here is the tentative schedule: September 3: 3.3.1-rc1 - This won't actually be a 'real' Release Candidate. The purpose of rc1 will be to update and test the release scripts

Hi, We are now about halfway between the 3.4 and 3.5 releases, and I would like to start preparing for a 3.4.1 release. Here is my proposed release schedule: Mar 26 - April 9: Identify and backport additional bug fixes to the 3.4 branch. April 9 - April 18: Testing Phase April 18: 3.4.1 Release How you can help: - If you have any bug fixes you think should be included to 3.4.1, send me an