From: Eli Zaretskii <eliz@is.elta.co.il>
To: Andrew Cagney <ac131313@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [rfa/doco] FRAME_FP -> read_fp
Date: Tue, 19 Nov 2002 21:59:00 -0000 [thread overview]
Message-ID: <Pine.SUN.3.91.1021120075713.24803C-100000@is> (raw)
In-Reply-To: <3DDA9864.8010005@redhat.com>
On Tue, 19 Nov 2002, Andrew Cagney wrote:
> This patch updates the doco so that it better reflects GDB's current
> implementation of create_new_frame().
>
> ok?
Ahm, what does this mean, exactly, "read_fp in the machine description"?
Isn't read_fp a function? If so, how can it be present ``in the machine
description''?
In case it isn't clear, I refer to this text:
+@code{read_fp} in the machine description has no meaning
next prev parent reply other threads:[~2002-11-20 5:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-19 12:00 Andrew Cagney
2002-11-19 21:59 ` Eli Zaretskii [this message]
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=Pine.SUN.3.91.1021120075713.24803C-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