This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
Re: [rfa/doco] FRAME_FP -> read_fp
- From: "Eli Zaretskii" <eliz at is dot elta dot co dot il>
- To: ac131313 at redhat dot com
- Cc: gdb-patches at sources dot redhat dot com
- Date: Wed, 20 Nov 2002 19:20:04 +0300
- Subject: Re: [rfa/doco] FRAME_FP -> read_fp
- References: <Pine.SUN.3.91.1021120075713.24803C-100000@is> <3DDBB787.90007@redhat.com>
- Reply-to: Eli Zaretskii <eliz at is dot elta dot co dot il>
> 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.