Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@is.elta.co.il>
To: Andrew Cagney <ac131313@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch/rfc] FRAME_FP() -> get_frame_base()
Date: Tue, 19 Nov 2002 21:56:00 -0000	[thread overview]
Message-ID: <Pine.SUN.3.91.1021120075531.24803B-100000@is> (raw)
In-Reply-To: <3DDA9741.4050001@redhat.com>


On Tue, 19 Nov 2002, Andrew Cagney wrote:

> There will be several follow-on patches:
> - replace any occurance of frame->frame with get_frame_base(frame)
> - delete the identical default_frame_address(), replacing all references 
> with get_frame_base().
> - (I guess) re-vamp the PPC so that get_frame_base() is constant through 
> out the lifetime of a frame.

I presume some patch to gdbint.texinfo should also follow, right?


  reply	other threads:[~2002-11-20  5:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-19 11:55 Andrew Cagney
2002-11-19 21:56 ` Eli Zaretskii [this message]
2002-11-20  8:26   ` Andrew Cagney
2002-11-20 13:38 ` Kevin Buettner
2002-11-20 18:26   ` Andrew Cagney
2002-11-22 17:32 ` Andrew Cagney
2002-11-24 10:46 ` Andrew Cagney
2002-11-24 15:06   ` muller

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.SUN.3.91.1021120075531.24803B-100000@is \
    --to=eliz@is.elta.co.il \
    --cc=ac131313@redhat.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