Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@redhat.com>
To: gdb-patches@sources.redhat.com
Subject: [rfa/doco] FRAME_FP -> read_fp
Date: Tue, 19 Nov 2002 12:00:00 -0000	[thread overview]
Message-ID: <3DDA9864.8010005@redhat.com> (raw)

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

Hello,

This patch updates the doco so that it better reflects GDB's current 
implementation of create_new_frame().

ok?
Andrew

[-- Attachment #2: diffs --]
[-- Type: text/plain, Size: 942 bytes --]

2002-11-19  Andrew Cagney  <ac131313@redhat.com>

	* gdbint.texinfo (Algorithms): Replace FRAME_FP with read_fp.

Index: gdbint.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdbint.texinfo,v
retrieving revision 1.107
diff -u -r1.107 gdbint.texinfo
--- gdbint.texinfo	26 Oct 2002 17:19:28 -0000	1.107
+++ gdbint.texinfo	19 Nov 2002 19:58:05 -0000
@@ -234,13 +234,13 @@
 and called functions.
 
 @findex create_new_frame
-@vindex FRAME_FP
-@code{FRAME_FP} in the machine description has no meaning to the
+@vindex read_fp
+@code{read_fp} in the machine description has no meaning to the
 machine-independent part of @value{GDBN}, except that it is used when
 setting up a new frame from scratch, as follows:
 
 @smallexample
-create_new_frame (read_register (FP_REGNUM), read_pc ()));
+create_new_frame (read_fp (), read_pc ()));
 @end smallexample
 
 @cindex frame pointer register

             reply	other threads:[~2002-11-19 20:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-19 12:00 Andrew Cagney [this message]
2002-11-19 21:59 ` Eli Zaretskii
2002-11-20  8:26   ` Andrew Cagney
2002-11-20  9:20     ` Eli Zaretskii
2003-01-29 15:49       ` 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=3DDA9864.8010005@redhat.com \
    --to=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