From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-patches-return-12623-listarch-gdb-patches=sourceware.cygnus.com@sources.redhat.com>
Received: (qmail 18769 invoked by alias); 8 Feb 2002 17:29:31 -0000
Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm
Precedence: bulk
List-Subscribe: <mailto:gdb-patches-subscribe@sources.redhat.com>
List-Archive: <http://sources.redhat.com/ml/gdb-patches/>
List-Post: <mailto:gdb-patches@sources.redhat.com>
List-Help: <mailto:gdb-patches-help@sources.redhat.com>, <http://sources.redhat.com/ml/#faqs>
Sender: gdb-patches-owner@sources.redhat.com
Received: (qmail 18710 invoked from network); 8 Feb 2002 17:29:26 -0000
Received: from unknown (HELO localhost.redhat.com) (24.114.26.18)
  by sources.redhat.com with SMTP; 8 Feb 2002 17:29:26 -0000
Received: from cygnus.com (localhost [127.0.0.1])
	by localhost.redhat.com (Postfix) with ESMTP
	id 186BD3E77; Fri,  8 Feb 2002 12:29:25 -0500 (EST)
Message-ID: <3C640AF4.7040300@cygnus.com>
Date: Fri, 08 Feb 2002 09:29:00 -0000
From: Andrew Cagney <ac131313@cygnus.com>
User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:0.9.7) Gecko/20020103
X-Accept-Language: en-us
MIME-Version: 1.0
To: Richard.Earnshaw@arm.com, Daniel Jacobowitz <drow@mvista.com>
Cc: gdb-patches@sources.redhat.com,
	Corinna Vinschen <vinschen@redhat.com>
Subject: Re: ARM float changes
References: <200202081713.RAA08910@cam-mail2.cambridge.arm.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-SW-Source: 2002-02/txt/msg00238.txt.bz2

> For instance, my results on i386-linux, callfuncs.exp:
>> standard coercion			default coercion
>> =================			================
>> 
>> GCC 2.95
>> stabs+	1 XPASS, 1 FAIL, 1 XFAIL	1 FAIL, 2 XPASS
>> dwarf2	1 FAIL				5 FAIL
>> 
>> GCC 3.0.4pre
>> stabs+	1 XPASS, 1 XFAIL		2 XPASS
>> dwarf2	0 FAILS				4 FAIL
>> 
> 
> 
> So doesn't all this mean that the coercion model should be selected based 
> on the debug-info type?  Can we do that dynamically in the back-end?


I suspect, in truth the target should never have even been allowed to 
enter the picture.  The core of GDB should have set a policy based on 
debug info and then stuck with it.

The change at least makes things consistent with other modern targets. 
 From memory the comment that goes with standard_...() hints strongly 
that no target should ever be using default_...().

I think this illustrates my contention that GDB should bite the bullet 
and ``break'' some targets but fix the problem.

I can always make the next release 6.0 :-^

enjoy,
Andrew