From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23790 invoked by alias); 24 Dec 2002 19:39: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 23776 invoked from network); 24 Dec 2002 19:39:03 -0000 Received: from unknown (HELO crack.them.org) (65.125.64.184) by 209.249.29.67 with SMTP; 24 Dec 2002 19:39:03 -0000 Received: from nevyn.them.org ([66.93.61.169] ident=mail) by crack.them.org with asmtp (Exim 3.12 #1 (Debian)) id 18Qwlk-0006lB-00; Tue, 24 Dec 2002 15:39:20 -0600 Received: from drow by nevyn.them.org with local (Exim 3.36 #1 (Debian)) id 18QuuR-0000ZY-00; Tue, 24 Dec 2002 14:40:11 -0500 Date: Tue, 24 Dec 2002 12:09:00 -0000 From: Daniel Jacobowitz To: Kevin Buettner Cc: gdb-patches@sources.redhat.com Subject: Re: [RFA] Add support for 64-bit MIPS GNU/Linux targets Message-ID: <20021224194011.GA2004@nevyn.them.org> Mail-Followup-To: Kevin Buettner , gdb-patches@sources.redhat.com References: <1021223225021.ZM25698@localhost.localdomain> <20021223235639.GA6927@nevyn.them.org> <1021224062810.ZM26995@localhost.localdomain> <20021224145304.GA29615@nevyn.them.org> <1021224192935.ZM27391@localhost.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1021224192935.ZM27391@localhost.localdomain> User-Agent: Mutt/1.5.1i X-SW-Source: 2002-12/txt/msg00670.txt.bz2 On Tue, Dec 24, 2002 at 12:29:35PM -0700, Kevin Buettner wrote: > On Dec 24, 9:53am, Daniel Jacobowitz wrote: > > > > I'll fix the GDBSERVER_DEPFILES and tm-linux64 nits, but the > > > supply_gregset issue will require further discussion. In the interim, > > > how would you like to proceed? > > > > Since it won't affect thread support for 32-bit MIPS, I've no objection > > to committing it now. > > Okay, it's in. In addition to fixing the problems previously discussed, > I found it necessary to change the osabi registration (in mips-linux-tdep.c) > from: > > gdbarch_register_osabi (bfd_arch_mips, 0, GDB_OSABI_LINUX, > mips_linux_init_abi); > > to: > > for (arch_info = bfd_lookup_arch (bfd_arch_mips, 0); > arch_info != NULL; > arch_info = arch_info->next) > { > gdbarch_register_osabi (bfd_arch_mips, arch_info->mach, GDB_OSABI_LINUX, > mips_linux_init_abi); > } > > I'm not entirely happy with this change, but I see no way around it > due to the recent changes to osabi.c. (I'm open to suggestions for > better ways to do it...) OK, that's a problem. In fact it's disgusting... A mach value of 0 is always supposed to mean "default", if I remember my BFD correctly. Has the change to pass a machine of 0 broken osabi support for anything that sets a machine? It looks that way. -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer