From: "Eli Zaretskii" <eliz@is.elta.co.il>
To: ac131313@redhat.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: [rfa/doco] FRAME_FP -> read_fp
Date: Wed, 20 Nov 2002 09:20:00 -0000 [thread overview]
Message-ID: <2593-Wed20Nov2002192004+0200-eliz@is.elta.co.il> (raw)
In-Reply-To: <3DDBB787.90007@redhat.com> (message from Andrew Cagney on Wed, 20 Nov 2002 11:25:43 -0500)
> Date: Wed, 20 Nov 2002 11:25:43 -0500
> From: Andrew Cagney <ac131313@redhat.com>
> >
> > 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''?
>
> regcache.c contains:
>
> CORE_ADDR
> read_fp (void)
> {
> return TARGET_READ_FP ();
> }
>
> and TARGET_READ_FP() is part of the machine description (a.k.a.
> architecture vector).
Yes, but still I find it confusing to tell that a function is in the
machine description. A machine description is a bunch of macros and
machine-specific functions, right? And read_fp is neither of these,
right?
> Hmm, I guess this could do with a similar s/FP_REGNUM/read_fp/
> transformation?
Probably.
next prev parent reply other threads:[~2002-11-20 17:20 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
2002-11-20 8:26 ` Andrew Cagney
2002-11-20 9:20 ` Eli Zaretskii [this message]
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=2593-Wed20Nov2002192004+0200-eliz@is.elta.co.il \
--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