From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1498 invoked by alias); 17 Jun 2003 13:53:29 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 1307 invoked from network); 17 Jun 2003 13:53:27 -0000 Received: from unknown (HELO localhost.redhat.com) (207.219.125.131) by sources.redhat.com with SMTP; 17 Jun 2003 13:53:27 -0000 Received: from redhat.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 6C27B2B5F; Tue, 17 Jun 2003 09:53:21 -0400 (EDT) Message-ID: <3EEF1D51.7000300@redhat.com> Date: Tue, 17 Jun 2003 13:53:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0.2) Gecko/20030223 X-Accept-Language: en-us, en MIME-Version: 1.0 To: cgd@broadcom.com Cc: drow@mvista.com, gdb@sources.redhat.com Subject: Re: MIPS o32 ABI spec, $fp1 valid? References: <3EEE0E2D.8050805@redhat.com> <20030616185054.GA30776@nevyn.them.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2003-06/txt/msg00334.txt.bz2 Now we're getting somewhere :-) Next question. Does the o32 ABI specify how to spill a loating point register (a spill is different to a double store of a parameter as a spilt register is recovered by the unwind code. mdebug might, for instance, specify something. Andrew >> Co-processor 1 adds 32 32-bit floating-point general registers and a >> 32-bit control/status register. Each even/odd pair of the 32 >> floating-point general registers can be used as either a 32-bit >> single-precision floating-point register or as a 64-bit >> double-precision floating-point register. For single-precision values, >> the even-numbered floating-point register holds the value. For >> double-precision values, the even-numbered floating-point register >> holds the least significant 32 bits of the value and the odd-numbered >> floating-point register holds the most significant 32 bits of the >> value. This is always true, regardless of the byte ordering conventions >> in use ( big endian or little endian). > > > FYI, the above agrees with my reading of Kane (see > http://sources.redhat.com/ml/gdb-patches/2003-06/msg00555.html ). > > The ISBN is 0135847494. it can be found used in lots of places for > approx $10. I paid more for mine 10+ years ago. 8-) > > > >> Which is actually pretty ambiguous, > > > not really at all: "Each even/odd pair... as either _a_ 32-bit ..." > etc. > > Kane makes clear: > > In the following pages, the notation FGR refers to the > FPA's general register 0 through 31, and FPR refers ot > the FPA's floating-point registers (FPR 0 through 30) which > are formed by concatenation of FGR's[sic] (as described in > Chapter 6). > > Chapter 6 really makes quite clear that there are 16 FGRs. > > > > cgd > >