Re: [lldb-dev] [3.8 Release] Release status

2016-02-23 Thread Aaron Ballman via lldb-dev
On Mon, Feb 22, 2016 at 10:48 PM, Hans Wennborg wrote: > I had hoped to tag rc3 today (I feel like I've said this a lot > lately), but it's at least really, really close. I'm waiting for: > > - r261297 - Implement the likely resolution of core issue 253. > Still in post-commit review. > > - D175

Re: [lldb-dev] [3.8 Release] Release status

2016-02-22 Thread Hans Wennborg via lldb-dev
I had hoped to tag rc3 today (I feel like I've said this a lot lately), but it's at least really, really close. I'm waiting for: - r261297 - Implement the likely resolution of core issue 253. Still in post-commit review. - D17507 - The controlling expression for _Generic is unevaluated New fo

Re: [lldb-dev] [3.8 Release] Release status

2016-02-20 Thread Hal Finkel via lldb-dev
quot; > , "Davide Italiano" , "Quentin > Colombet" , "Hal Finkel" > , "Chandler Carruth" , "JF Bastien" > , "Nemanja Ivanovic" > , "Matthias Braun" > Sent: Friday, February 19, 2016 9:33:16 AM > Subject: Re

Re: [lldb-dev] [3.8 Release] Release status

2016-02-20 Thread Davide Italiano via lldb-dev
On Thu, Feb 18, 2016 at 4:22 PM, Hans Wennborg wrote: > According to the schedule (e.g. on the right on llvm.org), we should > have tagged the release by now, but we haven't, so we're officially > behind schedule. I'm still optimistic that we can wrap this up pretty > soon, though. > > This is wha

Re: [lldb-dev] [3.8 Release] Release status

2016-02-19 Thread Hans Wennborg via lldb-dev
Many thanks to everyone who helped out after this email yesterday! Here's an update on the remaining issues. As you can see, it's a much shorter list :-) I'm hoping to tag rc3 very soon. Thanks again, Hans On Thu, Feb 18, 2016 at 4:22 PM, Hans Wennborg wrote: > - Shrink-wrapping vs TLS: Davide

Re: [lldb-dev] [3.8 Release] Release status

2016-02-19 Thread Quentin Colombet via lldb-dev
Hi Hans, Thanks for pushing this forward. > On Feb 18, 2016, at 4:22 PM, Hans Wennborg wrote: > > According to the schedule (e.g. on the right on llvm.org), we should > have tagged the release by now, but we haven't, so we're officially > behind schedule. I'm still optimistic that we can wrap t

Re: [lldb-dev] [3.8 Release] Release status

2016-02-19 Thread Renato Golin via lldb-dev
On 19 February 2016 at 15:33, Renato Golin wrote: > On 19 February 2016 at 00:22, Hans Wennborg via lldb-dev > wrote: >> - PR26600: Loop vectorization creates an unsafe out-of-bounds load >> There's a patch out: http://reviews.llvm.org/D17332 >> But no comments yet.. Hal? > > This looks like

Re: [lldb-dev] [3.8 Release] Release status

2016-02-19 Thread Daniel Sanders via lldb-dev
ruth; JF Bastien; Nemanja Ivanovic; Matthias Braun Subject: RE: [lldb-dev] [3.8 Release] Release status Hi Hans, I think PR26369 should be on the list but we could potentially make do without it (see below). Without it we get 23 failures on libcxx tests caused by failing to link the tests with li

Re: [lldb-dev] [3.8 Release] Release status

2016-02-19 Thread Renato Golin via lldb-dev
On 19 February 2016 at 00:22, Hans Wennborg via lldb-dev wrote: > - PR26600: Loop vectorization creates an unsafe out-of-bounds load > There's a patch out: http://reviews.llvm.org/D17332 > But no comments yet.. Hal? This looks like a serious bug but Hal's idea is still unproven. I think we sh

Re: [lldb-dev] [3.8 Release] Release status

2016-02-19 Thread Daniel Sanders via lldb-dev
lists.llvm.org); release-test...@lists.llvm.org; Cong Hou; Davide Italiano; Quentin Colombet; Hal Finkel; Chandler Carruth; JF Bastien; Nemanja Ivanovic; Matthias Braun Subject: [lldb-dev] [3.8 Release] Release status According to the schedule (e.g. on the right on llvm.org), we should have tagged the

[lldb-dev] [3.8 Release] Release status

2016-02-18 Thread Hans Wennborg via lldb-dev
According to the schedule (e.g. on the right on llvm.org), we should have tagged the release by now, but we haven't, so we're officially behind schedule. I'm still optimistic that we can wrap this up pretty soon, though. This is what's blocking us: - PR26509: Crash in InnerLoopVectorizer::vectori