From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 537 invoked by alias); 20 May 2003 20:17:39 -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 454 invoked from network); 20 May 2003 20:17:36 -0000 Received: from unknown (HELO crack.them.org) (146.82.138.56) by sources.redhat.com with SMTP; 20 May 2003 20:17:36 -0000 Received: from nevyn.them.org ([66.93.61.169] ident=mail) by crack.them.org with asmtp (Exim 3.12 #1 (Debian)) id 19IDYc-0006lK-00; Tue, 20 May 2003 15:17:59 -0500 Received: from drow by nevyn.them.org with local (Exim 3.36 #1 (Debian)) id 19IDXz-0004N3-00; Tue, 20 May 2003 16:17:19 -0400 Date: Tue, 20 May 2003 20:17:00 -0000 From: Daniel Jacobowitz To: Andrew Cagney Cc: Adam Fedor , GDB Patches Subject: Re: [RFA]: gdbarch FETCH_POINTER_ARGUMENT Message-ID: <20030520201718.GA16779@nevyn.them.org> Mail-Followup-To: Andrew Cagney , Adam Fedor , GDB Patches References: <3EC84B9A.8030505@doc.com> <3ECA8AF1.10001@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3ECA8AF1.10001@redhat.com> User-Agent: Mutt/1.5.1i X-SW-Source: 2003-05/txt/msg00366.txt.bz2 On Tue, May 20, 2003 at 04:07:13PM -0400, Andrew Cagney wrote: > Adam, > > I need to think about FETCH_POINTER_ARGUMENT. It needs additional > parameters - something to that lets it fetch registers or memory, and > something identifying the type of pointer. I'm curious. Would you mind expanding on that? My vision of FETCH_POINTER_ARGUMENT was: For a normal function on this architecture whose first N arguments are all pointers (or passed like pointers, etc.) fetch the value of the Nth argument. So I don't see how it would need a param specifying registers or memory. Hmm, maybe a regcache argument though. -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer