From: Tom Tromey <tromey@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [4/4] RFC: dynamic arrays and DW_FORM_exprloc
Date: Mon, 18 Jul 2011 15:46:00 -0000 [thread overview]
Message-ID: <m3zkkb7h5l.fsf@fleche.redhat.com> (raw)
In-Reply-To: <m3oc0v9snf.fsf@fleche.redhat.com> (Tom Tromey's message of "Fri, 15 Jul 2011 14:48:52 -0600")
Jan> archer-jankratochvil-vla handles DW_FORM_exprloc by using
Jan> attr_form_is_block here. But that may be outside of the scope of
Jan> this patch, this change is OK.
Tom> I will change it to use attr_form_is_block; that seems totally
Tom> reasonable to me.
Here is what I am checking in.
Tom
2011-07-15 Tom Tromey <tromey@redhat.com>
* dwarf2read.c (read_subrange_type): Use attr_form_is_block when
checking for variable-sized array.
From 6ccb8e249bfe359df263dd9d179ad6b88f3490ef Mon Sep 17 00:00:00 2001
From: Tom Tromey <tromey@redhat.com>
Date: Fri, 15 Jul 2011 11:35:35 -0600
Subject: [PATCH 4/4] also recognize DW_FORM_exprloc as dynamic range
---
gdb/ChangeLog | 5 +++++
gdb/dwarf2read.c | 4 ++--
2 files changed, 7 insertions(+), 2 deletions(-)
diff --git a/gdb/dwarf2read.c b/gdb/dwarf2read.c
index 8a6b142..b397af9 100644
--- a/gdb/dwarf2read.c
+++ b/gdb/dwarf2read.c
@@ -8623,7 +8623,7 @@ read_subrange_type (struct die_info *die, struct dwarf2_cu *cu)
attr = dwarf2_attr (die, DW_AT_upper_bound, cu);
if (attr)
{
- if (attr->form == DW_FORM_block1 || is_ref_attr (attr))
+ if (attr_form_is_block (attr) || is_ref_attr (attr))
{
/* GCC encodes arrays with unspecified or dynamic length
with a DW_FORM_block1 attribute or a reference attribute.
@@ -8706,7 +8706,7 @@ read_subrange_type (struct die_info *die, struct dwarf2_cu *cu)
/* Mark arrays with dynamic length at least as an array of unspecified
length. GDB could check the boundary but before it gets implemented at
least allow accessing the array elements. */
- if (attr && attr->form == DW_FORM_block1)
+ if (attr && attr_form_is_block (attr))
TYPE_HIGH_BOUND_UNDEFINED (range_type) = 1;
/* Ada expects an empty array on no boundary attributes. */
--
1.7.6
prev parent reply other threads:[~2011-07-18 15:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-15 18:25 Tom Tromey
2011-07-15 18:28 ` Jan Kratochvil
2011-07-15 20:58 ` Tom Tromey
2011-07-18 15:46 ` Tom Tromey [this message]
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=m3zkkb7h5l.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
/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