From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3851 invoked by alias); 17 Feb 2002 16:57:01 -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 3776 invoked from network); 17 Feb 2002 16:57:00 -0000 Received: from unknown (HELO localhost.redhat.com) (24.112.135.44) by sources.redhat.com with SMTP; 17 Feb 2002 16:57:00 -0000 Received: from cygnus.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 9514C3D04; Sun, 17 Feb 2002 11:57:00 -0500 (EST) Message-ID: <3C6FE0DC.1060308@cygnus.com> Date: Sun, 17 Feb 2002 08:57:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:0.9.8) Gecko/20020210 X-Accept-Language: en-us MIME-Version: 1.0 To: Daniel Jacobowitz Cc: "Peter.Schauer" , gdb-patches@sources.redhat.com Subject: Re: [RFD] How to fix FRAME_CHAIN_VALID redefinition in config/i386/tm-i386v4.h ? References: <200202171345.OAA04571@reisser.regent.e-technik.tu-muenchen.de> <3C6FD90E.5000504@cygnus.com> <20020217113349.A3217@nevyn.them.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2002-02/txt/msg00455.txt.bz2 > > Or we could fix this particular problem by making FRAME_CHAIN_VALID > into a multi-arch method (just in case, and for hppa (?) which seemed > to have a useful redefinition, though I don't see why it was needed), > defaulting it to func_frame_chain_valid for all targets. No one ever > gave me a reason not to do this when I asked. Er, FRAME_CHAIN_VALID is a multi-arch method. >> I suspect a combination of the first three is the best. The moment the >> heuristic is pushed down to the target we end up with inconsistent, >> target dependant, behavour. > > > There's some interesting code along these lines in what Richard > committed for ARM. He parses things like glibc's .note.ABI-tag > section, as well as ELF_OSABI fields where set. The situtation is very similar to COERCE_FLOAT_TO_DOUBLE. The problem should be solved in a generic way. However, until then each target gets to come up with a local solution. Andrew