From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30211 invoked by alias); 6 Nov 2002 03:20:14 -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 30203 invoked from network); 6 Nov 2002 03:20:13 -0000 Received: from unknown (HELO crack.them.org) (65.125.64.184) by sources.redhat.com with SMTP; 6 Nov 2002 03:20:13 -0000 Received: from nevyn.them.org ([66.93.61.169] ident=mail) by crack.them.org with asmtp (Exim 3.12 #1 (Debian)) id 189HfB-0008OR-00; Tue, 05 Nov 2002 22:19:33 -0600 Received: from drow by nevyn.them.org with local (Exim 3.36 #1 (Debian)) id 189GkZ-0004X9-00; Tue, 05 Nov 2002 22:21:03 -0500 Date: Tue, 05 Nov 2002 19:20:00 -0000 From: Daniel Jacobowitz To: Joel Brobecker Cc: gdb-patches@sources.redhat.com Subject: Re: Which HPPA targets do we still support? Message-ID: <20021106032103.GA16623@nevyn.them.org> Mail-Followup-To: Joel Brobecker , gdb-patches@sources.redhat.com References: <20021106020308.GM5164@gnat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20021106020308.GM5164@gnat.com> User-Agent: Mutt/1.5.1i X-SW-Source: 2002-11/txt/msg00087.txt.bz2 On Tue, Nov 05, 2002 at 06:03:08PM -0800, Joel Brobecker wrote: > I was looking at configure.tgt to see the list of OSABI I would need to > add in osabi.[hc], and found a list that's a bit longer than I expected: > > hppa*-*-bsd*) gdb_target=hppabsd ;; > hppa*-*-pro*) gdb_target=hppapro ;; > hppa*64*-*-hpux11*) gdb_target=hppa64 ;; > hppa*-*-hpux*) gdb_target=hppahpux ;; > hppa*-*-hiux*) gdb_target=hppahpux ;; > hppa*-*-osf*) gdb_target=hppaosf ;; > hppa*-*-*) gdb_target=hppa ;; > > So far, the only target that I knew of was the hppa*-*-hpux*. > I did not know that hppa*-*-bsd* and hppa*-*-osf* existed. > I did not know about the hppa*-*-pro* either... > > All I have access to are 2 HP/UX machines, with 11.00 and 10.20 (but > this machine is very slow)... While doing the multi-arch conversion, > I'll try not to break the other targets, but that's going to be a hard > battle. A second pair of eyes from a multiarch guru will be greatly > appreciated. Maybe I should send a message to gdb@sources to check if > some people are still using all these targets? Actually, I believe that no one is using any of these targets except for HP/UX. hppa*-*-pro* was kept around because it is (was?) standalone; you could build an hppa-proelf cross debugger to make sure you didn't break compilation for the PA. I've seen bug reports for HP/UX, but never for any of the others; and we know the HPPA target has broken periodically, so that's a good hint that no one's tracking them. Of course if it's not much trouble, we can keep them for now and deal with it later - but I'm not sure that we need to hang on to all of them. Looking at GCC's supported targets, I wouldn't be surprised if hppa-openbsd is in use, but that won't match the existing pattern anyway... ditto hppa-rtems. > Is the list above the correct list to look at to get the list of new > OSABI enums? I would like to suggest the addition of > > GDB_OSABI_HPPA > GDB_OSABI_HPPA_64 > GDB_OSABI_HPPA_BSD > GDB_OSABI_HPPA_HPUX > GDB_OSABI_HPPA_OSF > GDB_OSABI_HPPA_PRO > > Does this look ok? I don't think they're necessary, by analogy with the existing code... certainly not GDB_OSABI_HPPA or GDB_OSABI_HPPA_64. We probably need GDB_OSABI_HPUX. We've already got OSF1, which is presumably the right OSF target. If we're going to keep the anonymous "hppa-bsd" target we may need GDB_OSABI_BSD. I don't know if hppa-proelf has its own OSABI or not. -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer