From: Pedro Alves <palves@redhat.com>
To: Kaushik Phatak <Kaushik.Phatak@kpitcummins.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [RFA 4/5] New port: CR16: gdbserver
Date: Wed, 23 Jan 2013 13:29:00 -0000 [thread overview]
Message-ID: <50FFE596.20303@redhat.com> (raw)
In-Reply-To: <C6CA53A2A46BA7469348BDBD663AB65848578991@KCHJEXMB02.kpit.com>
On 01/23/2013 12:50 PM, Kaushik Phatak wrote:
>> You mean additional code in gdbserver, or in the kernel? I'd think the
>> former.
> Yes, the code changes would be for gdbserver and gdb.
> I would prefer to keep my kernel code changes to a minimal.
>
>> always expose the registers as pairs in the remote protocol,
>> and then implement the user visible non-paired registers in
>> GDB as pseudo registers (and hide the pairs). IOW, your .dat
>> file would stay the same, and gdbserver wouldn't change. GDB's
>> core cr16 register numbers would be decoupled from the RSP
>> register set.
> Yes, I agree. Disturbing the .dat file is causing issues in the
> remote protocol.
What issues? Can you be more specific?
> So, using pseudo registers within gdb would be a
> better way to proceed as long as I can get the register numbers to
> match my expedite register numbers.
--
Pedro Alves
next prev parent reply other threads:[~2013-01-23 13:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-04 10:23 Kaushik Phatak
2012-12-14 18:47 ` Pedro Alves
2012-12-28 4:42 ` Kaushik Phatak
2013-01-18 16:39 ` Pedro Alves
2013-01-22 13:43 ` Kaushik Phatak
2013-01-22 15:05 ` Pedro Alves
2013-01-23 12:50 ` Kaushik Phatak
2013-01-23 13:29 ` Pedro Alves [this message]
2013-01-23 14:04 ` Kaushik Phatak
2013-01-23 14:44 ` Pedro Alves
2013-06-19 14:10 ` Kaushik Phatak
2013-06-25 19:10 ` Pedro Alves
2013-06-26 8:03 ` Kaushik Phatak
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=50FFE596.20303@redhat.com \
--to=palves@redhat.com \
--cc=Kaushik.Phatak@kpitcummins.com \
--cc=gdb-patches@sourceware.org \
/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