From: Tom Tromey <tromey@redhat.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: GDB <gdb-patches@sourceware.org>
Subject: Re: RFC: Support DW_TAG_entry_point
Date: Mon, 23 Mar 2009 18:26:00 -0000 [thread overview]
Message-ID: <m3fxh485tc.fsf@fleche.redhat.com> (raw)
In-Reply-To: <6dc9ffc80903210924i10a807f6n320d93ca23e07fef@mail.gmail.com> (H. J. Lu's message of "Sat\, 21 Mar 2009 09\:24\:31 -0700")
>>>>> "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...
Tom
next prev parent reply other threads:[~2009-03-23 18:14 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 [this message]
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
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=m3fxh485tc.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=hjl.tools@gmail.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