From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4338 invoked by alias); 10 Mar 2002 23:18:08 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 4277 invoked from network); 10 Mar 2002 23:18:07 -0000 Received: from unknown (HELO localhost.redhat.com) (24.112.135.44) by sources.redhat.com with SMTP; 10 Mar 2002 23:18:07 -0000 Received: from cygnus.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 374A03CAA; Sun, 10 Mar 2002 18:18:06 -0500 (EST) Message-ID: <3C8BE9AD.5060300@cygnus.com> Date: Sun, 10 Mar 2002 15:18:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:0.9.8) Gecko/20020210 X-Accept-Language: en-us MIME-Version: 1.0 To: Daniel Jacobowitz Cc: Don Howard , gdb-patches@sources.redhat.com Subject: Re: [RFA] mips: Fix "info registers" output References: <20010619225007.A10141@nevyn.them.org> <20020307165956.A22042@nevyn.them.org> <3C8ABF59.7080908@cygnus.com> <20020310015637.A13373@nevyn.them.org> <3C8B8A11.8070609@cygnus.com> <20020310120037.A29124@nevyn.them.org> <3C8B9C06.9020506@cygnus.com> <20020310143027.A3933@nevyn.them.org> <3C8BC5DB.3040102@cygnus.com> <20020310172609.B9299@nevyn.them.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2002-03/txt/msg00152.txt.bz2 > Right now, for MIPS, builtin_type_double always means "whichever of > builtin_type_ieee_double_{big,little} is appropriate" and likewise > for builtin_type_float. (I note in passing that the type_ieee > variables are not referenced. Anywhere. Only the floatformats are.) Yes, it is a bug. MIPS integer registers have been (mostly?) changed to the correct uint32 et.al. That fixed problems when debugging -mlong64 -mlong32 etc code. > All I could see changed in mips-tdep.c would be to explicitly state > that, and I don't really see the point, given the MIPS FP models we > support. That's why I didn't see the need for the FIXME in question. > Perhaps I'm not understanding you...? It is one of those things where the ``right thing'' may not appear to have an immediate return. enjoy, Andrew