Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Andrew STUBBS <andrew.stubbs@st.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [SH] PATCH: Define the register groups
Date: Fri, 20 Jan 2006 23:35:00 -0000	[thread overview]
Message-ID: <20060120233520.GJ21181@nevyn.them.org> (raw)
In-Reply-To: <436F6CF7.1070003@st.com>

On Mon, Nov 07, 2005 at 03:04:23PM +0000, Andrew STUBBS wrote:
> 	* sh-tdep.c: Include reggroups.h.
> 	(sh_register_reggroup_p): New function.
> 	(sh_gdbarch_init): Add call to set_gdbarch_register_reggroup_p.
> 	* Makefile.in (sh-tdep.o): Add dependency on reggroups.h.

Just a couple of questions for you, only one of which involves changing
anything:

  - Are the fv registers for floating point vectors?  Since you
    put them in both info float and info vector.  I'm guessing that
    they are.  Makes sense.

  - Can we reuse default_register_reggroup_p for most of this, and
    just handle the register numbers that it's likely to get
    wrong?  e.g. we probably do need to handle FPUL here - but
    calling the default will handle dr0 just fine.

  - You've put a bunch of registers in system_reggroup (e.g. pc, pr)
    that other folks don't; but no one besides the TUI uses that
    anyway, so it doesn't really matter.  I wouldn't have included
    those two.  I don't remember what the other ones you listed do,
    so I've got no idea about them :-)

-- 
Daniel Jacobowitz
CodeSourcery


  parent reply	other threads:[~2006-01-20 23:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-28 18:03 Andrew STUBBS
2005-11-07 18:57 ` Andrew STUBBS
2006-01-12 12:39   ` Andrew STUBBS
2006-01-20 23:35   ` Daniel Jacobowitz [this message]
2006-01-23 15:51     ` Andrew STUBBS
2006-01-23 16:07       ` Daniel Jacobowitz
2006-01-23 17:35         ` 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=20060120233520.GJ21181@nevyn.them.org \
    --to=drow@false.org \
    --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