[lldb-dev] Win64 lldb build broken, llvm::call_once and _mm_mfence

The Win64 lldb build seems broken (at 294367). I ran into this when trying to build the weekly snapshot (http://www.llvm.org/builds/) which includes LLDB these days. I suspect this might be related to Kamil's changes a few days ago. I see Pavel committed something to fix Darwin afterwards. Zach,

Re: [lldb-dev] Win64 lldb build broken, llvm::call_once and _mm_mfence

I only ran into problems on Win64. I guess your bot is doing a 32-bit build. On Wed, Feb 8, 2017 at 1:41 PM, Pavel Labath wrote: > My fix was just correcting places Kamil forgot to update (or updated > over-excessively). It does not touch the root problem. > > That said, our windows bot >

[lldb-dev] [4.0.0 Release] Release Candidate 2 has been tagged

Hello testers, 4.0.0-rc2 was just tagged from the branch at r294535. There are still open relase blocking bugs and merge requests, so this will not be the last release candidate, but we've had a lot of merges since the last one, and I'd like to see what the testing looks like. The test-release.s

[lldb-dev] [4.0.0] Release notes nag email

Dear everyone, It's time for the six-monthly release notes nag email in preparation for the upcoming release. As usual, the release notes are almost empty. Please help fill them with the work you've done in the past six months. The notes do get read by a lot of people, so I think they're worth so

Re: [lldb-dev] [4.0.0 Release] Release Candidate 2 has been tagged

On Wed, Feb 8, 2017 at 4:33 PM, Hans Wennborg wrote: > Hello testers, > > 4.0.0-rc2 was just tagged from the branch at r294535. > > There are still open relase blocking bugs and merge requests, so this > will not be the last release candidate, but we've had a lot of merges > since the last one, an

Re: [lldb-dev] Win64 lldb build broken, llvm::call_once and _mm_mfence

I'm happy as long as it builds :-) On Wed, Feb 8, 2017 at 2:26 PM, Zachary Turner wrote: > Should we do that now, as a way to fix this issue, or should we try to get > another fix in first so we have more time to think about using std > call_once? > > On Wed, Feb 8, 2017 at 2:19 PM Reid Kleckner

Re: [lldb-dev] [Release-testers] [4.0.0 Release] Release Candidate 2 has been tagged

On Thu, Feb 9, 2017 at 2:23 PM, Dimitry Andric wrote: > On 9 Feb 2017, at 01:33, Hans Wennborg via Release-testers > wrote: >> >> 4.0.0-rc2 was just tagged from the branch at r294535. > > Building on FreeBSD 10 at least didn't crash this time, and lld built just > fine. :) I uploaded the follo

Re: [lldb-dev] [llvm-dev] [cfe-dev] [Release-testers] [4.0.0 Release] Release Candidate 2 has been tagged

On Fri, Feb 10, 2017 at 3:56 AM, Renato Golin wrote: > On 10 February 2017 at 11:38, Pavel Labath via llvm-dev > wrote: >> All I can say is these tests did not exist in 3.9, so I wouldn't call >> this a regression. (Well... technically, a similar test existed, but >> it was run by a different tes

[lldb-dev] [4.0.0 Release] Release Candidate 1 source and binaries available

Source, binaries and docs for LLVM-4.0.0-rc2 are now available at http://www.llvm.org/pre-releases/4.0.0/#rc2 Please try it out, run tests, build your favourite projects and file bugs about anything that needs to be fixed, marking them as blockers of http://llvm.org/pr31622. Many things have been

[lldb-dev] [4.0.0 Release] Release Candidate 2 source and binaries available

Apologies, the subject should say Release Candidate *2* is now availalble. On Tue, Feb 14, 2017 at 11:56 AM, Hans Wennborg wrote: > Source, binaries and docs for LLVM-4.0.0-rc2 are now available at > http://www.llvm.org/pre-releases/4.0.0/#rc2 > > Please try it out, run tests, build your favourit

[lldb-dev] [4.0.0 Release] Current status

According to the schedule on llvm.org, we should have tagged 'final' yesterday, so the release is now officially a little behind schedule. There are currently seven blockers (llvm.org/pr31622). Several of them have patches. If you can help reviewing them, please do so. - PR30256: Assert in llvm::

[lldb-dev] [4.0.0 Release] Release Candidate 3 has been tagged

Hello testers, 4.0.0-rc3 was just tagged from the branch at r296762. This is a release candidate in the real sense: if no major issues show up with this one, it is the version that will be released. Please let me know if you find any issues, including in release notes or documentation, which wil

Re: [lldb-dev] [4.0.0 Release] Release Candidate 3 has been tagged

On Thu, Mar 2, 2017 at 11:47 AM, Hans Wennborg wrote: > 4.0.0-rc3 was just tagged from the branch at r296762. > > This is a release candidate in the real sense: if no major issues show > up with this one, it is the version that will be released. > > Please let me know if you find any issues, inclu

[lldb-dev] [4.0.0 Release] Release Candidate 3 source and binaries available

Source, binaries and docs for LLVM-4.0.0-rc3 are now available at http://www.llvm.org/pre-releases/4.0.0/#rc3 Please file any issues as blockers of http://llvm.org/pr31622. Hopefully we can get to the final release soon. Cheers, Hans ___ lldb-dev maili

[lldb-dev] [4.0.0 Release] Release Candidate 4 has been tagged

Dear testers, 4.0.0-rc4 was just tagged from the branch at r297204. This is very similar to rc3, with additional fixes for PR32142 and PR32153. Please take it for a quick spin. If nothing new comes up, this is what the final release will look like. Thanks, Hans _

Re: [lldb-dev] [4.0.0 Release] Release Candidate 4 has been tagged

On Tue, Mar 7, 2017 at 1:15 PM, Hans Wennborg wrote: > Dear testers, > > 4.0.0-rc4 was just tagged from the branch at r297204. > > This is very similar to rc3, with additional fixes for PR32142 and PR32153. > > Please take it for a quick spin. If nothing new comes up, this is what > the final rele

[lldb-dev] [4.0.0 Release] 'final' has been tagged

Dear testers, The final version of 4.0.0 was just tagged (from the 4.0 branch at r297335). There were no changes after rc4. Please build the final binaries and upload to the sftp. For others following along: this means 4.0.0 is complete, but it will take a few days to get the tarballs ready and

Re: [lldb-dev] [4.0.0 Release] 'final' has been tagged

On Wed, Mar 8, 2017 at 4:52 PM, Hans Wennborg wrote: > Dear testers, > > The final version of 4.0.0 was just tagged (from the 4.0 branch at > r297335). There were no changes after rc4. > > Please build the final binaries and upload to the sftp. Windows: $ sha1sum *LLVM-4.0.0-win*.exe b48a3dab37e

Re: [lldb-dev] [4.0.0 Release] 'final' has been tagged

On Thu, Mar 9, 2017 at 2:28 PM, Hans Wennborg wrote: > On Wed, Mar 8, 2017 at 4:52 PM, Hans Wennborg wrote: >> Dear testers, >> >> The final version of 4.0.0 was just tagged (from the 4.0 branch at >> r297335). There were no changes after rc4. >> >> Please build the final binaries and upload to t

Re: [lldb-dev] [llvm-dev] [cfe-dev] [4.0.0 Release] 'final' has been tagged

Hi Khem, On Fri, Mar 10, 2017 at 1:03 PM, Khem Raj via llvm-dev wrote: > On Fri, Mar 10, 2017 at 7:01 AM, Renato Golin via llvm-dev > wrote: >> ARM and AArch64 looking good, uploaded. >> > > This is not particularly related to this RC but in general with 4.0.0 > I am seeing a failure quite commo

[lldb-dev] LLVM 4.0.0 Release

It is my pleasure to announce that LLVM 4 is now available. Get it here: http://llvm.org/releases/download.html#4.0.0 LLVM is now using a new versioning scheme, increasing the major version number with each major release. Stable updates to this release will be versioned 4.0.x, and the next major

Re: [lldb-dev] [Release-testers] [4.0.0 Release] 'final' has been tagged

On Mon, Mar 13, 2017 at 10:33 AM, Simon Dardis wrote: > Hi Hans, > > Sorry for the delay. RC4 uploaded, looks ok, md5s: > > 85668cdcf53dc6de09af34e13d9a8a46 clang+llvm-4.0.0-rc4-mipsel-linux-gnu.tar.xz > 61d46cb7650fd6acf5d23f11496f2ff8 clang+llvm-4.0.0-rc4-mips-linux-gnu.tar.xz > 605f792a1b9371

Re: [lldb-dev] Python scripting in Windows LLDB

Yes, my machine doesn't have the _d.dll files. On Fri, May 19, 2017 at 1:14 PM, Vadim Chugunov wrote: > Update: looks like Python detection in CMake now requires debug binaries to > be there as well (e.g. python35_d.dll), otherwise Python support gets > disabled. I am wondering if Python the bui

Re: [lldb-dev] Python scripting in Windows LLDB

It would be better if the build fails hard if some dependency isn't available. I'll never notice a message about Python support being disabled since there's so much noise in the build anyway. On Fri, May 19, 2017 at 1:42 PM, Ted Woodward wrote: > LLDBConfig.cmake has this: > > > > if (NOT (PYTH

[lldb-dev] [5.0.0 Release] Schedule and call for testers

Hello everyone, We're about a month away from the start of the 5.0.0 release process, so it's time for the traditional schedule and call for testers email. If you'd like to help providing binaries and testing for your favourite platform, please let me know and subscribe to the release-testers mai

Re: [lldb-dev] [Openmp-dev] [5.0.0 Release] Schedule and call for testers

I don't know what the exact status of NewGVN is, but we generally do timed releases rather than feature-based releases. If it's ready before the branch point and doesn't break during the process it goes in the release, otherwise not. As far as I know it's not enabled yet, so I'm guessing it might

[lldb-dev] [5.0.0 Release] One week to the branch

Hello everyone, Here is a quick reminder that the upcoming release branch is scheduled for one week from now: Wednesday 19 July 2017. Please try to avoid disruptive changes right before the branch. The full release schedule was posted in a previous email [1] and is also available under Upcoming

[lldb-dev] [5.0.0 Release] The release branch is open; trunk is now 6.0.0

Dear everyone, The release branch was recently created from trunk at r308441 and the trunk version was subsequently incremented to 6.0.0. Release blockers are tracked by https://bugs.llvm.org/show_bug.cgi?id=33849 Please mark any bugs, old or new, that you think need to be fixed before the releas

[lldb-dev] [5.0.0 Release] Release Candidate 1 tagged

Dear testers, 5.0.0-rc1 has just been tagged. Please build, test and upload binaries to the sftp. Let me know if there are any issues. I'll upload sources, docs, and your binaries to the pre-release website once they're ready. Thanks, Hans ___ lldb-de

Re: [lldb-dev] [llvm-dev] [5.0.0 Release] Release Candidate 1 tagged

I've replied on the patch. It needs to find a reviewer. On Fri, Jul 28, 2017 at 4:16 AM, Andrew Kelley wrote: > Hans, > > Apologies for the repetition. I'm not quite familiar with the release > process. Will https://reviews.llvm.org/D35387 make it in? It has been > awaiting review for quite some

Re: [lldb-dev] [cfe-dev] [5.0.0 Release] Release Candidate 1 tagged

On Sat, Jul 29, 2017 at 4:59 AM, Dimitry Andric wrote: > On 27 Jul 2017, at 00:41, Hans Wennborg via cfe-dev > wrote: >> >> 5.0.0-rc1 has just been tagged. >> >> Please build, test and upload binaries to the sftp. Let me know if >> there are any issues. > > Built and tested rc1. Test failures o

[lldb-dev] [5.0.0 Release] Release Candidate 1 source and binaries available

Hello all, Source, binaries and docs for LLVM-5.0.0-rc1 are now available at http://prereleases.llvm.org/5.0.0/#rc1 Please try it out, run tests, builds your favourite projects and file bugs about anything that needs to be fixed (including docs!), marking them blockers of http://llvm.org/pr33849.

Re: [lldb-dev] [cfe-dev] [5.0.0 Release] Release Candidate 1 tagged

On Tue, Aug 1, 2017 at 3:01 AM, Simon Dardis wrote: > Currently I'm getting "Couldn't write to remote file > "/home/testers/uploads/clang+llvm-5.0.0-rc1-mips-linux-gnu.tar.xz": Failure", > does that account need more space? Yes, the partition is full. I've asked Anton to see if we can fix this.

Re: [lldb-dev] [cfe-dev] [5.0.0 Release] Release Candidate 1 tagged

On Tue, Aug 1, 2017 at 9:13 AM, Hans Wennborg wrote: > On Tue, Aug 1, 2017 at 3:01 AM, Simon Dardis wrote: >> Currently I'm getting "Couldn't write to remote file >> "/home/testers/uploads/clang+llvm-5.0.0-rc1-mips-linux-gnu.tar.xz": Failure", >> does that account need more space? > > Yes, the p

Re: [lldb-dev] [cfe-dev] [5.0.0 Release] Release Candidate 1 tagged

On Fri, Aug 4, 2017 at 2:33 AM, Simon Dardis wrote: > > >> -Original Message- >> From: hwennb...@google.com [mailto:hwennb...@google.com] On Behalf >> Of Hans Wennborg >> Sent: 04 August 2017 00:52 >> To: Simon Dardis >> Cc: Release-testers; llvm-dev; cfe-dev; openmp-dev (openmp- >> d...@l

Re: [lldb-dev] [Release-testers] [cfe-dev] [5.0.0 Release] Release Candidate 1 tagged

On Fri, Aug 4, 2017 at 10:39 AM, Vedant Kumar wrote: > I've uploaded the x86_64/Darwin package: > > SHA1(clang+llvm-5.0.0-rc1-x86_64-apple-darwin.tar.xz) = > 66cb113cb735b7f0d3b7eebe155969f069c8a684 > SHA256(clang+llvm-5.0.0-rc1-x86_64-apple-darwin.tar.xz) = > ca13407528536f0c4e9b5bf00115a2f3d65

Re: [lldb-dev] [cfe-dev] [5.0.0 Release] Release Candidate 1 tagged

On Wed, Aug 9, 2017 at 12:22 PM, Alex Bradbury wrote: > On 26 July 2017 at 23:41, Hans Wennborg via cfe-dev > wrote: >> Dear testers, >> >> 5.0.0-rc1 has just been tagged. >> >> Please build, test and upload binaries to the sftp. Let me know if >> there are any issues. > > On 26 July 2017 at 23:4

[lldb-dev] [5.0.0 Release] Release Candidate 2 tagged

Dear testers, 5.0.0-rc2 was just tagged. I know we still have a bunch of open release blockers, but there has been a lot of merged patches and I'd like to find out what the status is. Please build, test and upload binaries to the sftp. When uploading, make sure to use the /data/testers-uploads/

Re: [lldb-dev] [Release-testers] [5.0.0 Release] Release Candidate 2 tagged

I'm not aware of a bug filed for this, so please file one. I don't know much about the workings of test-suite myself, though. On Fri, Aug 11, 2017 at 2:54 PM, Brian Cain wrote: > Much or all of "Bitcode/simd_ops/simd_ops_*.test" (254 failures) seem to be > failing for me with SIGILL. I'm guessin

Re: [lldb-dev] [5.0.0 Release] Release Candidate 2 tagged

On Thu, Aug 10, 2017 at 7:00 PM, Hans Wennborg wrote: > Dear testers, > > 5.0.0-rc2 was just tagged. > > I know we still have a bunch of open release blockers, but there has > been a lot of merged patches and I'd like to find out what the status > is. > > Please build, test and upload binaries to

[lldb-dev] [5.0.0 Release] Release Candidate 2 source and binaries available

Hello everyone, Source, binaries and docs for LLVM-5.0.0-rc2 are now available at http://prereleases.llvm.org/5.0.0/#rc2 (I'll add more binaries as they become available.) Please try it out, run tests, builds your favourite projects and file bugs about anything that needs to be fixed (including

Re: [lldb-dev] [llvm-dev] [5.0.0 Release] Release Candidate 2 tagged

On Thu, Aug 17, 2017 at 4:03 PM, Vedant Kumar wrote: > Hi, > > There are no regressions from RC1 on Darwin. > > I've uploaded clang+llvm-5.0.0-rc2-x86_64-apple-darwin.tar.xz to > /data/testers-uploads. > > SHA 1: 8ffaf7ab44e7e7fe582dc9573aad9745ee63e186 > SHA 256: 578c18ceb6485fd2fcac329a7a5fe7e5

Re: [lldb-dev] [5.0.0 Release] Release Candidate 2 source and binaries available

lang are gone. > > I have filed PR32433 and PR32434 to address the remaining failures. > > The test-suite for mips and mipsel appears clean. > > x86_64-linux-gnu-debian8 appears clean. > > Thanks, > Simon > ____________ > From: lldb-dev [lld

[lldb-dev] [5.0.0 Release] Please write release notes

Dear everyone, We're a couple of release candidates into the process, and the release notes are not in very good shape: http://prereleases.llvm.org/5.0.0/#rc2 If you committed anything noteworthy in the last six months, or saw someone else do it, please consider adding it to the release notes. Pe

[lldb-dev] [5.0.0 Release] Please help fix the remaining blockers (2 days left!)

Hello everyone, According to the release schedule, we're supposed to be tagging 'final' on Wednesday. Unfortunately, I suspect we will be a little late. There are currently 32 open release blockers: https://bugs.llvm.org/buglist.cgi?f1=blocked&o1=equals&v1=33849&query_format=advanced&resolution=-

Re: [lldb-dev] [llvm-dev] [5.0.0 Release] Please help fix the remaining blockers (2 days left!)

On Tue, Aug 22, 2017 at 1:20 PM, Kamil Rytarowski wrote: > On 22.08.2017 01:36, Hans Wennborg via llvm-dev wrote: >> Hello everyone, >> >> According to the release schedule, we're supposed to be tagging >> 'final' on Wednesday. Unfortunately, I suspect we will be a little >> late. >> >> There are

Re: [lldb-dev] Remote debugging ARM target from x86 host

This was marked as an lldb 5.0.0 release blocker since it's a regression from 4.0.1: https://bugs.llvm.org/show_bug.cgi?id=34183 lldb-dev: Is there any interest in fixing this bug? On Fri, Aug 4, 2017 at 10:13 PM, Ramana via lldb-dev wrote: > Hi, > > I am trying to remote debug ARM (linux) targe

Re: [lldb-dev] [Release-testers] [5.0.0 Release] Release Candidate 2 tagged

On Mon, Aug 14, 2017 at 3:36 AM, Dimitry Andric wrote: > On 11 Aug 2017, at 04:00, Hans Wennborg via Release-testers > wrote: >> 5.0.0-rc2 was just tagged. >> >> I know we still have a bunch of open release blockers, but there has >> been a lot of merged patches and I'd like to find out what the

Re: [lldb-dev] [cfe-dev] [5.0.0 Release] Release Candidate 1 tagged

On Tue, Aug 1, 2017 at 3:01 AM, Simon Dardis wrote: > Hi all, > > I have new regressions for mips(el)-linux-gnu, some of which I have patches > for: > > I have patch for (believe this to be a libc bug): > LLVM-Unit :: > DebugInfo/DWARF/./DebugInfoDWARFTests/DWARFDebugInfo.TestDwarfVerifyInva

[lldb-dev] [5.0.0 Release] Only 3 release blockers left, please help fix!

Hello everyone, We started the week with 32 open release blockers and are now down to only 3: https://bugs.llvm.org/buglist.cgi?f1=blocked&o1=equals&v1=33849&query_format=advanced&resolution=--- Many thanks for your hard work so far. None of the three remaining ones have any traction, so any help

[lldb-dev] [5.0.0 Release] Release Candidate 3 tagged

Dear testers, 5.0.0-rc3 was just tagged. This is a release candidate in the real sense: if nothing bad comes up in testing, this is what the release is going to look like. Please build, test and upload binaries to the sftp (use the /data/testers-uploads/ directory) and let me know what issues re

Re: [lldb-dev] [5.0.0 Release] Release Candidate 3 tagged

On Fri, Aug 25, 2017 at 3:52 PM, Hans Wennborg wrote: > Dear testers, > > 5.0.0-rc3 was just tagged. > > This is a release candidate in the real sense: if nothing bad comes up > in testing, this is what the release is going to look like. > > Please build, test and upload binaries to the sftp (use

Re: [lldb-dev] [llvm-dev] [Release-testers] [5.0.0 Release] Release Candidate 3 tagged

I see there's a patch in progress to fix this: https://reviews.llvm.org/D36049 Since the issue was raised so late in the process, I don't think it will get fixed for 5.0.0 however. Maybe for 5.0.1. Thanks, Hans On Mon, Aug 28, 2017 at 12:40 AM, Dr.-Ing. Christoph Cullmann wrote: > Hi, > > one i

[lldb-dev] [5.0.0 Release] Release Candidate 3 source and binaries available

Hello everyone, Source, binaries and docs for LLVM-5.0.0-rc3 are now available at http://prereleases.llvm.org/5.0.0/#rc3 (I'll add more binaries as they become available.) We're a little behind schedule, but hopefully will be ready for the final release soon. Please report any problems you find

[lldb-dev] [5.0.0 Release] Release Candidate 4 tagged

Hello testers, 5.0.0-rc4 was just tagged. There were very few changes after rc3, and if nothing unexpected comes up, this is what the final release will look like. Please test and let me know if there are any issues. Cheers, Hans ___ lldb-dev mailing

Re: [lldb-dev] [llvm-dev] [5.0.0 Release] Release Candidate 4 tagged

So far it's just a tag in the svn repository. If you want the source, you can get it from there. In a few days, the tarballs will be uploaded to http://prereleases.llvm.org/5.0.0/ and I'll send a "source and binaries available" email. On Tue, Aug 29, 2017 at 11:24 PM, Somchai Smythe wrote: > Dow

Re: [lldb-dev] [5.0.0 Release] Release Candidate 3 tagged

__________ > From: lldb-dev [lldb-dev-boun...@lists.llvm.org] on behalf of Hans Wennborg > via lldb-dev [lldb-dev@lists.llvm.org] > Sent: 25 August 2017 23:52 > To: Release-testers > Cc: llvm-dev; cfe-dev; openmp-dev (openmp-...@lists.llvm.org); LLDB Dev > Subject: [

Re: [lldb-dev] [llvm-dev] [5.0.0 Release] Release Candidate 4 tagged

On Wed, Aug 30, 2017 at 2:14 PM, Michał Górny wrote: > W dniu wto, 29.08.2017 o godzinie 16∶52 -0700, użytkownik Hans Wennborg > via llvm-dev napisał: >> Hello testers, >> >> 5.0.0-rc4 was just tagged. >> >> There were very few changes after rc3, and if nothing unexpected comes >> up, this is what

Re: [lldb-dev] [llvm-dev] [5.0.0 Release] Release Candidate 4 tagged

On Wed, Aug 30, 2017 at 10:22 PM, Michał Górny wrote: > W dniu śro, 30.08.2017 o godzinie 15∶22 -0700, użytkownik Hans Wennborg > napisał: >> On Wed, Aug 30, 2017 at 2:14 PM, Michał Górny wrote: >> > W dniu wto, 29.08.2017 o godzinie 16∶52 -0700, użytkownik Hans Wennborg >> > via llvm-dev napisał

Re: [lldb-dev] [5.0.0 Release] Release Candidate 4 tagged

On Tue, Aug 29, 2017 at 4:52 PM, Hans Wennborg wrote: > Hello testers, > > 5.0.0-rc4 was just tagged. > > There were very few changes after rc3, and if nothing unexpected comes > up, this is what the final release will look like. > > Please test and let me know if there are any issues. Windows is

[lldb-dev] [5.0.0 Release] Release Candidate 5 tagged

Hello again, 5.0.0-rc5 was just tagged. I had hoped rc4 would be the last one, but I think we needed the fix for PR34381. Please do a quick test; if there are no new issues, this will become 'final' early next week. Thanks, Hans ___ lldb-dev mailing l

[lldb-dev] [5.0.0 Release] The final tag is in

Dear testers, The final version of 5.0.0 has just been tagged. There were no changes after rc5. Please build the final binaries and upload to the sftp. For those following along: this means 5.0.0 is complete, but it will take a few days to get the tarballs ready and published on the web page. I

[lldb-dev] LLVM 5.0.0 Release

It is my pleasure to announce that LLVM 5 is now available. Get it here: https://llvm.org/releases/download.html#5.0.0 (Why the big jump from 4.0.1? With the new versioning scheme, the major version is incremented for each major release: http://blog.llvm.org/2016/12/llvms-new-versioning-scheme.ht

Re: [lldb-dev] [Release-testers] [5.0.0 Release] The final tag is in

On Fri, Sep 8, 2017 at 5:33 AM, Brian Cain wrote: > > > On Tue, Sep 5, 2017 at 1:24 PM, Hans Wennborg via Release-testers > wrote: >> >> Dear testers, >> >> The final version of 5.0.0 has just been tagged. There were no changes >> after rc5. >> >> Please build the final binaries and upload to the

Re: [lldb-dev] [Release-testers] [cfe-dev] [5.0.0 Release] The final tag is in

Thanks! I've added them to the download page. It can take up to an hour for the change to propagate to the CDN. Cheers, Hans On Mon, Sep 11, 2017 at 11:52 AM, Simon Dardis wrote: > > Hi, > > I've uploaded the binaries for mips: > > SHA256(clang+llvm-5.0.0-mipsel-linux-gnu.tar.xz)= > b629b953bb6

[lldb-dev] [6.0.0 Release] Scheduling the release

Hello everyone, It's time to start making plans for the 6.0.0 release. Following our regular schedule, the branch would occur about two weeks into January, on Wednesday 17 January 2018, with the goal of shipping early March. This is the schedule I would propose. However, one large consumer of th

Re: [lldb-dev] [6.0.0 Release] Scheduling the release

On Wed, Dec 6, 2017 at 9:28 AM, Hans Wennborg wrote: > Hello everyone, > > It's time to start making plans for the 6.0.0 release. > > Following our regular schedule, the branch would occur about two weeks > into January, on Wednesday 17 January 2018, with the goal of shipping > early March. This i

Re: [lldb-dev] [Openmp-dev] [6.0.0 Release] Scheduling the release

On Thu, Dec 14, 2017 at 10:42 PM, Chandler Carruth wrote: > FWIW, I don't have really strong objections, but I'm honestly not a fan. The > reason is mostly that I think it is very late to make the change and likely > to mean most people are on holiday when the branch occurs. I somewhat > anticipat

[lldb-dev] [6.0.0 Release] One week to the branch

This is a quick reminder that the upcoming release branch is scheduled for one week from today: Wednesday 3 January 2018. Please try to avoid disruptive changes right before the branch. As discussed in [1], the branch is happening a little earlier this year. The first two weeks of the release pro

[lldb-dev] [6.0.0 Release] The release branch is here; trunk is now 7.0.0

Hello everyone, The release branch for 6.0.0 was created from trunk at r321711 around 3pm GMT today, and the trunk version was subsequently incremented to 7.0.0. (Hopefully the git mirror will have the branch soon too.) Note that this time we're doing an early "slow start" of the release process.

[lldb-dev] [6.0.0 Release] Release Candidate 1 tagged

Dear testers, Start your engines; 6.0.0-rc1 was just tagged. I know there are still open blockers and it's early in the process in a way, but I'd like to find out where we are. Please run the test script, let me know the results, and upload binaries. Thanks, Hans

Re: [lldb-dev] [llvm-dev] [Release-testers] [6.0.0 Release] Release Candidate 1 tagged

On Thu, Jan 18, 2018 at 7:27 PM, Dimitry Andric wrote: > On 18 Jan 2018, at 15:03, Jonas Hahnfeld wrote: >> >> Am 2018-01-18 14:55, schrieb Dimitry Andric via llvm-dev: >>> On 17 Jan 2018, at 18:53, Hans Wennborg via Release-testers >>> wrote: Start your engines; 6.0.0-rc1 was just tagged.

Re: [lldb-dev] [llvm-dev] [Release-testers] [6.0.0 Release] Release Candidate 1 tagged

Thanks! On Sat, Jan 20, 2018 at 1:32 PM, Dimitry Andric wrote: > On 19 Jan 2018, at 17:11, Hans Wennborg wrote: >> >> On Thu, Jan 18, 2018 at 7:27 PM, Dimitry Andric wrote: >>> On 18 Jan 2018, at 15:03, Jonas Hahnfeld wrote: Am 2018-01-18 14:55, schrieb Dimitry Andric via llvm-dev: >

[lldb-dev] [6.0.0 Release] Release Candidate 2 tagged

Dear testers, There's been a lot of merges since rc1, and hopefully the tests are in a better state now. 6.0.0-rc2 was just tagged, after r324506. Please test, let me know how it goes, and upload binaries. Thanks, Hans ___ lldb-dev mailing list lldb-d

Re: [lldb-dev] [6.0.0 Release] Release Candidate 2 tagged

On Wed, Feb 7, 2018 at 9:51 PM, Hans Wennborg wrote: > Dear testers, > > There's been a lot of merges since rc1, and hopefully the tests are in > a better state now. > > 6.0.0-rc2 was just tagged, after r324506. > > Please test, let me know how it goes, and upload binaries. Windows binaries are r

Re: [lldb-dev] [Release-testers] [6.0.0 Release] Release Candidate 2 tagged

On Thu, Feb 8, 2018 at 10:43 PM, Dimitry Andric wrote: > On 7 Feb 2018, at 21:51, Hans Wennborg via Release-testers > wrote: >> >> There's been a lot of merges since rc1, and hopefully the tests are in >> a better state now. >> >> 6.0.0-rc2 was just tagged, after r324506. >> >> Please test, let

[lldb-dev] [6.0.0 Release] Release Candidate 2 source, docs and binaries available

Hello everyone, Source, docs and binaries for LLVM-6.0.0-rc2 are now available at http://prereleases.llvm.org/6.0.0/#rc2 I'll add more binaries as they become available. Please report any problems you find, ideally as bugs marked as blockers of http://llvm.org/PR35804 Thanks, Hans _

Re: [lldb-dev] [Openmp-dev] [cfe-dev] [Release-testers] [6.0.0 Release] Release Candidate 2 tagged

On Sun, Feb 11, 2018 at 3:31 PM, Dimitry Andric wrote: > On 9 Feb 2018, at 22:30, Dimitry Andric wrote: >> >> On 9 Feb 2018, at 22:11, Dimitry Andric via Openmp-dev >> wrote: >>> >>> On 9 Feb 2018, at 20:40, Dimitry Andric via cfe-dev >>> wrote: > On 9 Feb 2018, at 10:20, Hans Wennbo

Re: [lldb-dev] [llvm-dev] [6.0.0 Release] Release Candidate 2 tagged

On Tue, Feb 13, 2018 at 10:36 AM, Jonas Hahnfeld wrote: > Am 2018-02-07 21:51, schrieb Hans Wennborg via llvm-dev: >> >> Dear testers, >> >> There's been a lot of merges since rc1, and hopefully the tests are in >> a better state now. >> >> 6.0.0-rc2 was just tagged, after r324506. >> >> Please te

Re: [lldb-dev] [llvm-dev] [Openmp-dev] [cfe-dev] [Release-testers] [6.0.0 Release] Release Candidate 2 tagged

Hi Andrew, On Mon, Feb 12, 2018 at 5:00 PM, Andrew Kelley wrote: > I noticed a problem with llvm-config.exe on Windows: > >>"c:\Users\andy\llvm+clang-6.0.0rc2-win64-msvc-release\bin\llvm-config.exe" >>--system-libs > psapi.lib shell32.lib ole32.lib uuid.lib > > But then when I link against LLVM

Re: [lldb-dev] [Release-testers] [6.0.0 Release] Release Candidate 2 tagged

Thanks! I've added the binaries to http://prereleases.llvm.org/6.0.0/ On Tue, Feb 13, 2018 at 10:57 PM, Simon Dardis wrote: > Hi Hans, > > I'm seeing one unexpected failure: > > libc++ :: > std/input.output/stream.buffers/streambuf/streambuf.protected/streambuf.put.area/pbump2gig.pass.cpp >

[lldb-dev] [6.0.0 Release] TIme to wrap it up

Dear everyone, The release schedule has snuck up on me again, and it's time to wrap up the release. We won't make it to the final tag on the 21st as per the schedule, but I would like to get all outstanding blockers fixed and rc3 tagged by Friday. Hopefully this would be the last rc and we could

[lldb-dev] [6.0.0 Release] Release notes nag email

Dear everyone, We're getting close to the 6.0.0 release, but the release notes are still in a pretty bad state. You can see the notes for rc2 here: http://prereleases.llvm.org/6.0.0/#rc2 (a few things have been added since). When the release happens, a lot of people will look at the notes, so it'

[lldb-dev] [6.0.0 Release] Release Candidate 3 tagged

Dear testers, 6.0.0-rc3 was just tagged, after r325901 on the branch. There are still a few open blockers, but I'm not sure we'll actually end up blocking on all of them. So depending on what comes up, this release candidate is probably pretty close to what the final release will look like (I'm s

[lldb-dev] [6.0.0 Release] Release Candidate 3 source, docs and binaries available

Hi everyone, The source, docs and binaries for LLVM-6.0.0-rc3 are now available at http://prereleases.llvm.org/6.0.0/#rc3 More binaries will be added as they become available. Please report any problems you find as bugs marked blocking http://llvm.org/PR35804 If this looks good, the final tag w

Re: [lldb-dev] [6.0.0 Release] Release Candidate 3 tagged

On Fri, Feb 23, 2018 at 4:14 PM, Hans Wennborg wrote: > Dear testers, > > 6.0.0-rc3 was just tagged, after r325901 on the branch. > > There are still a few open blockers, but I'm not sure we'll actually > end up blocking on all of them. So depending on what comes up, this > release candidate is pr

Re: [lldb-dev] [Release-testers] [6.0.0 Release] Release Candidate 3 tagged

Thanks! Added to the web page now. On Tue, Feb 27, 2018 at 9:18 PM, Simon Dardis wrote: > Hi, > > No major issues seen so far for mips. Binaries uploaded. > > SHA256(clang+llvm-6.0.0-rc3-mipsel-linux-gnu.tar.xz)= > 6e4fab79cc341a9084dab94cced108daff39fcde14a11e8d7ae454e9f92cb77c > SHA256(clang+l

[lldb-dev] [6.0.0 Release] The final tag is in

Dear testers, The final version of 6.0.0 has just been tagged from the branch after r326550. It has the same contents as -rc3 modulo release notes and one small x86 fix (r326393). Please build the final binaries and upload to the sftp. For those following along: this means llvm-6.0.0 is complete

[lldb-dev] LLVM 6.0.0 Release

I am pleased to announce that LLVM 6 is now available. Get it here: https://llvm.org/releases/download.html#6.0.0 This release is the result of the community's work over the past six months, including: retpoline Spectre variant 2 mitigation, significantly improved CodeView debug info for Windows,

[lldb-dev] [7.0.0 Release] Schedule proposal

Hello everyone, There's plenty of time before the release process starts, but I'd like to begin the schedule discussion. For the September release we usually branch mid-July. However, this year my vacation runs a little later, so a good branch date for me would be the 1st of August. Proposal: -

Re: [lldb-dev] [llvm-dev] [7.0.0 Release] Schedule proposal

Yes, I expect that to have happened well before this process starts. On Fri, Jun 8, 2018 at 5:34 AM, Somchai Smythe wrote: > I think you need to get 6.0.1 out the door first > > On 6/7/18, Hans Wennborg via llvm-dev wrote: >> Hello everyone, >> >> There's plenty of time before the release pr

Re: [lldb-dev] [cfe-dev] [7.0.0 Release] Schedule proposal

On Thu, Jun 7, 2018 at 6:56 PM, wrote: >> Proposal: >> >> - 1 August 2018: Branch; RC1 soon after >> - 22 August 2018: RC2; all lose ends should be tied up by now >> - 5 September; final tag, release a few days later (don't slip past >> first half of September) >> >> What do you think? >> >> I'm

[lldb-dev] [7.0.0 Release] One week to the branch

Hello everyone, Here's just a quick reminder that the upcoming release branch is scheduled for creation one week from today, on Wednesday 1 August 2018. Please try to avoid disruptive changes close to the branch. The full release schedule is available under Upcoming Releases at https://llvm.org/

[lldb-dev] [7.0.0 Release] The release branch is open; trunk is now 8.0.0

Hi everyone, The release branch for 7.0.0 was created off trunk at r338536 earlier today, and the trunk version was subsequently bumped to 8.0.0. Release blockers are tracked by https://llvm.org/PR38406 Please mark any bugs, old or new, that need to be fixed for the release as blocking that. To

[lldb-dev] [7.0.0 Release] rc1 has been tagged

Dear testers, 7.0.0-rc1 was just tagged (from the branch at r338847). It's early in the release process, but I'd like to find out what the status is of the branch on our various platforms. Please run the test script, share the results, and upload binaries. Thanks, Hans _

Re: [lldb-dev] [cfe-dev] [7.0.0 Release] rc1 has been tagged

On Fri, Aug 3, 2018 at 3:38 PM, wrote: > Hi Hans, > > I was just trying to push a release note about DWARF v5 support. I did: > git checkout release_70 # in the monorepo > git commit > git llvm push > but that fails. How do you want to do release notes? I'm not familiar with "git llvm",

Re: [lldb-dev] [Release-testers] [7.0.0 Release] rc1 has been tagged

On Sun, Aug 5, 2018 at 5:49 PM, Dimitry Andric wrote: > On 3 Aug 2018, at 13:37, Hans Wennborg via Release-testers > wrote: >> >> 7.0.0-rc1 was just tagged (from the branch at r338847). >> >> It's early in the release process, but I'd like to find out what the >> status is of the branch on our v

[lldb-dev] [7.0.0 Release] Release Candidate 1 source, docs, and binaries available

Hello everyone, Source, docs, and binaries for LLVM-7.0.0-rc1 are now available at http://prereleases.llvm.org/7.0.0/#rc1 I'll add more binaries as they become available. Please try it out and report any problems as bugs marked as blockers of https://llvm.org/PR38406 Thanks, Hans __

Re: [lldb-dev] [Release-testers] [7.0.0 Release] rc1 has been tagged

On Tue, Aug 7, 2018 at 9:49 PM, Dimitry Andric wrote: > On 6 Aug 2018, at 18:23, Hans Wennborg wrote: >> >> On Sun, Aug 5, 2018 at 5:49 PM, Dimitry Andric wrote: >>> On 3 Aug 2018, at 13:37, Hans Wennborg via Release-testers >>> wrote: 7.0.0-rc1 was just tagged (from the branch at r3

Re: [lldb-dev] [llvm-dev] [Release-testers] [7.0.0 Release] rc1 has been tagged

On Tue, Aug 7, 2018 at 10:38 PM, Louis Dionne wrote: > > >> On Aug 7, 2018, at 16:17, Dimitry Andric via llvm-dev >> wrote: >> >> On 3 Aug 2018, at 13:37, Hans Wennborg via Release-testers >> wrote: >>> >>> Dear testers, >>> >>> 7.0.0-rc1 was just tagged (from the branch at r338847). >>> >>> I

<    1   2   3   4   >