From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Tom Tromey <tromey@redhat.com>, "H.J. Lu" <hjl.tools@gmail.com>,
GDB <gdb-patches@sourceware.org>
Subject: Re: RFC: Support DW_TAG_entry_point
Date: Thu, 23 Apr 2009 11:10:00 -0000 [thread overview]
Message-ID: <20090423110940.GA10652@host0.dyn.jankratochvil.net> (raw)
In-Reply-To: <20090423061003.GA7552@adacore.com>
On Thu, 23 Apr 2009 08:10:03 +0200, Joel Brobecker wrote:
> On Wed, 22 Apr 2009 23:13:27 +0200, Tom Tromey wrote:
> > This looks strange to me. IIUC, there's no requirement that
> > DW_TAG_entry_point be the first child.
>
> That was my main observation at the time.
I guess the whole patch tagets just one compiler's (ifort's?) use of
DW_TAG_entry_point. DWARF standard also says neither that DW_TAG_entry_point
should be a child of DW_TAG_subprogram nor that it should not have its own
DW_AT_high_pc. Therefore assuming DW_TAG_entry_point will be the first child
DIE is ensured for the target compiler this patch was made for.
Still this patch is a clear improvement of the current GDB state while having
no regressions. Shouldn't be a more complete support left as a possible next
patch on top of it?
Just my $0.02,
Jan
next prev parent reply other threads:[~2009-04-23 11:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-20 22:15 H.J. Lu
2009-03-21 1:02 ` Tom Tromey
2009-03-21 16:25 ` H.J. Lu
2009-03-23 18:26 ` Tom Tromey
2009-03-23 19:09 ` H.J. Lu
2009-04-22 21:13 ` Tom Tromey
2009-04-23 10:58 ` Joel Brobecker
2009-04-23 11:10 ` Jan Kratochvil [this message]
2009-04-23 23:43 ` Tom Tromey
2009-04-23 23:49 ` H.J. Lu
2009-04-24 0:13 ` 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=20090423110940.GA10652@host0.dyn.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=hjl.tools@gmail.com \
--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