From: LaPonsey Brian-ra4951 <Brian.Laponsey@motorola.com>
To: gdb-patches@sources.redhat.com
Subject: mcore registers
Date: Mon, 29 Sep 2003 15:17:00 -0000 [thread overview]
Message-ID: <15BB35FC418BD511868500D0B7B916B108A35017@zuk07exm02.sps.mot.com> (raw)
I have written a gdb stub for mcore-elf, and in my efforts to improve it I have noticed that gdb defines too many control registers for the mcore chip. Despite having a 5-bit field in the control register move instructions, there are not actually 32 control registers on the mcore. All the existing mcore designs, either current or planned, have only 13 control registers. The gdb source code defines all 32, but cr13..cr31 don't actually exist.
It speeds up the stub not to have to report the status of these phantom registers over the serial line. Patching them out of gdb also allows the stub to keep its RAM requirement below 1K.
My question is, would it be advisable to make this change to the gdb mainline? I realize that there will always be unintended consequences of such a patch. Any thoughts?
Regards,
--
Brian LaPonsey
Motorola Semiconductor
next reply other threads:[~2003-09-29 15:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-29 15:17 LaPonsey Brian-ra4951 [this message]
2003-09-29 17:25 ` Andrew Cagney
2003-09-30 8:21 LaPonsey Brian-ra4951
2003-09-30 14:46 ` Andrew Cagney
2003-09-30 15:34 ` Paul Koning
2003-09-30 15:40 ` Andrew Cagney
2003-09-30 15:22 LaPonsey Brian-ra4951
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=15BB35FC418BD511868500D0B7B916B108A35017@zuk07exm02.sps.mot.com \
--to=brian.laponsey@motorola.com \
--cc=gdb-patches@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox