From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13031 invoked by alias); 18 Sep 2013 22:26:58 -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 13012 invoked by uid 89); 18 Sep 2013 22:26:58 -0000 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; Wed, 18 Sep 2013 22:26:58 +0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=0.0 required=5.0 tests=AWL,BAYES_50,KHOP_THREADED,RDNS_NONE,SPF_HELO_FAIL autolearn=no version=3.3.2 X-Spam-User: qpsmtpd, 2 recipients X-HELO: relay1.mentorg.com Received: from svr-orw-fem-01.mgc.mentorg.com ([147.34.98.93]) by relay1.mentorg.com with esmtp id 1VMQCy-0006MO-FD from Maciej_Rozycki@mentor.com ; Wed, 18 Sep 2013 15:26:52 -0700 Received: from SVR-IES-FEM-01.mgc.mentorg.com ([137.202.0.104]) by svr-orw-fem-01.mgc.mentorg.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Wed, 18 Sep 2013 15:26:52 -0700 Received: from [172.30.64.65] (137.202.0.76) by SVR-IES-FEM-01.mgc.mentorg.com (137.202.0.104) with Microsoft SMTP Server id 14.2.247.3; Wed, 18 Sep 2013 23:26:50 +0100 Date: Wed, 18 Sep 2013 22:26:00 -0000 From: "Maciej W. Rozycki" To: Joel Brobecker CC: Tristan Gingold , Richard Sandiford , , Subject: Re: Release 2.24 In-Reply-To: <20130918213245.GO3132@adacore.com> Message-ID: References: <2741C968-721F-46E9-A2BA-E4B0F64C444B@adacore.com> <20130918213245.GO3132@adacore.com> User-Agent: Alpine 1.10 (DEB 962 2008-03-14) MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" X-SW-Source: 2013-09/txt/msg00637.txt.bz2 On Wed, 18 Sep 2013, Joel Brobecker wrote: > > Just as a reminder, can we please coordinate so that GDB 7.7 is released > > before binutils 2.24? > > It's fine with GDB of course if the Binutils projects wants to wait > for the GDB 7.7 release, but my guess is that we are quite a ways > away from it: We need the git transition to be done first, then > we need to make the branch and stabilize it towards a release state. I reckon the original plan was to make the steps in the reverse order so that there's no pressure from outstanding releases to get the GIT tree in order, which I found reasonable -- what was the rationale behind changing the plan? It has somehow escaped me (a list archive reference will do). > > On the MIPS target we've switched PLT formats produced by LD for MIPS16 > > and microMIPS binaries and for correct frame unwinding GDB has to > > understand them. Otherwise it'll fail in odd ways, e.g. when stepping > > over a function called via PLT. Of course all code required is there in > > our shared repository, it's just a matter of making the releases in the > > right order so that ordinary developers have a version of GDB to upgrade > > to available if needed. > > Can you patch gdb-7.6 to understand the new format as well as > the old one with a patch that could be deemed safe? Perhaps it would > make sense to make a 7.6.2 release just for MIPS. That sounds like a plan, thanks, and should be doable with a reasonable effort -- the changes really needed by GDB are the addition of _bfd_mips_elf_get_synthetic_symtab to bfd/elfxx-mips.c, its wiring in bfd/elf32-mips.c, and then small self-contained pieces in opcodes/ and of course gdb/. I'll have a look at it and let you know when I'm ready with a backport. BTW, please note that the old format remains supported and produced for standard MIPS and, in some cases, mixed-mode binaries, so it's not like it's going away or something. Maciej