Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Hui Zhu <teawater@gmail.com>
To: Kevin Buettner <kevinb@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA/RFC] mips tracepoint: fix Bug 12013
Date: Wed, 22 Dec 2010 07:12:00 -0000	[thread overview]
Message-ID: <AANLkTiknF-96c3Q4YtYJEAg9sJa1EMUZMo9n5HiXR+Fz@mail.gmail.com> (raw)
In-Reply-To: <20101221230428.43315eea@mesquite.lan>

On Wed, Dec 22, 2010 at 14:04, Kevin Buettner <kevinb@redhat.com> wrote:
> On Tue, 21 Dec 2010 23:58:29 +0800
> Hui Zhu <teawater@gmail.com> wrote:
>
>> Thanks.  Do you think I can add a special name for these raw registers
>> then other part can use this raw register if need.
>
> I have a hunch that such an approach will result in an assertion
> failure in mips_print_registers_info() when a raw register name is
> used to attempt to print a register.
>
> The other problem with such an approach is that it again exposes the
> raw registers to the user.  In this case, instead of using the name
> "sp", the user would instead have to use "raw-sp" (or some such).
> This is not completely horrible, but it's certainly not as nice as
> allowing the user to continue referring to standard nomenclature when
> using the trace machinery.
>
> You might consider implementing a new gdbarch method which provides a
> mapping from pseudo register numbers to raw register numbers.  The
> trace machinery could use such a mapping to find the corresponding raw
> register(s) when presented with a pseudo register.  I can think of
> several potential pitfalls with this approach, but I think the idea is
> worth exploring.
>
> Kevin
>

Thanks Kevin.  I will do it.

And I make a patch to add some comments from your mail to mips_register_name.
Wish it can help other people.

Please help me review it.

Thanks,
Hui

2010-12-22  Hui Zhu  <teawater@gmail.com>

	* mips-tedp.c (mips_register_name): Add comments.

---
 mips-tdep.c |    7 ++++++-
 1 file changed, 6 insertions(+), 1 deletion(-)

--- a/mips-tdep.c
+++ b/mips-tdep.c
@@ -454,7 +454,12 @@ mips_register_name (struct gdbarch *gdba
   enum mips_abi abi = mips_abi (gdbarch);

   /* Map [gdbarch_num_regs .. 2*gdbarch_num_regs) onto the raw registers,
-     but then don't make the raw register names visible.  */
+     but then don't make the raw register names visible.
+     Because It is possible to debug a 64-bit device using a 32-bit programming
+     model.  In such instances, the raw registers are configured to be
+     64-bits wide, while the pseudo registers are configured to be 32-bits
+     wide.  The registers that the user sees - the pseudo registers - match
+     the user's expectations given the programming model being used.  */
   int rawnum = regno % gdbarch_num_regs (gdbarch);
   if (regno < gdbarch_num_regs (gdbarch))
     return "";


  reply	other threads:[~2010-12-22  7:12 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-19  8:36 Hui Zhu
2010-12-19 10:39 ` Mark Kettenis
2010-12-19 12:16   ` Hui Zhu
2010-12-21 14:45     ` Hui Zhu
2010-12-21 14:58       ` Mark Kettenis
2010-12-21 15:09         ` Hui Zhu
2010-12-21 15:42     ` Kevin Buettner
2010-12-21 15:59       ` Hui Zhu
2010-12-22  6:04         ` Kevin Buettner
2010-12-22  7:12           ` Hui Zhu [this message]
2010-12-22 16:20             ` Kevin Buettner
2010-12-23  3:33               ` Hui Zhu
2010-12-27 13:20                 ` Hui Zhu
2010-12-27 13:56                   ` Joel Brobecker
2010-12-28  4:43                     ` Hui Zhu
2010-12-22 11:27           ` Pedro Alves
2010-12-25 19:10             ` Hui Zhu
2010-12-27 13:52               ` Pedro Alves
2010-12-28  9:52                 ` Hui Zhu
2010-12-28 10:30                   ` Pedro Alves
2010-12-28 17:09                     ` Hui Zhu
2010-12-28 18:04                       ` Joel Brobecker
2010-12-28 19:05                         ` Pedro Alves
2010-12-28 19:07                           ` Pedro Alves
2010-12-29  8:10                             ` Hui Zhu
2010-12-29 13:06                               ` Pedro Alves
2010-12-29 16:09                                 ` Hui Zhu
2010-12-29 17:57                                   ` Pedro Alves
2010-12-30  8:00                                     ` Hui Zhu

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=AANLkTiknF-96c3Q4YtYJEAg9sJa1EMUZMo9n5HiXR+Fz@mail.gmail.com \
    --to=teawater@gmail.com \
    --cc=gdb-patches@sourceware.org \
    --cc=kevinb@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