Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "H.J. Lu" <hjl.tools@gmail.com>
To: tromey@redhat.com
Cc: GDB <gdb-patches@sourceware.org>
Subject: Re: RFC: Support DW_TAG_entry_point
Date: Mon, 23 Mar 2009 19:09:00 -0000	[thread overview]
Message-ID: <6dc9ffc80903231125y5012f098ra2720ca3d4fbd152@mail.gmail.com> (raw)
In-Reply-To: <m3fxh485tc.fsf@fleche.redhat.com>

On Mon, Mar 23, 2009 at 11:14 AM, Tom Tromey <tromey@redhat.com> wrote:
>>>>>> "H.J." == H J Lu <hjl.tools@gmail.com> writes:
>
> Tom> Yes.  A rationale for the patch would also be helpful, at least to me.
>
> H.J.> DW_TAG_entry_point may be used by Fortran compiler. But gcc
> H.J.> doesn't use it.  I guess one reason is gdb doesn't support it. Is
> H.J.> this good enough?
>
> Yeah.  You also need that ChangeLog entry though...

Here is ChangeLog entry.  OK to install?

Thanks.

H.J.
---
2009-03-23  H.J. Lu  <hongjiu.lu@intel.com>

	* dwarf2read.c (scan_partial_symbols): Make a recursive call
	if a DIE has children. Handle DW_TAG_entry_point.
	(load_partial_dies): Don't skip DW_TAG_entry_point. Follow
	children of DW_TAG_subprogram if not C.
	(add_partial_symbol): Handle DW_TAG_entry_point.
	(process_die): Likewise.
	(dwarf2_get_pc_bounds): Likewise.
	(get_scope_pc_bounds): Likewise.
	(fixup_partial_die): Likewise.
	(new_symbol): Likewise.
	(read_type_die): Likewise.


  reply	other threads:[~2009-03-23 18:26 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 [this message]
2009-04-22 21:13 ` Tom Tromey
2009-04-23 10:58   ` Joel Brobecker
2009-04-23 11:10     ` Jan Kratochvil
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=6dc9ffc80903231125y5012f098ra2720ca3d4fbd152@mail.gmail.com \
    --to=hjl.tools@gmail.com \
    --cc=gdb-patches@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