Hi Pedro,

I was wondering if you good give some feedback on something I am trying
to do.  Basically, I am working on gdbserver for powerpc-lynx178.
Version 178 of LynxOS is based on an older version of LynxOS where XCOFF
is still in use.  The object format is actually identical to the one
used on AIX.

The problem is that GDB and GDBserver use different register numberings.
On the target side, the register number is the same as the ones we see
on versions 4.x and 5.x. But on the GDB side, because the objfect format
is the same as on AIX, the architecture ends up being set to
"rs6000:6000" (instead of "powerpc:common"). As a result, there are
a few discrepancies in terms of a couple of registers ("fpscr" is the
one that attracted my attention).

So, my idea was to have GDBserver tell GDB what the number is.
Unlike what I am seeing on x86 targets, I don't think we need
anything fancy because, for now, the register map is completely
static. So we don't need to configure the register map besides
setting it at initialization (init_registers_powerpc_32).

The first thing I did was update rs6000-tdep.c so that GDB would
ask for xmlRegister support. And to my surprise, that was almost
enough to get things working. All I had to do next was to update
configure.tgt to include the appropriate XML files, and things
started working. I thought I would have to confirm support for
xmlRegister first, but it looks like it's not the case.

Can you tell me what you think of the following patch? Am I going
to need to do something a little more elaborate, for instance?
I am also worrying about breaking other power targets, but I hope
not. Hopefully GDB sends a qXfer:features:read:target.xml packet,
gets an error, and falls back to the default architecture...

Thanks!
-- 
Joel