Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Thomas Schwinge <thomas@codesourcery.com>
To: Kevin Buettner <kevinb@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC] sh-tdep.c: Don't fetch FPSCR register if it doesn't exist
Date: Fri, 02 Mar 2012 09:24:00 -0000	[thread overview]
Message-ID: <87pqcv2w64.fsf@schwinge.name> (raw)
In-Reply-To: <20120301111926.14b1025b@mesquite.lan>

[-- Attachment #1: Type: text/plain, Size: 1397 bytes --]

Hi Kevin!

On Thu, 1 Mar 2012 11:19:26 -0700, Kevin Buettner <kevinb@redhat.com> wrote:
> I think it is still okay because [...]

I agree with your reasoning.


> On Thu, 01 Mar 2012 11:30:13 +0100
> Thomas Schwinge <thomas@codesourcery.com> wrote:
> > Still learning about GDB's code layout -- is there any benefit in
> > invoking gdbarch_register_reggroup_p (as you're doing) in contrast to
> > directly going for sh_register_reggroup_p?
> 
> Well, the way I'm doing it is slower.
> 
> But, if at some point someone were to add another
> `register_reggroup_p' method for some other sh variant (as is the case
> for `register_name'), the code that I wrote will still work.  If I
> called sh_register_reggroup_p directly, then presumably the wrong
> function would be called for that new architecture variant.

Sure, but a person adding a new variant of sh_register_reggroup_p would
surely be checking all places where the current only implementation is
invoked, and decide which is now applicable, the old or the new -- or
simply defer that decision to gdbarch_register_reggroup_p then; so we
might as well do that right now.


> 	* sh-tdep.c (sh_frame_cache): Don't fetch the FPSCR register
> 	unless it exists for this architecture.

Looks good; before committing, you may want to unify spaces/tabs usage
used for indenting the comment.


Grüße,
 Thomas

[-- Attachment #2: Type: application/pgp-signature, Size: 489 bytes --]

  reply	other threads:[~2012-03-02  9:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-01  0:34 Kevin Buettner
2012-03-01  1:33 ` Joel Brobecker
2012-03-01  5:09   ` Kevin Buettner
2012-03-01 10:30     ` Thomas Schwinge
2012-03-01 19:11       ` Kevin Buettner
2012-03-02  9:24         ` Thomas Schwinge [this message]
2012-03-02 13:46           ` Kevin Buettner
2012-03-03  1:29         ` Kevin Buettner
2012-03-01 15:57     ` Joel Brobecker
2012-03-01 19:10       ` Kevin Buettner

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=87pqcv2w64.fsf@schwinge.name \
    --to=thomas@codesourcery.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