From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29405 invoked by alias); 13 May 2003 22:59:04 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 29397 invoked from network); 13 May 2003 22:59:02 -0000 Received: from unknown (HELO e4.ny.us.ibm.com) (32.97.182.104) by sources.redhat.com with SMTP; 13 May 2003 22:59:02 -0000 Received: from northrelay04.pok.ibm.com (northrelay04.pok.ibm.com [9.56.224.206]) by e4.ny.us.ibm.com (8.12.9/8.12.2) with ESMTP id h4DMwrsZ155210; Tue, 13 May 2003 18:58:53 -0400 Received: from d27ml103.rchland.ibm.com (d01av02.pok.ibm.com [9.56.224.216]) by northrelay04.pok.ibm.com (8.12.9/NCO/VER6.5) with ESMTP id h4DMwoxT178242; Tue, 13 May 2003 18:58:51 -0400 Subject: Re: [PATCH] new support for PPC64 architecture To: Jim Blandy Cc: Elena Zannoni , gdb-patches@sources.redhat.com, will_schmidt@vnet.ibm.com Message-ID: From: Will Schmidt Date: Tue, 13 May 2003 22:59:00 -0000 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII X-SW-Source: 2003-05/txt/msg00206.txt.bz2 Those steps sound good to me. :-) Elena, were you able to get your build to complete? willschm@us.ibm.com Linux on PowerPC-64 Development IBM Rochester Jim Blandy To: Will Schmidt/Rochester/IBM@IBMUS cc: gdb-patches@sources.redhat.com, will_schmidt@vnet.ibm.com, Elena Zannoni 05/13/2003 05:38 PM Subject: Re: [PATCH] new support for PPC64 architecture "Will Schmidt" writes: > This patch contains code that provides support for GDB on the PPC64 > architecture. This patch will apply clean on top of the RedHat > gdb-5.3post-0.20021129.29.src.rpm. (A patch against CVS will > happen, but not today.. ) Okay --- here are the next steps, as I see them: - As you say, get the patch to apply and run against current sources. This can happen without worrying about bringing the patch in line with current requirements for contributions: multi-arch, using new interfaces, etc. - Get a test suite run with those sources that we can use as a baseline for evaluating subsequent work. - Worry about multi-arch, new interfaces, etc. This should be pretty easy going, since both tasks break down into (possibly large) sets of small, mostly independent changes. It'll be easy to work incrementally, and share the job.