Re: Sumbitting ip2k port for review.

["Nick Kelsey" <nickk@ubicom.com>]

Re: Sumbitting ip2k port for review.
From: Andrew Cagney <ac131313 at redhat dot com>
To: Nick Kelsey <nickk at ubicom dot com>
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