From: Tom Tromey <tromey@redhat.com>
To: "Pierre Muller" <pierre.muller@ics-cnrs.unistra.fr>
Cc: "'Doug Evans'" <dje@google.com>,
"'Pedro Alves'" <pedro@codesourcery.com>,
<gdb-patches@sourceware.org>
Subject: Re: [RFA]dwarf reader: Avoid complaint on const type
Date: Fri, 02 Jul 2010 21:47:00 -0000 [thread overview]
Message-ID: <m3d3v5k13u.fsf@fleche.redhat.com> (raw)
In-Reply-To: <29342.6726283089$1277816998@news.gmane.org> (Pierre Muller's message of "Tue, 29 Jun 2010 15:09:41 +0200")
>>>>> "Pierre" == Pierre Muller <pierre.muller@ics-cnrs.unistra.fr> writes:
Pierre> --- src/gdb/dwarf2read.c 28 Jun 2010 22:03:31 -0000 1.406
Pierre> +++ src/gdb/dwarf2read.c 29 Jun 2010 12:31:55 -0000
Pierre> @@ -3220,12 +3220,15 @@ process_die (struct die_info *die, struc
Pierre> case DW_TAG_base_type:
Pierre> case DW_TAG_subrange_type:
Pierre> case DW_TAG_typedef:
Pierre> - case DW_TAG_const_type:
Pierre> - case DW_TAG_volatile_type:
Pierre> /* Add a typedef symbol for the type definition, if it has a
Pierre> DW_AT_name. */
Pierre> new_symbol (die, read_type_die (die, cu), cu);
Pierre> break;
Pierre> + /* Type modifiers should be accepted without creating a new type
Pierre> name. */
Pierre> + case DW_TAG_const_type:
Pierre> + case DW_TAG_volatile_type:
Pierre> + read_type_die (die, cu);
Pierre> + break;
Why here and not a little earlier, with this case?
/* These dies have a type, but processing them does not create
a symbol or recurse to process the children. Therefore we can
read them on-demand through read_type_die. */
case DW_TAG_subroutine_type:
case DW_TAG_set_type:
case DW_TAG_array_type:
case DW_TAG_pointer_type:
case DW_TAG_ptr_to_member_type:
case DW_TAG_reference_type:
case DW_TAG_string_type:
break;
Pierre> case DW_TAG_base_type:
Pierre> - case DW_TAG_subrange_type:
Pierre> - case DW_TAG_const_type:
Pierre> - case DW_TAG_volatile_type:
Pierre> + case DW_TAG_subrange_type:
Pierre> SYMBOL_CLASS (sym) = LOC_TYPEDEF;
Pierre> SYMBOL_DOMAIN (sym) = VAR_DOMAIN;
Pierre> add_symbol_to_list (sym, cu->list_in_scope);
Why remove DW_TAG_subrange_type here?
Tom
next prev parent reply other threads:[~2010-07-02 21:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <41597.7287375883$1274454923@news.gmane.org>
2010-05-21 17:20 ` Tom Tromey
2010-05-21 20:46 ` Pierre Muller
2010-06-16 16:08 ` Pedro Alves
2010-06-20 22:39 ` Pierre Muller
[not found] ` <3752333521215815628@unknownmsgid>
2010-06-28 20:27 ` Doug Evans
2010-06-29 13:09 ` Pierre Muller
2010-07-01 17:09 ` Pedro Alves
2010-07-01 17:13 ` Joel Brobecker
2010-07-21 17:16 ` Pedro Alves
[not found] ` <29342.6726283089$1277816998@news.gmane.org>
2010-07-02 21:47 ` Tom Tromey [this message]
2010-05-21 15:31 Pierre Muller
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=m3d3v5k13u.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.com \
--cc=pierre.muller@ics-cnrs.unistra.fr \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).