From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 96300 invoked by alias); 17 Jul 2015 17:53:34 -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 96290 invoked by uid 89); 17 Jul 2015 17:53:33 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.2 required=5.0 tests=AWL,BAYES_00,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_NONE autolearn=no version=3.3.2 X-HELO: rock.gnat.com Received: from rock.gnat.com (HELO rock.gnat.com) (205.232.38.15) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-SHA encrypted) ESMTPS; Fri, 17 Jul 2015 17:53:32 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id 8756828E9F; Fri, 17 Jul 2015 13:53:30 -0400 (EDT) Received: from rock.gnat.com ([127.0.0.1]) by localhost (rock.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id g-SNoEI8dg3X; Fri, 17 Jul 2015 13:53:30 -0400 (EDT) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id 619DD28890; Fri, 17 Jul 2015 13:53:30 -0400 (EDT) Received: by joel.gnat.com (Postfix, from userid 1000) id E6CAF40283; Fri, 17 Jul 2015 10:53:28 -0700 (PDT) Date: Fri, 17 Jul 2015 17:53:00 -0000 From: Joel Brobecker To: gdb-patches@sourceware.org Cc: keiths@redhat.com, Jan Kratochvil Subject: GDB 7.10 release 2015-07-17 status update? Message-ID: <20150717175328.GA15874@adacore.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.23 (2014-03-12) X-SW-Source: 2015-07/txt/msg00511.txt.bz2 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. -- Joel