From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27627 invoked by alias); 31 Jan 2003 06:04:13 -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 27619 invoked from network); 31 Jan 2003 06:04:11 -0000 Received: from unknown (HELO localhost.redhat.com) (24.157.209.173) by 172.16.49.205 with SMTP; 31 Jan 2003 06:04:11 -0000 Received: from redhat.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 5DDB73C9D; Fri, 31 Jan 2003 01:04:04 -0500 (EST) Message-ID: <3E3A11D4.2010405@redhat.com> Date: Fri, 31 Jan 2003 06:04:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0.1) Gecko/20021211 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Nick Kelsey Cc: gdb-patches@sources.redhat.com Subject: Re: Sumbitting ip2k port for review. References: <008d01c2a2cb$2c23ce00$0a00a8c0@nkelseyhome> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2003-01/txt/msg00839.txt.bz2 \ > What the ip2k really needs out of the register handling is > - the ability to display a register group (there are about 12 register > groups in the ip2k). > - the ability to obtain a list of the register groups in a general way (for > use with a GUI). > - insight support. See: (gdb) help maint print register-groups > I get the impression that insight is not under strong active development so > if we can leave the registers-structure trick in place then that would > satify the insight requirement. I am quite happy to work with whoever is > driving the changes to the register code so that the ip2k port can make use > of these features. See current insight. >>- ``__'' shouldn't be avoided as a prefix to symbols. A leading `_' is > > reserved for the system's namespace. > > Sorry, i don't quite follow, can you give an example please. The ip2k gcc > port uses an underscore prefix for normal c-code. There are a few symbols > that the linker script creates that gdb needs if the vn is to be used. I > used a double-underscore prefix to avoid name-space issues with c-ode. Your code contained C symbols with a leading `_'. All GDB source code needs to avoid it. Andrew