Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: andrew.stubbs@st.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH][SH] info registers
Date: Wed, 16 Nov 2005 16:54:00 -0000	[thread overview]
Message-ID: <200511161618.jAGGItsB021108@elgar.sibelius.xs4all.nl> (raw)
In-Reply-To: <437B556D.2050202@st.com> (message from Andrew STUBBS on Wed, 16 Nov 2005 15:51:09 +0000)

> Date: Wed, 16 Nov 2005 15:51:09 +0000
> From: Andrew STUBBS <andrew.stubbs@st.com>
> 
> Hi,
> 
> sh-tdep.c contains quite a lot of code to implement the 'info registers' 
> command (and friends).
> 
> It has a number of issues:
>   - The double and vector registers are only in hex.
>   - Invalid registers are still printed for some types (not that GDB 
> knows which registers are invalid - that's my next patch).
>   - The double registers are incorrectly named dr0..dr7, and the vector 
> registers incorrectly named fv0..fv3. They should be dr0,dr2,dr4... and 
> fv0,fv4,...
> 
> I have discovered that the default code (when the architecture may 
> override) does everything the SH code does right and yet does not do 
> everything it does wrong. Specifically all the above problems are 
> addressed.
> 
> I therefore propose removing all this garbage entirely.

I'm very much in favour of this, but please wait a week or so with
checking this in to give people who actually use gdb for the SH the
opportunity to object.

Mark


  reply	other threads:[~2005-11-16 16:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-16 16:48 Andrew STUBBS
2005-11-16 16:54 ` Mark Kettenis [this message]
2005-11-23 18:39   ` Andrew STUBBS
2005-11-23 18:39     ` Daniel Jacobowitz
2005-11-23 19:08       ` Andrew STUBBS

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=200511161618.jAGGItsB021108@elgar.sibelius.xs4all.nl \
    --to=mark.kettenis@xs4all.nl \
    --cc=andrew.stubbs@st.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