From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11695 invoked by alias); 28 Mar 2005 22:34:28 -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 11425 invoked from network); 28 Mar 2005 22:34:18 -0000 Received: from unknown (HELO priv-edtnes57.telusplanet.net) (199.185.220.220) by sourceware.org with SMTP; 28 Mar 2005 22:34:18 -0000 Received: from takamaka.act-europe.fr ([142.179.108.108]) by priv-edtnes57.telusplanet.net (InterMail vM.6.01.04.00 201-2131-118-20041027) with ESMTP id <20050328223417.ZFIK17716.priv-edtnes57.telusplanet.net@takamaka.act-europe.fr>; Mon, 28 Mar 2005 15:34:17 -0700 Received: by takamaka.act-europe.fr (Postfix, from userid 507) id A7B7647DC0; Mon, 28 Mar 2005 14:34:16 -0800 (PST) Date: Mon, 28 Mar 2005 22:34:00 -0000 From: Joel Brobecker To: Mark Kettenis Cc: gdb-patches@sources.redhat.com Subject: Re: [RFA] Fix problem fetching/setting FSR register (IRIX) Message-ID: <20050328223416.GQ2545@adacore.com> References: <20050326004308.GH2545@adacore.com> <200503260802.j2Q82QHU011664@elgar.sibelius.xs4all.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200503260802.j2Q82QHU011664@elgar.sibelius.xs4all.nl> User-Agent: Mutt/1.4i X-SW-Source: 2005-03/txt/msg00368.txt.bz2 > 2005-03-25 Joel Brobecker > > * irix5-nat.c (supply_fpregset): Fix bug that caused the FSR > register value to be incorrectly written in the regcache. > (fill_fpregset): Fix bug that caused the FSR register value > to be incorrectly read from the regcache. > Fixes [E223-028]. > > Tested on mips-irix. No regression. OK to apply? > > Oh, my message was sort of intended as approval. But now that you > asked again, there's one little nit: what's that funny E223-028. If > it is what I think it is, then I'm not sure if we should add bug ID's > from a non-public bug database to our ChangeLog. Oops. Thanks for catching this. It was a copy/paste error on my part. I made sure I didn't included it in the ChangeLog. > (I will submit a testcase for this asap) > > A somewhat general MIPS floating-point test would be great ;-). Hmmm, the problem is that I am not very good with floats... I'll see what I can do. Thanks, -- Joel