similar to: [LLVMdev] Reminder 3.5.2 merge deadline is Monday, Mar 16 - Testers needed

I've uploaded clang+llvm-3.5.2-rc1-mips-linux-gnu.tar.xz and clang+llvm-3.5.2-rc1-mips-linux-gnu.tar.xz started testing them. > -----Original Message----- > From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] > On Behalf Of Daniel Sanders > Sent: 16 March 2015 15:36 > To: Tom Stellard; llvmdev at cs.uiuc.edu > Subject: Re: [LLVMdev] Reminder 3.5.2

On Mon, Mar 16, 2015 at 01:51:32PM -0700, Tom Stellard wrote: > On Thu, Mar 12, 2015 at 06:04:35PM -0400, Tom Stellard wrote: > > Hi, > > > > Just a reminder that testing for 3.5.2 will begin on Monday, Mar 16. If > > you have any patches you want merged please send an email to the > > relevant commits list and cc me and the code owner. If you have already >

Hi, Just a reminder that I'm planning to start the 3.5.1 release cycle on Wednesday. If you have any patches you want included in 3.5.1 please let me know. There haven't been many stable patches so far, so I may be willing to extend the deadline if some people have fixes, but won't be able to get to them before Wednesday. Also, if you are interested in helping to test the 3.5.1

Hi, Here is a proposed release schedule for 3.9.1: Nov 21, 2016: Deadline for nominating change to merge to the 3.9 branch Nov 29, 2016: -rc1 Dec 5, 2015: 3.9.1 Release As a reminder, if you would like to request a patch be merged to the 3.9 branch, file a bug at www.llvm.org/bugs with the subject "Merge rxxxxx into the 3.9 branch." and add

Hi, I have just tagged 3.6.2-rc1, so testing can begin. We can always use more testers, so if you are interested in testing, let me know. -Tom

Hi, I have tagged the 3.6.1-rc1 so testing can begin. We can always use more testers, so if you are interested in helping, let me know. Instructions for validating an LLVM release can be found here: http://llvm.org/docs/ReleaseProcess.html Reminder: We are using 3.6.0 as our baseline for regression testing. Thanks, Tom

Hi, It's about time to start thinking about the 3.8.1 release. Here is a proposed release schedule: May 25 - Deadline to request a change be merged to the 3.8 branch. June 1 - Deadline to merge changes to the 3.8 branch. June 1 - 3.8.1-rc1 June 8 - 3.8.1-rc2 (if necessary) June 15 - 3.8.1 Release If you want a patch included in the 3.8.1 release, send an email to llvm-commits with the

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

Hi, I had a quick look at that link and it seems to be a linker internal error. Presumably we're triggering a bug in the system toolchain. FWIW, my mipsel build on a Debian Jessie machine (binutils 2.24.90.20141023-1) successfully completed test-release.sh. I'm currently running the tests. Here's the relevant bit of the log from your link: cd

What, the deadline is tomorrow?!? The deadline for proposals snuck up on me, and I'm sure many of you forgot as well. Therefore, I am extending the deadline. I have received some great talk proposals, so keep them coming. However, I have very few tutorials, BoFs, posters, or lightening talk proposals. So please, get those proposals in and lets make this year the best developer meeting yet!

Hi All, Just a quick reminder that Euro LLVM 2015 will be on April 13th-14th in London at Goldsmiths college. We have now sold over half the tickets and so if you have not done so, register at: http://www.eventbrite.com/e/eurollvm-2015-tickets-15350278095 Also the deadline for submissions is nearly upon us. Deadline: February 16th 2015 https://easychair.org/conferences/?conf=eurollvm2015

Hi, We don't normally do X.Y.2 releases, but there has been some interest in getting a 5.0.2 release out with the Spectre mitigations included, so I am proposing the following schedule for a 5.0.2 release: LLVM 5.0.2 -rc1 Mon Mar 19 -final Mon Mar 26 To keep things easy for testers, 5.0.2 will be for Spectre related fixes only and won't be opened up for general bugs. And here is

> Test suite is green but I'm seeing two libc++ test failures when running check-all. What tests are failing? On Fri, Jun 10, 2016 at 5:13 PM, Nikola Smiljanic via cfe-dev < cfe-dev at lists.llvm.org> wrote: > Uploaded Fedora and openSUSE binaries. Test suite is green but I'm seeing > two libc++ test failures when running check-all. I'm pretty sure these were >

Will the PR's marked as blockers of PR36649 be merged in or do we need to do something specific? On Thu, Apr 26, 2018 at 12:28 AM, Tom Stellard via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Hi, > > I've just tagged the 6.0.1-rc1 release. Testers may begin testing and > uploading > binaries. Also, any tester who has not tested 5.0.2-rc1 and would like to >

On Wed, Jun 24, 2015 at 10:11:26AM -0700, Hans Wennborg wrote: > On Tue, Jun 23, 2015 at 5:17 PM, Tom Stellard <tom at stellard.net> wrote: > > I have just tagged 3.6.2-rc1, so testing can begin. We can always use > > more testers, so if you are interested in testing, let me know. > > I had trouble building on Windows, getting errors in > AMDGPUGenSubtargetInfo.inc

Hi, I've just tagged the 6.0.1-rc1 release. Testers may begin testing and uploading binaries. Also, any tester who has not tested 5.0.2-rc1 and would like to do so please try to do this before Friday, because I would like to tag 5.0.2-final then. As a reminder to users and developers, May 18 is the deadline for submitting merge requests for 6.0.1, so there is still time to get bug fixes

No regressions this time. Fedora and OpenSUSE binaries uploaded. On Sat, Apr 26, 2014 at 12:47 PM, Tom Stellard <tom at stellard.net> wrote: > Dropping llvmdev and cc'ing testers directly, so this email > won't be held in moderation for having too many recipients. > > I like having tester discussions on list, so it would probably > be best to reply to the original

Daniel, Note the openmp library only has cmake build machinery preventing autoconf-based builds. Jack On Tue, Jun 23, 2015 at 10:18 AM, Daniel Sanders <Daniel.Sanders at imgtec.com> wrote: > Hi, > > I'll do Mips as usual. Are we going to do an autoconf-based build for LLVM 3.7? If so, I might try Mips64 packages too. > >> -----Original

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, I know a lot of people were busy with the dev-meeting last week, so I've decided to continue to accept stable patches until November 9. I would still like to keep the original schedule of an -rc1 release on November 10, so if there are any newly submitted patches that take more than a few days to get approved, they will probably end up going into llvm 3.7.2. I am currently working