From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6070 invoked by alias); 28 Aug 2003 22:48:05 -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 6046 invoked from network); 28 Aug 2003 22:48:02 -0000 Received: from unknown (HELO localhost.redhat.com) (207.219.125.105) by sources.redhat.com with SMTP; 28 Aug 2003 22:48:02 -0000 Received: from redhat.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 187242B7F; Thu, 28 Aug 2003 18:48:02 -0400 (EDT) Message-ID: <3F4E86A1.8090805@redhat.com> Date: Thu, 28 Aug 2003 22:48:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0.2) Gecko/20030820 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Jim Blandy Cc: Kevin Buettner , gdb-patches@sources.redhat.com Subject: Re: [ppc64-linux] gdbarch hook to find true execution entry point References: <1030611231105.ZM27287@localhost.localdomain> <3EFC90EC.9040502@redhat.com> <3F0210EA.8050009@redhat.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2003-08/txt/msg00522.txt.bz2 >>> - Can infcall.c instead explicitly call CONVERT_FROM_FUNC_PTR_ADDR on >>> CALL_DUMMY_ADDRESS, or better, have entry_point_address do this? It >>> would help eliminate CALL_DUMMY_ADDRESS. >>> >> >> I'm not sure I understand enough of the details to say anything about >> this. Why isn't infcall.c just using entry_point_address right now? >> > Unfortunatly, a number of targets, such as PowerPC 64 GNU/Linux, have added custom CALL_DUMMY_ADDRESS methods :-( > > My original concern here was that CALL_DUMMY_ADDRESS, CONVERT_FROM_FUNC_PTR_ADDR, and this new architecture method all appeared to be doing roughly the same thing. > > Can at PowerPC 64 GNU/Linux's CALL_DUMMY_ADDRESS be eliminated? Just FYI, I've eliminated CALL_DUMMY_ADDRESS. Andrew