From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14155 invoked by alias); 2 Jul 2004 22:40:58 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 14135 invoked from network); 2 Jul 2004 22:40:55 -0000 Received: from unknown (HELO nevyn.them.org) (66.93.172.17) by sourceware.org with SMTP; 2 Jul 2004 22:40:55 -0000 Received: from drow by nevyn.them.org with local (Exim 4.34 #1 (Debian)) id 1BgWi7-0005aX-Li; Fri, 02 Jul 2004 18:40:47 -0400 Date: Fri, 02 Jul 2004 22:40:00 -0000 From: Daniel Jacobowitz To: Jim Blandy Cc: gdb@sources.redhat.com Subject: Re: Delay the branch for E500 native support Message-ID: <20040702224047.GA21295@nevyn.them.org> Mail-Followup-To: Jim Blandy , gdb@sources.redhat.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.5.1+cvs20040105i X-SW-Source: 2004-07/txt/msg00014.txt.bz2 On Fri, Jul 02, 2004 at 05:26:35PM -0500, Jim Blandy wrote: > > Would it be possible to delay the GDB 6.2 branch for another week, > until Fri, July 9th? > > It would be really nice for 6.2 to contain full, unqualified native > PowerPC E500 Linux support. We're really close. The bulk of it is > committed and working. The two missing pieces are that you can't > access the E500's vector registers in multi-threaded programs, and you > can't refer to variables located in vector registers, because of GCC's > use of DW_OP_piece. I've posted patches to address the first problem, > which are being discussed for revision, and I'm working on patches for > the second issue, revised as discussed in the thread at: > > http://sources.redhat.com/ml/gdb-patches/2003-05/msg00425.html DW_OP_piece will presumably be a substantial change. While I'd love to see it in GDB 6.2: (A) A week before the branch is not a good time for huge new features. (B) it can be merged after the branch is cut, once it is known to work on HEAD and has been tested - in fact this is probably preferable to committing before the branch. The vector register stuff I have no comments about, since it's not going to affect other targets in the same way. That's an even better candidate for committing to the branch after branching. > I'm happy to put in time over the U.S. holiday weekend, and do what it > takes next week to get it all posted for further review by midweek. > If maintainers can give me detailed instructions on how they want the > patches revised, I'll be happy to comply. > > I'd just really like to be able to say, in the GDB 6.2 NEWS: "Added > support for native PowerPC E500 Linux", without qualifications. I would really have liked for GDB 6.1 to contain inter-compilation-unit reference support too. If the timing doesn't work out, it doesn't work out - if the schedule holds there may even be another release this year. -- Daniel Jacobowitz