Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Maciej W. Rozycki" <macro@mips.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sourceware.org, Chris Dearman <chris@mips.com>,
	     "Maciej W. Rozycki" <macro@linux-mips.org>
Subject: Re: mips-tdep.c: Fix retrieval of the virtual frame pointer
Date: Fri, 28 Sep 2007 18:14:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.61.0709281908410.670@perivale.mips.com> (raw)
In-Reply-To: <20070928175657.GA20487@caradoc.them.org>

On Fri, 28 Sep 2007, Daniel Jacobowitz wrote:

> Have I mentioned that I have queued patches I haven't gotten to yet?
> :-)  I spent the past two weeks fighting with an obstinate qemu, and
> one of the patches I was testing was basically this one.

 I see...

> Mine was:
> 
> +/* Dummy virtual frame pointer method.  This is no more or less accurate
> +   than most other architectures; we just need to be explicit about it,
> +   because the pseudo-register gdbarch_sp_regnum will otherwise lead to
> +   an assertion failure.  */
> +
> +static void
> +mips_virtual_frame_pointer (CORE_ADDR pc, int *reg, LONGEST *offset)
> +{
> +  *reg = MIPS_SP_REGNUM;
> +  *offset = 0;
> +}
> 
> I think this is more accurate than yours, since these:

 You mean simpler?  No argument.

> > +  if (gdbarch_deprecated_fp_regnum (current_gdbarch) >= 0)
> 
> > +  else if (MIPS_SP_REGNUM >= 0)
> 
> are both constants for MIPS.

 Well, this may change in theory, but I know of no plans to do that, so 
shall I replace Chris's patch with yours and test it and you will commit 
it shortly?

  Maciej


  reply	other threads:[~2007-09-28 18:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-28 17:46 Maciej W. Rozycki
2007-09-28 17:57 ` Daniel Jacobowitz
2007-09-28 18:14   ` Maciej W. Rozycki [this message]
2007-09-28 18:19     ` Daniel Jacobowitz
2007-10-01 11:27       ` Maciej W. Rozycki

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=Pine.LNX.4.61.0709281908410.670@perivale.mips.com \
    --to=macro@mips.com \
    --cc=chris@mips.com \
    --cc=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    --cc=macro@linux-mips.org \
    /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