From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5843 invoked by alias); 17 Jul 2015 18:14:56 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 5834 invoked by uid 89); 17 Jul 2015 18:14:56 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.4 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 X-HELO: relay1.mentorg.com Received: from relay1.mentorg.com (HELO relay1.mentorg.com) (192.94.38.131) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 17 Jul 2015 18:14:55 +0000 Received: from svr-orw-fem-06.mgc.mentorg.com ([147.34.97.120]) by relay1.mentorg.com with esmtp id 1ZGA9r-00007G-BM from Luis_Gustavo@mentor.com ; Fri, 17 Jul 2015 11:14:51 -0700 Received: from [172.30.9.81] (147.34.91.1) by SVR-ORW-FEM-06.mgc.mentorg.com (147.34.97.120) with Microsoft SMTP Server id 14.3.224.2; Fri, 17 Jul 2015 11:14:50 -0700 Message-ID: <55A94617.1040701@codesourcery.com> Date: Fri, 17 Jul 2015 18:14:00 -0000 From: Luis Machado Reply-To: Luis Machado User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: Joel Brobecker , CC: , Jan Kratochvil , Subject: Re: GDB 7.10 release 2015-07-17 status update? References: <20150717175328.GA15874@adacore.com> In-Reply-To: <20150717175328.GA15874@adacore.com> Content-Type: text/plain; charset="windows-1252"; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2015-07/txt/msg00512.txt.bz2 Hi Joel, On 07/17/2015 02:53 PM, Joel Brobecker wrote: > Hello, > > It's been almost 2 weeks since we branched, and there has been a number > of issues fixed since then. > > On the wiki (https://sourceware.org/gdb/wiki/GDB_7.10_Release), > we have 1 TODO item left: > > - Eval with KeithS regressions due to GCC 5.1 (regressions caused by > GCC rather than GDB) > > For this one, the latest (private) update I got from Keith was > that GDB was likely in the clear - mostly GCC issues? Keith? > > We still have 2 "Maybe"'s: > > - [GCC review/Jan] PR compile/18485 (set debug compile: Display GCC driver > filename) > - [GCC review/Jan] PR compile/18486 (Add 'set compile-gcc') > > If the reason for it being a "Maybe" is time, we can probably give you > a little extra time (see below). > > I've moved the following item to the Exclude list, as per Pedro's > recommendation: > > - PR gdb/18600 (After forking and threads spawning, gdb leaves newly > created threads stopped) (too delicate) > > David Edelson reported that the buildBot was reporting a lot of > failures around the time we cut the branch. Has anyone looked at those > since then? When I did, I was looking at the waterfall view, and > several builds looked like they were failing right at the beginning, > so I didn't know what to make of it. Also, that's a lot of info to > grok, so I didn't have time to look further. > > What I can say is that I've tested the branch with a number of > platforms, not as exhaustively of course, but so far, it looks > pretty good. > > What I think we should do is give it another couple of weeks, and > see if other reports come up. It would be good, also, if we had > some info about the buildBOT failures, and whether the release > might be affected by any regression it found. > > So, I propose a re-sync on Aug 3rd. > Do we consider the fact that mingw32 (and maybe other non-GNU) builds have been broken since this libiberty sync a blocker/critical issue? https://sourceware.org/ml/gdb-patches/2015-06/msg00405.html Last we heard of it was here... https://sourceware.org/ml/gdb-patches/2015-06/msg00654.html But we received no word from Yunlian Jiang yet. Maybe it should be added to the wiki too?