From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29883 invoked by alias); 23 Nov 2005 02:23:30 -0000 Received: (qmail 29875 invoked by uid 22791); 23 Nov 2005 02:23:30 -0000 X-Spam-Check-By: sourceware.org Received: from nile.gnat.com (HELO nile.gnat.com) (205.232.38.5) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 23 Nov 2005 02:23:29 +0000 Received: from localhost (localhost [127.0.0.1]) by filtered-nile.gnat.com (Postfix) with ESMTP id B101748CF44; Tue, 22 Nov 2005 21:23:26 -0500 (EST) Received: from nile.gnat.com ([127.0.0.1]) by localhost (nile.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 20609-01-4; Tue, 22 Nov 2005 21:23:26 -0500 (EST) Received: from takamaka.act-europe.fr (s142-179-108-108.bc.hsia.telus.net [142.179.108.108]) by nile.gnat.com (Postfix) with ESMTP id 37BD148CF40; Tue, 22 Nov 2005 21:23:26 -0500 (EST) Received: by takamaka.act-europe.fr (Postfix, from userid 507) id 8038F47E79; Tue, 22 Nov 2005 18:23:25 -0800 (PST) Date: Wed, 23 Nov 2005 02:52:00 -0000 From: Joel Brobecker To: Jim Blandy , gdb@sourceware.org Subject: Re: Prologue analysis interface Message-ID: <20051123022325.GU1635@adacore.com> References: <8f2776cb0511221124u988f759u17418a114e1f3b7c@mail.gmail.com> <20051122193034.GA25326@nevyn.them.org> <8f2776cb0511221549p2cfbbc30w621da6c2f159a33f@mail.gmail.com> <20051123020455.GA2247@nevyn.them.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051123020455.GA2247@nevyn.them.org> User-Agent: Mutt/1.4i Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2005-11/txt/msg00515.txt.bz2 > The frame pointer bits do involve some target heuristics. I think we > could do away with that, if we had reason to (i.e. an interesting > target which didn't use a fixed register for this). But I'm not > suggesting it until we have such a target, hopefully not for a long > time. Not sure if this is relevant, but the HPPA ABI says that when there is a frame pointer, it is either in r3 or r4, depending on the frame size (IIRC). GCC doesn't follow the ABI, and always uses r3, but I am pretty sure that the HP C compiler does follow that convention... -- Joel