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: Tue, 25 Jun 2013 19:10:00 -0000 [thread overview]
Message-ID: <51C9E48B.7050605@redhat.com> (raw)
In-Reply-To: <C6CA53A2A46BA7469348BDBD663AB6585308FA32@KCHJEXMB02.kpit.com>
On 06/19/2013 02:28 PM, Kaushik Phatak wrote:
> The below gdbserver port has following changes,
> 1. Remove register pair access over remote protocol in the .dat file.
> This allows for matching of the register numbers in the gdbserver with those
> in linux-tdep.c. This was done by simplifying the PTRACE_GETREGS inside kernel
> to read single registers.
> 2. Remove support for "r0r1_orig" register. This is a kernel internal register
> and need not be user visible.
> 3. Set cr16_num_regs to 20 and PC_REGNUM to 16. This will now match the gdb port.
> 4. Add registers pc,usp,ra to the "expedite" set.
> 5. Move the ptrace macro defines like PT_TEXT_ADDR from linux-low.c to the kernel's
> ptrace.h
I'm not clear on point #2, but the rest sounds excellent. Thanks!
> +
> +/* We only place breakpoints in empty marker functions, and thread locking
> + is outside of the function. So rather than importing software single-step,
> + we can just run until exit. */
> +static CORE_ADDR
Add empty line between describing comment and function definition.
> +cr16_reinsert_addr (void)
> +{
> + struct regcache *regcache = get_thread_regcache (current_inferior, 1);
> + unsigned long pc;
> +
> + /* R14/Ra is return address register */
"... is the return ..."
Other than that, this looks good.
--
Pedro Alves
next prev parent reply other threads:[~2013-06-25 18:42 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
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 [this message]
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=51C9E48B.7050605@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