From: Daniel Jacobowitz <drow@false.org>
To: Jim Blandy <jimb@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [rfa/dwarf] Support for attributes pointing to a different CU
Date: Sun, 03 Oct 2004 16:16:00 -0000 [thread overview]
Message-ID: <20041003161621.GB3234@nevyn.them.org> (raw)
In-Reply-To: <vt2k6ucua6b.fsf@zenia.home>
On Wed, Sep 29, 2004 at 02:50:20PM -0500, Jim Blandy wrote:
>
> > @@ -4610,6 +4821,9 @@ read_subrange_type (struct die_info *die
> > low = 1;
> > }
> >
> > + /* FIXME: For variable sized arrays either of these could be
> > + a variable rather than a constant value. We'll allow it,
> > + but we don't know how to handle it. */
> > attr = dwarf2_attr (die, DW_AT_lower_bound, cu);
> > if (attr)
> > low = dwarf2_get_attr_constant_value (attr, 0);
>
> This should be committed separately.
OK, done as below.
--
Daniel Jacobowitz
2004-10-03 Daniel Jacobowitz <dan@debian.org>
* dwarf2read.c (read_subrange_type): Add comment for variable
sized arrays.
Index: dwarf2read.c
===================================================================
RCS file: /cvs/src/src/gdb/dwarf2read.c,v
retrieving revision 1.163
diff -u -p -r1.163 dwarf2read.c
--- dwarf2read.c 21 Sep 2004 15:04:41 -0000 1.163
+++ dwarf2read.c 3 Oct 2004 16:14:23 -0000
@@ -4610,6 +4610,9 @@ read_subrange_type (struct die_info *die
low = 1;
}
+ /* FIXME: For variable sized arrays either of these could be
+ a variable rather than a constant value. We'll allow it,
+ but we don't know how to handle it. */
attr = dwarf2_attr (die, DW_AT_lower_bound, cu);
if (attr)
low = dwarf2_get_attr_constant_value (attr, 0);
next prev parent reply other threads:[~2004-10-03 16:16 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-23 4:57 Daniel Jacobowitz
2004-09-23 22:19 ` Jim Blandy
2004-09-23 22:33 ` Daniel Jacobowitz
2004-09-24 0:34 ` Daniel Jacobowitz
2004-09-28 22:43 ` Jim Blandy
2004-09-28 22:51 ` Jim Blandy
2004-09-28 22:57 ` Jim Blandy
2004-10-04 0:41 ` Daniel Jacobowitz
2004-10-04 22:12 ` Jim Blandy
2004-10-04 23:35 ` Daniel Jacobowitz
2004-10-05 5:13 ` Jim Blandy
2004-09-28 23:07 ` Jim Blandy
2004-10-03 16:28 ` Daniel Jacobowitz
2004-09-29 17:52 ` Jim Blandy
2004-10-03 16:12 ` Daniel Jacobowitz
2004-10-04 21:17 ` Jim Blandy
2004-10-04 21:22 ` Daniel Jacobowitz
2004-10-05 5:07 ` Jim Blandy
2004-10-05 13:48 ` Daniel Jacobowitz
2004-10-05 16:13 ` Jim Blandy
2004-10-05 16:11 ` Jim Blandy
2004-10-05 18:01 ` Daniel Jacobowitz
2004-10-05 19:24 ` Jim Blandy
2004-09-29 17:54 ` Jim Blandy
2004-09-29 19:53 ` Jim Blandy
2004-10-03 16:16 ` Daniel Jacobowitz [this message]
2004-09-29 20:19 ` Jim Blandy
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=20041003161621.GB3234@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=jimb@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