From: Andrew Cagney <ac131313@redhat.com>
To: LaPonsey Brian-ra4951 <Brian.Laponsey@motorola.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: mcore registers
Date: Tue, 30 Sep 2003 14:46:00 -0000 [thread overview]
Message-ID: <3F79974E.4070203@redhat.com> (raw)
In-Reply-To: <15BB35FC418BD511868500D0B7B916B108A35018@zuk07exm02.sps.mot.com>
>> Can you post the output from "maint print registers"? If these
>> registers are last, the stub can send back a short register
>> packet
>
>
> The pc is the last, not cr31 --
Doh!
> (gdb) maint print registers
> cr31 63 63 252 4 int
> pc 64 64 256 4 int
>
>
>
>> longer packet back to the stub). It may also be possible to
>> run length
>> encode (phrase?) the "x" indicating that the the missing
>> registers are
>> not available.
>
>
> I had planned on eventually implementing the run-length encoding (using the '*' symbol). All of the non-existent registers just get reported as containing zeroes, so RLL would compress this consistently. Maybe it's time to get busy on that. I was hoping for a fix that not only improves performance, but also accurately reflects how the mcore is actually built.
Ok. Note that GDB doesn't run length encode. Instead it tries to use
the "P" packet. If not already, also look at the "T..." response to
things like continue.
Andrew
next prev parent reply other threads:[~2003-09-30 14:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-30 8:21 LaPonsey Brian-ra4951
2003-09-30 14:46 ` Andrew Cagney [this message]
2003-09-30 15:34 ` Paul Koning
2003-09-30 15:40 ` Andrew Cagney
-- strict thread matches above, loose matches on Subject: below --
2003-09-30 15:22 LaPonsey Brian-ra4951
2003-09-29 15:17 LaPonsey Brian-ra4951
2003-09-29 17:25 ` Andrew Cagney
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=3F79974E.4070203@redhat.com \
--to=ac131313@redhat.com \
--cc=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