Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Kevin Buettner <kevinb@redhat.com>
To: Andrew Cagney <ac131313@cygnus.com>,
	gdb-patches@sources.redhat.com,
	Kevin Buettner <kevinb@redhat.com>
Subject: Re: [patch/rfa:rs6000] Don't use ->prev
Date: Mon, 15 Apr 2002 00:59:00 -0000	[thread overview]
Message-ID: <1020415075921.ZM24483@localhost.localdomain> (raw)
In-Reply-To: Andrew Cagney <ac131313@cygnus.com> "[patch/rfa:rs6000] Don't use ->prev" (Apr 14, 12:52pm)

On Apr 14, 12:52pm, Andrew Cagney wrote:

> The rs6000 has me puzzled. I think the ->frame contains the address of 
> the wrong end of the frame!  If ->frame pointed at the frame's start, 
> the code below wouldn't even be needed.  Anyway, I've changed it to use 
> frame_chain() (I don't see regressions on NetBSD/PPC.  The other 
> possability would be to risk a (recursive) get_prev_frame() call.
> 
> Anyway, is the rs6000 ok?
> 
[...]
> 	* rs6000-tdep.c (frame_get_saved_regs): Use rs6000_frame_chain()
> 	instead of ->prev.

I think that your patch is okay so long as you use FRAME_CHAIN()
instead of rs6000_frame_chain().  Note that FRAME_CHAIN() may be set
to something other than rs6000_frame_chain() depending upon the ABI / OS.

At the moment though, it doesn't really matter too much since the
case -- signal handler trampolines -- that calling FRAME_CHAIN gets
right is broken in frame_get_saved_regs() anyway.  The Linux/PPC
target works around this deficiency by interposing some code which
computes the correct saved register locations for signal handler
callers instead of calling the rs6000_* version which invokes
rs6000_get_saved_register().

Kevin


  reply	other threads:[~2002-04-15  7:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-14  9:52 Andrew Cagney
2002-04-15  0:59 ` Kevin Buettner [this message]
2002-04-19 20:11   ` Andrew Cagney
2002-04-24 15:09 ` Michael Snyder
2002-05-04 18:39   ` Andrew Cagney

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=1020415075921.ZM24483@localhost.localdomain \
    --to=kevinb@redhat.com \
    --cc=ac131313@cygnus.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