From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9205 invoked by alias); 19 Nov 2002 20:00:41 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 9198 invoked from network); 19 Nov 2002 20:00:40 -0000 Received: from unknown (HELO localhost.redhat.com) (216.138.202.10) by sources.redhat.com with SMTP; 19 Nov 2002 20:00:40 -0000 Received: from redhat.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id D7BA13E39 for ; Tue, 19 Nov 2002 15:00:36 -0500 (EST) Message-ID: <3DDA9864.8010005@redhat.com> Date: Tue, 19 Nov 2002 12:00:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0.0) Gecko/20020824 X-Accept-Language: en-us, en MIME-Version: 1.0 To: gdb-patches@sources.redhat.com Subject: [rfa/doco] FRAME_FP -> read_fp Content-Type: multipart/mixed; boundary="------------080506090405080704070401" X-SW-Source: 2002-11/txt/msg00492.txt.bz2 This is a multi-part message in MIME format. --------------080506090405080704070401 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-length: 128 Hello, This patch updates the doco so that it better reflects GDB's current implementation of create_new_frame(). ok? Andrew --------------080506090405080704070401 Content-Type: text/plain; name="diffs" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="diffs" Content-length: 942 2002-11-19 Andrew Cagney * 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 --------------080506090405080704070401--