This is the mail archive of the
gdb@sourceware.cygnus.com
mailing list for the GDB project.
developing mpc860 stub
- To: gdb at sourceware dot cygnus dot com
- Subject: developing mpc860 stub
- From: Quality Quorum <qqi at world dot std dot com>
- Date: Tue, 1 Feb 2000 01:12:07 -0500 (EST)
Hi,
I am developing mpc860 stub (sort of), I have a requirement to
support extended set of SPR registers. It seems like one can
execute "processor" command to set a particular processor model
and corresponding extended registers.
However, it seems to me that mpc860 has too many unimplmented
registers defined: total is 165 registers out of which 73 (44%)
are unimplemented (fp0-31, mq, sr0-15, ibat-dbat, asr, sdr1, dabr,
and ear). Unfortunately there is no example of supporting extended
register set.
I have a few questions in this respect:
1. Is my understanding correct ?
2. Does this feature really work on the gdb side ?
3. Is it OK fora a stub to spit out 165 registers, while gdb
expects only 71 (say gdb side did not execute "processor xxx") ?
4. Is it OK do dump that many unimplemented regs on the screen by `info
reg' ?
5. Is it a good idea to require gdb-4.18 or later and use 'x' to encode
unavailable nibbles ?
Thanks,
Aleksey