From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24217 invoked by alias); 21 Jun 2007 17:44:22 -0000 Received: (qmail 24205 invoked by uid 22791); 21 Jun 2007 17:44:22 -0000 X-Spam-Check-By: sourceware.org Received: from NaN.false.org (HELO nan.false.org) (208.75.86.248) by sourceware.org (qpsmtpd/0.31) with ESMTP; Thu, 21 Jun 2007 17:44:19 +0000 Received: from nan.false.org (localhost [127.0.0.1]) by nan.false.org (Postfix) with ESMTP id A727398301; Thu, 21 Jun 2007 17:44:17 +0000 (GMT) Received: from caradoc.them.org (22.svnf5.xdsl.nauticom.net [209.195.183.55]) by nan.false.org (Postfix) with ESMTP id 5CE28982FF; Thu, 21 Jun 2007 17:44:17 +0000 (GMT) Received: from drow by caradoc.them.org with local (Exim 4.67) (envelope-from ) id 1I1Qhs-0005mT-RS; Thu, 21 Jun 2007 13:44:32 -0400 Date: Thu, 21 Jun 2007 17:44:00 -0000 From: Daniel Jacobowitz To: Joern Rennecke Cc: gdb@sourceware.org Subject: Re: How do I replace DEPRECATED_TM_FILE? Message-ID: <20070621174432.GA22192@caradoc.them.org> Mail-Followup-To: Joern Rennecke , gdb@sourceware.org References: <20070621161305.GD8169@elsdt-razorfish.arc.com> <20070621162152.GA18158@caradoc.them.org> <20070621173342.GE8169@elsdt-razorfish.arc.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070621173342.GE8169@elsdt-razorfish.arc.com> User-Agent: Mutt/1.5.15 (2007-04-09) X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2007-06/txt/msg00176.txt.bz2 On Thu, Jun 21, 2007 at 06:33:42PM +0100, Joern Rennecke wrote: > except for ARC_RET_REGNUM and ARC_ORIG_R8_REGNUM, these registers > exist also for the embedded target, but with different numbers; > the embedded target allos access to numerous extra auxilary registers. Which registers are available to talk to is a property of the target; you might want to look at target descriptions, which have been my project for the last year or two. Which ones a DWARF number refers to are a gdbarch property. > > That determines the answer to your question. If it's the dwarf2 > > mapping, for instance, you'd put overrides in an OS/ABI sniffer in the > > Linux tdep file. > > > > I've done a lot of work lately to isolate GDB's internal register > > numbering from various external numberings. You can probably use the > > same internal registers in most places now. > > Another difference is the osabi setting. arc_gdbarch_init also calls > different functions for the different subtargtes to set a number of other > settings. No, I mean, you use the OSABI setting to determine which set of dwarf registers you mean. I don't know what you meant by "another difference is the OSABI setting"; you should not be setting the OSABI in your arc_gdbarch_init, you should be using the normal sniffers and letting gdbarch_init_osabi dispatch appropriately. -- Daniel Jacobowitz CodeSourcery