From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13178 invoked by alias); 20 Jan 2009 03:57:48 -0000 Received: (qmail 13170 invoked by uid 22791); 20 Jan 2009 03:57:48 -0000 X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from NaN.false.org (HELO nan.false.org) (208.75.86.248) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 20 Jan 2009 03:57:42 +0000 Received: from nan.false.org (localhost [127.0.0.1]) by nan.false.org (Postfix) with ESMTP id A487010829; Tue, 20 Jan 2009 03:57:39 +0000 (GMT) Received: from caradoc.them.org (209.195.188.212.nauticom.net [209.195.188.212]) by nan.false.org (Postfix) with ESMTP id DEC20101AB; Tue, 20 Jan 2009 03:57:38 +0000 (GMT) Received: from drow by caradoc.them.org with local (Exim 4.69) (envelope-from ) id 1LP7k9-0003JR-Vy; Mon, 19 Jan 2009 22:57:37 -0500 Date: Tue, 20 Jan 2009 03:57:00 -0000 From: Daniel Jacobowitz To: Ulrich Weigand Cc: Jan Kratochvil , gdb-patches@sourceware.org, Joel Brobecker , Jim Blandy , Tobias Burnus Subject: Re: [patch] [VLA 2/2] Interpret FIELD_LOC_KIND_DWARF_BLOCK fields Message-ID: <20090120035737.GA12571@caradoc.them.org> Mail-Followup-To: Ulrich Weigand , Jan Kratochvil , gdb-patches@sourceware.org, Joel Brobecker , Jim Blandy , Tobias Burnus References: <20090113014122.GA27831@host0.dyn.jankratochvil.net> <200901191521.n0JFLAtI004277@d12av02.megacenter.de.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200901191521.n0JFLAtI004277@d12av02.megacenter.de.ibm.com> User-Agent: Mutt/1.5.17 (2008-05-11) X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2009-01/txt/msg00425.txt.bz2 On Mon, Jan 19, 2009 at 04:21:10PM +0100, Ulrich Weigand wrote: > Making this dwarf2-specific function directly callable seems to break > the abstraction layer that "hides" specific details of any particular > debug info formati from common code. > > However, I'm not sure I see a clean solution for this. Ideally, we'd > have something like a LOC_COMPUTED with callback functions, to handle > format-specific field_loc_kind values. But that would require adding > a new pointer to "struct field", which I don't really like either as > this is a quite space-critical data structure ... What fields use this - is it specific to array bounds? If so can we move it to a new array-specific extension to struct type? -- Daniel Jacobowitz CodeSourcery