From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18553 invoked by alias); 13 Dec 2002 17:15:22 -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 18535 invoked from network); 13 Dec 2002 17:15:11 -0000 Received: from unknown (HELO sccrmhc01.attbi.com) (204.127.202.61) by sources.redhat.com with SMTP; 13 Dec 2002 17:15:11 -0000 Received: from nkelseyhome (12-235-58-117.client.attbi.com[12.235.58.117]) by sccrmhc01.attbi.com (sccrmhc01) with SMTP id <2002121317151000100q3m8se>; Fri, 13 Dec 2002 17:15:10 +0000 Message-ID: <008d01c2a2cb$2c23ce00$0a00a8c0@nkelseyhome> From: "Nick Kelsey" To: "Andrew Cagney" Cc: Subject: Re: Sumbitting ip2k port for review. Date: Fri, 13 Dec 2002 09:58:00 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-SW-Source: 2002-12/txt/msg00420.txt.bz2 Re: Sumbitting ip2k port for review. From: Andrew Cagney To: Nick Kelsey Cc: gdb-patches at sources dot redhat dot com Date: Wed, 11 Dec 2002 19:01:37 -0500 Subject: Re: Sumbitting ip2k port for review. >The other question is who contributed to this work? `Java at silicondust' appears to have being doing some stuff >(or is that your alter ego?). I believe David Taylor may have also worked on the file ip2k-tdep.c in the past? I >know that the problems he encountered with the ip2k were one of the motivations behind overhauling pseudo->registers. jafa at silicondust is me also. Rigisters, right. The ip2k has a lot of registers (about 384) and many of them need to be combined and processed to give a useful user display. If you take a took at ip2k-registers.h and remote-ip2k.c you will see the current hack - a dummy memory address that the remote back-end builds to display registers formatted nicely so they can be type-casted as a multi-level structure (looks great in insight as the nodes can be colasped). 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. 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. >- ``__'' 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. >Andrew Thanks Nick