From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: ysato@users.sourceforge.jp
Cc: palves@redhat.com, gdb-patches@sourceware.org
Subject: Re: [PATCH] h8300 "info registers" broken
Date: Wed, 05 Feb 2014 17:59:00 -0000 [thread overview]
Message-ID: <201402051759.s15Hx0JB002993@glazunov.sibelius.xs4all.nl> (raw)
In-Reply-To: <878utpfnxs.wl%ysato@users.sourceforge.jp> (message from Yoshinori Sato on Thu, 06 Feb 2014 02:51:11 +0900)
> Date: Thu, 06 Feb 2014 02:51:11 +0900
> From: Yoshinori Sato <ysato@users.sourceforge.jp>
> > Can you explain the patch to me a little bit more, please?
> > It's not obvious to me at all what the register names
> > have to with the proposed change.
>
> Current h8300-tdep have two problems.
> 1. Size mismatch in pseudo register vs raw register.
> So overflow on register cache.
That doesn't make sense. Pseudo registers don't live in the register
cache. Instead they are synthesised from the contents of the register
cache.
> 2. Undisplay pseudo regsters.
Not sure what you're trying to say here. But if you don't want to
show a pseudo register, why do you have it in the first place?
next prev parent reply other threads:[~2014-02-05 17:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-01 12:43 Yoshinori Sato
2014-02-04 19:38 ` Pedro Alves
2014-02-05 17:51 ` Yoshinori Sato
2014-02-05 17:59 ` Mark Kettenis [this message]
2014-02-08 18:36 ` Yoshinori Sato
2014-02-10 15:53 ` Pedro Alves
2014-02-11 10:29 ` Yoshinori Sato
2014-02-11 11:47 ` Pedro Alves
2014-02-11 13:11 ` Yoshinori Sato
2014-02-12 12:42 ` [PATCH 0/2] H8/300: Fix registers Pedro Alves
2014-02-12 12:42 ` [PATCH 2/2] H8/300: Fix pseudo registers reads/writes Pedro Alves
2014-02-12 12:59 ` Mark Kettenis
2014-02-12 12:42 ` [PATCH 1/2] H8/300: Fix gdb<->sim register mapping Pedro Alves
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=201402051759.s15Hx0JB002993@glazunov.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--cc=ysato@users.sourceforge.jp \
/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