From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26679 invoked by alias); 6 Aug 2002 01:41:54 -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 26659 invoked from network); 6 Aug 2002 01:41:53 -0000 Received: from unknown (HELO cygnus.com) (205.180.83.203) by sources.redhat.com with SMTP; 6 Aug 2002 01:41:53 -0000 Received: from redhat.com (reddwarf.sfbay.redhat.com [172.16.24.50]) by runyon.cygnus.com (8.8.7-cygnus/8.8.7) with ESMTP id SAA07476; Mon, 5 Aug 2002 18:40:16 -0700 (PDT) Message-ID: <3D4F2501.491DA0E9@redhat.com> Date: Mon, 05 Aug 2002 18:41:00 -0000 From: Michael Snyder Organization: Red Hat, Inc. X-Accept-Language: en MIME-Version: 1.0 To: gdb-patches@sources.redhat.com CC: cagney@redhat.com, jimb@redhat.com, kevinb@redhat.com Subject: [RFC] Mips, saving / restoring FP regs? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-SW-Source: 2002-08/txt/msg00108.txt.bz2 I see that mips_push_dummy_frame saves the state of the FP registers, but mips_pop_frame does not appear to restore them. Is there any reason for that? It restores FPCSR, but not the FP regs themselves. This of course causes about 5 fails in callfuncs.exp, when we try to make sure that the registers are unchanged accross a target function call. Michael