From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25583 invoked by alias); 1 Jun 2002 22:33:10 -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 25575 invoked from network); 1 Jun 2002 22:33:10 -0000 Received: from unknown (HELO localhost.redhat.com) (24.112.240.27) by sources.redhat.com with SMTP; 1 Jun 2002 22:33:10 -0000 Received: from cygnus.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 0EDCA3E5E; Sat, 1 Jun 2002 18:33:19 -0400 (EDT) Message-ID: <3CF94BAE.7000506@cygnus.com> Date: Sat, 01 Jun 2002 15:33:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0rc3) Gecko/20020530 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Peter Barada Cc: gdb@sources.redhat.com Subject: Re: support for different sized FPU registers References: <200205292217.g4TMH7300610@hyper.wm.sps.mot.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2002-06/txt/msg00003.txt.bz2 > I'm trying to add GDB remote support for the ColdFire v4e, and I'm > running into problems with the FPU register definitions. > > On the ColdFire v4e, the FPU registers are 64 bit, but the gdb is > expecting 96 bit register values from a 68881. As a result I'm > getting some 'Remote reply is too short' messages from gdb when the > stub responds to a 'g' packet and on the host the register contents > are all wrong(from 'info reg'). > > What's the best way of telling gdb(for the coldfire portion of a > m68k-elf configured build) that the FPU registers are only 64 bits > instead of 96)? I still want this configuration to support 040s and > 060s which have the 96 bit FPU registers as well as a ColdFire's 64 > bit FPU registers... The most immediate thing that is needed is for the m68k family to be up-dated to the new multi-arch framework. Once that is done, handling both a coldfire and an m68k is fairly mechanical. Check other targets such as PPC, xstormy16, mn10300 et.al. for examples. Do you have an FSF assignment in place? Andrew