From: "Pierre Muller" <pierre.muller@ics-cnrs.unistra.fr>
To: "'Tom Tromey'" <tromey@redhat.com>
Cc: <gdb-patches@sourceware.org>
Subject: RE: [RFA-v3] dwarf2read.c: Avoid complaint for char array of unspecified size
Date: Wed, 02 Jun 2010 06:25:00 -0000 [thread overview]
Message-ID: <001201cb021c$5e5723a0$1b056ae0$@muller@ics-cnrs.unistra.fr> (raw)
In-Reply-To: <m339x67erz.fsf@fleche.redhat.com>
> Pierre> + /* Test "long long int", "long int", and "int" objfile
> types,
> Pierre> + and select the last one having a size above or equal to
> the
> Pierre> + architecture address size. */
>
> I think you should test these in the reverse order: int, then long,
> then
> long long. This assures you will find the smallest type that matches.
>
> This patch is ok with that change.
Thanks for the approval,
I modified as you suggested, even if I don't think that it makes
any difference in the chosen integer type...
Pierre
For the record, here is what I checked in rev 1.390 of dwarf2-read.c:
ChangeLog entry:
2010-06-02 Pierre Muller <muller@ics.u-strasbg.fr>
* dwarf2read.c (read_subrange_type): Handle missing base type
according to Dwarf-2 specifications.
Index: dwarf2read.c
===================================================================
RCS file: /cvs/src/src/gdb/dwarf2read.c,v
retrieving revision 1.389
diff -u -p -r1.389 dwarf2read.c
--- dwarf2read.c 1 Jun 2010 21:34:15 -0000 1.389
+++ dwarf2read.c 2 Jun 2010 06:19:23 -0000
@@ -6131,16 +6131,8 @@ read_subrange_type (struct die_info *die
LONGEST high = -1;
char *name;
LONGEST negative_mask;
-
+
base_type = die_type (die, cu);
- if (TYPE_CODE (base_type) == TYPE_CODE_VOID)
- {
- complaint (&symfile_complaints,
- _("DW_AT_type missing from DW_TAG_subrange_type"));
- base_type
- = init_type (TYPE_CODE_INT, gdbarch_addr_bit (gdbarch) / 8,
- 0, NULL, cu->objfile);
- }
if (cu->language == language_fortran)
{
@@ -6158,10 +6150,10 @@ read_subrange_type (struct die_info *die
attr = dwarf2_attr (die, DW_AT_upper_bound, cu);
if (attr)
{
- if (attr->form == DW_FORM_block1)
+ if (attr->form == DW_FORM_block1 || is_ref_attr (attr))
{
/* GCC encodes arrays with unspecified or dynamic length
- with a DW_FORM_block1 attribute.
+ with a DW_FORM_block1 attribute or a reference attribute.
FIXME: GDB does not yet know how to handle dynamic
arrays properly, treat them as arrays with unspecified
length for now.
@@ -6176,6 +6168,54 @@ read_subrange_type (struct die_info *die
else
high = dwarf2_get_attr_constant_value (attr, 1);
}
+ else
+ {
+ attr = dwarf2_attr (die, DW_AT_count, cu);
+ if (attr)
+ {
+ int count = dwarf2_get_attr_constant_value (attr, 1);
+ high = low + count - 1;
+ }
+ }
+
+ /* Dwarf-2 specifications explicitly allows to create subrange types
+ without specifying a base type.
+ In that case, the base type must be set to the type of
+ the lower bound, upper bound or count, in that order, if any of these
+ three attributes references an object that has a type.
+ If no base type is found, the Dwarf-2 specifications say that
+ a signed integer type of size equal to the size of an address should
+ be used.
+ For the following C code: `extern char gdb_int [];'
+ GCC produces an empty range DIE.
+ FIXME: muller/2010-05-28: Possible references to object for low bound,
+ high bound or count are not yet handled by this code.
+ */
+ if (TYPE_CODE (base_type) == TYPE_CODE_VOID)
+ {
+ struct objfile *objfile = cu->objfile;
+ struct gdbarch *gdbarch = get_objfile_arch (objfile);
+ int addr_size = gdbarch_addr_bit (gdbarch) /8;
+ struct type *int_type = objfile_type (objfile)->builtin_int;
+
+ /* Test "int", "long int", and "long long int" objfile types,
+ and select the first one having a size above or equal to the
+ architecture address size. */
+ if (int_type && TYPE_LENGTH (int_type) >= addr_size)
+ base_type = int_type;
+ else
+ {
+ int_type = objfile_type (objfile)->builtin_long;
+ if (int_type && TYPE_LENGTH (int_type) >= addr_size)
+ base_type = int_type;
+ else
+ {
+ int_type = objfile_type (objfile)->builtin_long_long;
+ if (int_type && TYPE_LENGTH (int_type) >= addr_size)
+ base_type = int_type;
+ }
+ }
+ }
negative_mask =
(LONGEST) -1 << (TYPE_LENGTH (base_type) * TARGET_CHAR_BIT - 1);
next prev parent reply other threads:[~2010-06-02 6:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <38685.0063725889$1274473713@news.gmane.org>
2010-05-21 22:13 ` [RFA] " Tom Tromey
2010-05-21 23:55 ` Pierre Muller
2010-05-24 15:35 ` Tom Tromey
2010-05-26 15:21 ` [RFA-v2] " Pierre Muller
[not found] ` <34200.8848595016$1274864816@news.gmane.org>
2010-05-27 20:09 ` Tom Tromey
2010-05-28 10:17 ` [RFA-v3] " Pierre Muller
2010-06-01 19:07 ` Tom Tromey
2010-06-02 6:25 ` Pierre Muller [this message]
2010-06-02 19:35 ` 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='001201cb021c$5e5723a0$1b056ae0$@muller@ics-cnrs.unistra.fr' \
--to=pierre.muller@ics-cnrs.unistra.fr \
--cc=gdb-patches@sourceware.org \
--cc=tromey@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