From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23457 invoked by alias); 8 Feb 2002 17:35:22 -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 23404 invoked from network); 8 Feb 2002 17:35:21 -0000 Received: from unknown (HELO nevyn.them.org) (128.2.145.6) by sources.redhat.com with SMTP; 8 Feb 2002 17:35:21 -0000 Received: from drow by nevyn.them.org with local (Exim 3.34 #1 (Debian)) id 16ZEvd-0006Eo-00; Fri, 08 Feb 2002 12:35:17 -0500 Date: Fri, 08 Feb 2002 09:35:00 -0000 From: Daniel Jacobowitz To: Andrew Cagney Cc: Richard.Earnshaw@arm.com, gdb-patches@sources.redhat.com, Corinna Vinschen Subject: Re: ARM float changes Message-ID: <20020208123517.A23880@nevyn.them.org> Mail-Followup-To: Andrew Cagney , Richard.Earnshaw@arm.com, gdb-patches@sources.redhat.com, Corinna Vinschen References: <200202081713.RAA08910@cam-mail2.cambridge.arm.com> <3C640AF4.7040300@cygnus.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3C640AF4.7040300@cygnus.com> User-Agent: Mutt/1.3.23i X-SW-Source: 2002-02/txt/msg00241.txt.bz2 On Fri, Feb 08, 2002 at 12:29:24PM -0500, Andrew Cagney wrote: > >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. See my comment on gdb@ about this just now. While standard appears to be the way to go for DWARF-2, the right solution for stabs just seems to be pretending we always have a prototype. I'll look over what various targets actually set this to... dealing with setting it based on debug info is somewhat dubious, since debug info may be mixed in the same objfile. > I can always make the next release 6.0 :-^ :) -- Daniel Jacobowitz Carnegie Mellon University MontaVista Software Debian GNU/Linux Developer