From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-patches-return-22059-listarch-gdb-patches=sources.redhat.com@sources.redhat.com>
Received: (qmail 18779 invoked by alias); 29 Jan 2003 15:49:31 -0000
Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm
Precedence: bulk
List-Subscribe: <mailto:gdb-patches-subscribe@sources.redhat.com>
List-Archive: <http://sources.redhat.com/ml/gdb-patches/>
List-Post: <mailto:gdb-patches@sources.redhat.com>
List-Help: <mailto:gdb-patches-help@sources.redhat.com>, <http://sources.redhat.com/ml/#faqs>
Sender: gdb-patches-owner@sources.redhat.com
Received: (qmail 18770 invoked from network); 29 Jan 2003 15:49:31 -0000
Received: from unknown (HELO localhost.redhat.com) (172.16.49.200)
  by 172.16.49.205 with SMTP; 29 Jan 2003 15:49:31 -0000
Received: from redhat.com (localhost [127.0.0.1])
	by localhost.redhat.com (Postfix) with ESMTP
	id EFE1A406C; Tue, 28 Jan 2003 19:22:49 -0500 (EST)
Message-ID: <3E371ED9.2090605@redhat.com>
Date: Wed, 29 Jan 2003 15:49:00 -0000
From: Andrew Cagney <ac131313@redhat.com>
User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0.1) Gecko/20021211
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [rfa/doco] FRAME_FP -> read_fp
References: <Pine.SUN.3.91.1021120075713.24803C-100000@is> <3DDBB787.90007@redhat.com> <2593-Wed20Nov2002192004+0200-eliz@is.elta.co.il>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-SW-Source: 2003-01/txt/msg00774.txt.bz2

Really old thread:

Eli, I'm dropping this patch.  Instead, I'm doing the full rewrite.

Andrew

>> 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.
>