This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [patch] static_kind -> bit0, bit1 [Re: [gdb] Fortran dynamic arrays]
- From: Daniel Jacobowitz <drow at false dot org>
- To: Joel Brobecker <brobecker at adacore dot com>
- Cc: Jan Kratochvil <jan dot kratochvil at redhat dot com>, gdb-patches at sourceware dot org, Tobias Burnus <burnus at net-b dot de>, Ulrich Weigand <uweigand at de dot ibm dot com>, Jim Blandy <jimb at red-bean dot com>, jimb at codesourcery dot com
- Date: Fri, 26 Sep 2008 08:57:54 -0400
- Subject: Re: [patch] static_kind -> bit0, bit1 [Re: [gdb] Fortran dynamic arrays]
- 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>
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