From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21994 invoked by alias); 20 May 2003 20:28:16 -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 21942 invoked from network); 20 May 2003 20:28:15 -0000 Received: from unknown (HELO localhost.redhat.com) (207.219.125.131) by sources.redhat.com with SMTP; 20 May 2003 20:28:15 -0000 Received: from redhat.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id E0A2F2B2F; Tue, 20 May 2003 16:28:03 -0400 (EDT) Message-ID: <3ECA8FD3.4050809@redhat.com> Date: Tue, 20 May 2003 20:28:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0.2) Gecko/20030223 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Daniel Jacobowitz Cc: Adam Fedor , GDB Patches Subject: Re: [RFA]: gdbarch FETCH_POINTER_ARGUMENT References: <3EC84B9A.8030505@doc.com> <3ECA8AF1.10001@redhat.com> <20030520201718.GA16779@nevyn.them.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2003-05/txt/msg00370.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. ``lets it fetch registers or memory'', not ``specify registers or memory''. > Hmm, maybe a regcache argument though. Something. Like I said, I need to think about it. Andrew