From: Tom Tromey <tromey@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb@sourceware.org
Subject: Re: [Ada/dwarf] New DW_AT_GNAT_descriptive_type DWARF attribute...
Date: Mon, 20 Apr 2009 18:36:00 -0000 [thread overview]
Message-ID: <m3bpqr4302.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20090417161934.GW7585@adacore.com> (Joel Brobecker's message of "Fri\, 17 Apr 2009 09\:19\:34 -0700")
>>>>> "Joel" == Joel Brobecker <brobecker@adacore.com> writes:
Joel> But the reality is that we don't see this happening in the near
Joel> future. As we've come to accept this fact, we at AdaCore think
Joel> that it would be useful to others to be able to take advantage
Joel> of this attribute.
I think you should trust your judgment here; you're the expert in this
area.
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?
If struct type is a major space problem, we can counteract that by
changing the type implementation. Jan sent some ideas about this to
the gdb-patches list a while ago. I'm not sure this is all that big
an issue, though I am also not completely certain. Numbers would
help.
Tom
next prev parent reply other threads:[~2009-04-20 18:03 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 [this message]
2009-04-20 21:15 ` Joel Brobecker
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=m3bpqr4302.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=brobecker@adacore.com \
--cc=gdb@sourceware.org \
/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