From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24584 invoked by alias); 4 Aug 2004 21:55:45 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 24576 invoked from network); 4 Aug 2004 21:55:44 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org with SMTP; 4 Aug 2004 21:55:44 -0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.12.10/8.12.10) with ESMTP id i74Ltde3030879 for ; Wed, 4 Aug 2004 17:55:44 -0400 Received: from localhost.redhat.com (porkchop.devel.redhat.com [172.16.58.2]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id i74LtXa24673; Wed, 4 Aug 2004 17:55:33 -0400 Received: from gnu.org (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id F24452B9D; Wed, 4 Aug 2004 17:55:27 -0400 (EDT) Message-ID: <41115B4F.1080700@gnu.org> Date: Wed, 04 Aug 2004 21:55:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-GB; rv:1.4.1) Gecko/20040801 MIME-Version: 1.0 To: Jim Blandy Cc: gdb@sources.redhat.com Subject: Re: interface to partial support for DW_OP_piece in dwarf2expr.[ch] References: <4111145F.7000504@gnu.org> <41112BAE.9080304@gnu.org> In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2004-08/txt/msg00048.txt.bz2 > Andrew Cagney writes: > > >>>> > Andrew Cagney writes: >>>> > >>> >>>>>> >>> I'm just having trouble getting my head around how this will affect >>>>>> >>> core-gdb, and seeing how this addresses our need to meet GCC 3.5's >>>>>> >>> requirements? >>>>>> >>> Can we expand on that? >> >>> >>> ? > > > I answered this. The dwarf2.expr.h change I posted doesn't get into > GCC 3.5's requirements, and it shouldn't. It's just meant to allow > dwarf2expr.[ch] to return the results of the computation it did; it's > up to its caller what to do with that. Ok. Can we just expand a little on how/where the caller, core-gdb, will use this then? Andrew