From: Joel Brobecker <brobecker@adacore.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb@sourceware.org
Subject: Re: [Ada/dwarf] New DW_AT_GNAT_descriptive_type DWARF attribute...
Date: Mon, 20 Apr 2009 21:15:00 -0000 [thread overview]
Message-ID: <20090420203152.GR2904@adacore.com> (raw)
In-Reply-To: <m3bpqr4302.fsf@fleche.redhat.com>
> I think you should trust your judgment here; you're the expert in this
> area.
Wow, thanks! :)
> Joel> The changes in GDB are relatively small, I think - at least in
> Joel> the DWARF reader part. We added a field in the gnat_specific part
> Joel> of struct type, and I can see how it could trigger some protests.
> Joel> But we can discuss the specifics of the patch if there are no
> Joel> objections to this new attribute.
>
> I don't see a gnat_specific part of struct type at all. Is this from
> an unsubmitted change?
Yes. This is actually part of the meat of that change were we add
the gnat_specific to the union to stuff some ada-specific data,
much like we do for C++ with the cplus_specific area.
I'll try to prepare a patch for everyone to see.
--
Joel
prev parent reply other threads:[~2009-04-20 20:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-17 17:32 Joel Brobecker
2009-04-20 18:36 ` Tom Tromey
2009-04-20 21:15 ` Joel Brobecker [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=20090420203152.GR2904@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb@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