From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19934 invoked by alias); 13 Jun 2003 23:23: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 19883 invoked from network); 13 Jun 2003 23:23:00 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sources.redhat.com with SMTP; 13 Jun 2003 23:23:00 -0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.11.6/8.11.6) with ESMTP id h5DNN0H27902 for ; Fri, 13 Jun 2003 19:23:00 -0400 Received: from pobox.corp.redhat.com (pobox.corp.redhat.com [172.16.52.156]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id h5DNN0I01811 for ; Fri, 13 Jun 2003 19:23:00 -0400 Received: from localhost.localdomain (vpn50-55.rdu.redhat.com [172.16.50.55]) by pobox.corp.redhat.com (8.11.6/8.11.6) with ESMTP id h5DNMxJ20842; Fri, 13 Jun 2003 19:22:59 -0400 Received: (from kev@localhost) by localhost.localdomain (8.11.6/8.11.6) id h5DNMsr07793; Fri, 13 Jun 2003 16:22:54 -0700 Date: Fri, 13 Jun 2003 23:23:00 -0000 From: Kevin Buettner Message-Id: <1030613232254.ZM7792@localhost.localdomain> In-Reply-To: Jim Blandy "RFA: New function to read a descriptor's entry point" (Jun 13, 6:01pm) References: To: Jim Blandy , gdb-patches@sources.redhat.com Subject: Re: RFA: New function to read a descriptor's entry point MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2003-06/txt/msg00488.txt.bz2 On Jun 13, 6:01pm, Jim Blandy wrote: > This is a trivial wrapper around read_memory_unsigned_integer, but > it's a bit clearer *why* one is reading that word if you use it. > > 2003-06-06 Jim Blandy > > * ppc-linux-tdep.c (ppc64_desc_entry_point): New function. > (ppc64_standard_linkage_target): Use it. Hmm. I thought I okay'd this one already: http://sources.redhat.com/ml/gdb-patches/2003-06/msg00442.html http://sources.redhat.com/ml/gdb-patches/2003-06/msg00457.html Anyway, it's still okay. :-) Kevin