From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22958 invoked by alias); 26 Sep 2008 12:58:41 -0000 Received: (qmail 22949 invoked by uid 22791); 26 Sep 2008 12:58:41 -0000 X-Spam-Check-By: sourceware.org Received: from NaN.false.org (HELO nan.false.org) (208.75.86.248) by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 26 Sep 2008 12:57:56 +0000 Received: from nan.false.org (localhost [127.0.0.1]) by nan.false.org (Postfix) with ESMTP id E91CF10D01; Fri, 26 Sep 2008 12:57:54 +0000 (GMT) Received: from caradoc.them.org (22.svnf5.xdsl.nauticom.net [209.195.183.55]) by nan.false.org (Postfix) with ESMTP id C935010CFE; Fri, 26 Sep 2008 12:57:54 +0000 (GMT) Received: from drow by caradoc.them.org with local (Exim 4.69) (envelope-from ) id 1KjCtO-0005ht-8D; Fri, 26 Sep 2008 08:57:54 -0400 Date: Fri, 26 Sep 2008 12:58:00 -0000 From: Daniel Jacobowitz To: Joel Brobecker Cc: Jan Kratochvil , gdb-patches@sourceware.org, Tobias Burnus , Ulrich Weigand , Jim Blandy , jimb@codesourcery.com Subject: Re: [patch] static_kind -> bit0, bit1 [Re: [gdb] Fortran dynamic arrays] Message-ID: <20080926125754.GC21287@caradoc.them.org> Mail-Followup-To: Joel Brobecker , Jan Kratochvil , gdb-patches@sourceware.org, Tobias Burnus , Ulrich Weigand , Jim Blandy , jimb@codesourcery.com References: <20080818111120.GE16894@adacore.com> <200808181553.m7IFrG3w005270@d12av02.megacenter.de.ibm.com> <48A59B3C.9050801@net-b.de> <20080818111120.GE16894@adacore.com> <20080907115637.GA12939@host0.dyn.jankratochvil.net> <20080919221221.GA23372@adacore.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080919221221.GA23372@adacore.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: 2008-09/txt/msg00516.txt.bz2 On Fri, Sep 19, 2008 at 03:12:21PM -0700, Joel Brobecker wrote: > Next, we add a new field in the "loc" union that would contain a pointer > to the dwarf block, and probably create some kind of routine to create > these range types. After that, we can update the DWARF reader to handle > DWARF blocks for range type bounds, and finally update Fortran to make > use of them. > > What do others think? Agreed. I would suggest LOC_COMPUTED as the role model, except I don't see where to stash an ops pointer. Maybe in TYPE_SPECIFIC, or is that ugly? -- Daniel Jacobowitz CodeSourcery