From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Doug Evans <dje@google.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch] Delete FIELD_LOC_KIND_DWARF_BLOCK, unused.
Date: Mon, 28 Jun 2010 15:57:00 -0000 [thread overview]
Message-ID: <20100628155732.GA5597@host0.dyn.jankratochvil.net> (raw)
In-Reply-To: <20100627165540.D944984613@ruffy.mtv.corp.google.com>
On Sun, 27 Jun 2010 18:55:40 +0200, Doug Evans wrote:
> This patch is strictly cleanup.
> It deletes FIELD_LOC_KIND_DWARF_BLOCK as it is unused.
Just a background for it why it was introduced and why it is no longer needed
even for future additions.
It has been introduced a s part of VLA (Variable Length Arrays) patch series
importing which I never finished that time (and should start again soon).
Re: [patch] static_kind -> bit0, bit1 [Re: [gdb] Fortran dynamic arrays]
http://sourceware.org/ml/gdb-patches/2008-09/msg00425.html
# The first goal, as I understand it, is to be able to extend range
# types so that the bounds can be DWARF blocks.
Just in the meantime this FIELD_LOC_KIND_* is no longer used for array bounds
as new TYPE_RANGE_DATA different field of the union in the former place of
TYPE_FIELDS has been introduced:
[COMMIT] 64-bit range types in GDB
http://sourceware.org/ml/gdb-patches/2009-12/msg00181.html
The current FSF GDB HEAD uses just `LONGEST low, high;' for the bounds.
archer-jankratochvil-vla therefore has ported this FIELD_LOC_KIND_DWARF_BLOCK
to:
struct
{
union
{
LONGEST constant;
struct dwarf2_locexpr_baton *dwarf_block;
struct
{
struct dwarf2_loclist_baton *loclist;
struct type *type;
}
dwarf_loclist;
}
u;
enum range_bound_kind
{
RANGE_BOUND_KIND_CONSTANT,
RANGE_BOUND_KIND_DWARF_BLOCK,
RANGE_BOUND_KIND_DWARF_LOCLIST
}
kind;
}
/* Low bound of range. */
low,
/* High bound of range. */
high,
/* Byte stride of range. */
byte_stride;
But that is not currently submitted for a review.
> I will commit this in a few days if there are no objections.
BTW I agree.
Thanks,
Jan
next prev parent reply other threads:[~2010-06-28 15:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-27 16:55 Doug Evans
2010-06-28 15:57 ` Jan Kratochvil [this message]
2010-06-28 17:34 ` Tom Tromey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100628155732.GA5597@host0.dyn.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox