[lldb-dev] [Bug 27935] Linking CXX executable lldb-argdumper and lldb-mi fails

2017-02-09 Thread via lldb-dev
https://llvm.org/bugs/show_bug.cgi?id=27935 Vedran Miletic changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

Re: [lldb-dev] A typo on the "Testing LLDB" tutorial page?

2017-02-09 Thread Greg Clayton via lldb-dev
Thanks for this, fixed with: % svn commit test.html Sendingtest.html Transmitting file data .done Committing transaction... Committed revision 294597. > On Feb 8, 2017, at 8:44 PM, Ramana via lldb-dev > wrote: > > On the "Testing LLDB" tutorial page, in the description under "RUNNING

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

2017-02-09 Thread Diana Picus via lldb-dev
Hi, AArch64 good to go. f27db27da7f75a435d89ba63c8a762885fd86a1a clang+llvm-4.0.0-rc2-aarch64-linux-gnu.tar.xz Diana On 9 February 2017 at 01:33, Hans Wennborg via Release-testers wrote: > Hello testers, > > 4.0.0-rc2 was just tagged from the branch at r294535. > > There are still open relase

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

2017-02-09 Thread Mehdi Amini via lldb-dev
(stage-3 check-all fails on macOS around libcxxabi but I think it is usual). I pushed: 9df4d8a9c74ccb1aaaf934f19a48d003917c9d81 rc2/clang+llvm-4.0.0-rc2-x86_64-apple-darwin.tar.xz — Mehdi > On Feb 8, 2017, at 4:33 PM, Hans Wennborg via llvm-dev > wrote: > > Hello testers, > > 4.0.0-rc2

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

2017-02-09 Thread Hans Wennborg via lldb-dev
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

2017-02-09 Thread Hans Wennborg via lldb-dev
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

2017-02-09 Thread Hans Wennborg via lldb-dev
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

2017-02-09 Thread Dimitry Andric via lldb-dev
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 following: SHA256 (clang+llvm-4.0.0-rc2-i386-unknown-freebsd10.tar.xz

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

2017-02-09 Thread Hans Wennborg via lldb-dev
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] [4.0.0] Release notes nag email

2017-02-09 Thread Matthias Braun via lldb-dev
> On Feb 9, 2017, at 1:46 PM, Hans Wennborg via llvm-dev > wrote: > > 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

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

2017-02-09 Thread Quentin Colombet via lldb-dev
> On Feb 9, 2017, at 1:46 PM, Hans Wennborg wrote: > > 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.