From: Joel Brobecker <brobecker@adacore.com>
To: Eric Botcazou <ebotcazou@adacore.com>
Cc: Michael Eager <eager@eagerm.com>,
gcc-patches@gcc.gnu.org, Olivier Hainque <hainque@adacore.com>,
Jason Merrill <jason@redhat.com>,
guitton@adacore.com
Subject: Re: [PING*4] add support for dwarf AT_GNU_descriptive_type
Date: Tue, 09 Nov 2010 21:42:00 -0000 [thread overview]
Message-ID: <20101109213749.GJ2811@adacore.com> (raw)
In-Reply-To: <201011092208.35602.ebotcazou@adacore.com>
> > I'm interested in seeing the DWARF which is generated for the specific
> > example and what would be generated with the patch.
>
> You can already see it with unpatched GNAT compilers; the only missing thing
> is the DW_AT_GNU_descriptive_type that links a type to the additional types
> generated to encode its debug info.
In other words, it's a performance improvement for the debugger. Instead
of performing the lookup by name, we have direct access to it.
--
Joel
next prev parent reply other threads:[~2010-11-09 21:38 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-02 14:51 add support for dwarf AT_descriptive_type Olivier Hainque
2010-09-15 11:21 ` [ping] " Olivier Hainque
2010-09-27 15:29 ` [ping*2] add support for dwarf AT_GNU_descriptive_type Olivier Hainque
2010-10-06 20:44 ` [ping*3] " Olivier Hainque
2010-10-18 9:11 ` [PING*4] " Olivier Hainque
2010-10-24 20:50 ` Jason Merrill
2010-10-26 11:03 ` Olivier Hainque
2010-11-09 11:47 ` Olivier Hainque
2010-11-09 17:20 ` Michael Eager
2010-11-09 19:11 ` Eric Botcazou
2010-11-09 21:11 ` Michael Eager
2010-11-09 21:17 ` Eric Botcazou
2010-11-09 21:42 ` Joel Brobecker [this message]
2010-11-09 21:53 ` Michael Eager
2010-11-09 22:07 ` Joel Brobecker
2010-11-10 0:02 ` Michael Eager
2010-11-10 5:55 ` Joel Brobecker
2010-11-10 7:33 ` Michael Eager
2010-11-10 8:34 ` Olivier Hainque
2010-10-24 22:57 ` add support for dwarf AT_descriptive_type Michael Eager
2010-10-26 11:03 ` Olivier Hainque
2010-10-27 18:32 ` Joel Brobecker
2010-10-27 18:35 ` Jakub Jelinek
2010-10-27 18:37 ` Joel Brobecker
2011-02-18 5:29 ` [PING #5] " Joel Brobecker
2011-02-21 5:05 ` Jason Merrill
2011-02-21 6:56 ` Jason Merrill
2011-02-22 17:44 ` Olivier Hainque
2011-02-23 1:49 ` Jason Merrill
2011-02-23 10:56 ` Olivier Hainque
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=20101109213749.GJ2811@adacore.com \
--to=brobecker@adacore.com \
--cc=eager@eagerm.com \
--cc=ebotcazou@adacore.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=guitton@adacore.com \
--cc=hainque@adacore.com \
--cc=jason@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).