From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14634 invoked by alias); 18 Jun 2004 04:07:51 -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 14627 invoked from network); 18 Jun 2004 04:07:50 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org with SMTP; 18 Jun 2004 04:07:50 -0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.12.10/8.12.10) with ESMTP id i5I47oe1023131 for ; Fri, 18 Jun 2004 00:07:50 -0400 Received: from zenia.home.redhat.com (porkchop.devel.redhat.com [172.16.58.2]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id i5I47m028887; Fri, 18 Jun 2004 00:07:49 -0400 To: "Xinan Tang" Cc: Subject: Re: "Info reg doesn't work" References: From: Jim Blandy Date: Fri, 18 Jun 2004 04:07:00 -0000 In-Reply-To: Message-ID: User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2004-06/txt/msg00195.txt.bz2 "Xinan Tang" writes: > Should I go into function _initialize_FOO_tdep() to modify the places > where bfd_arch_arm is used? I haven't done that yet since our target is > similar to arm. Well, you're going to need to choose your own bfd_arch_* value, and use that in the upstream toolchain. Or if your processor is a variant on the ARM, then you'll need to invent your own bfd_mach_arm_* value. Ask on binutils@sources.redhat.com about allocating a bfd_arch or bfd_mach value for your own use. I haven't done this before.