From: Tom Tromey <tom@tromey.com>
To: Nils-Christian Kempke via Gdb-patches <gdb-patches@sourceware.org>
Cc: Nils-Christian Kempke <nils-christian.kempke@intel.com>,
jinisusan.george@amd.com, tom@tromey.com, aburgess@redhat.com
Subject: Re: [PATCH v5 0/3] Fortran entry and DW_TAG_entry_point
Date: Mon, 09 Jan 2023 13:26:39 -0700 [thread overview]
Message-ID: <87lemb8neo.fsf@tromey.com> (raw)
In-Reply-To: <20220808170019.86052-1-nils-christian.kempke@intel.com> (Nils-Christian Kempke via Gdb-patches's message of "Mon, 8 Aug 2022 19:00:16 +0200")
>>>>> Nils-Christian Kempke via Gdb-patches <gdb-patches@sourceware.org> writes:
> Hi,
> please find attached v5 of this series. Changes since v4 incorporate
> Tom's feedback here
> https://sourceware.org/pipermail/gdb-patches/2022-July/190798.html
> Namely, I added a special case to cooked_indexer::index_dies for
> DW_TAG_entry_point entries that sets its parent correctly.
Thanks. I think this is ok.
Tom
prev parent reply other threads:[~2023-01-09 20:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-08 17:00 Nils-Christian Kempke via Gdb-patches
2022-08-08 17:00 ` [PATCH v5 1/3] gdb, dwarf: move part of dwarf2_get_pc_bounds into separate function Nils-Christian Kempke via Gdb-patches
2022-08-23 14:40 ` [PING][PATCH v5 0/3] Fortran entry and DW_TAG_entry_point Kempke, Nils-Christian via Gdb-patches
2022-08-30 14:45 ` [PING 2][PATCH " Kempke, Nils-Christian via Gdb-patches
2022-09-19 10:21 ` [PING 3][PATCH " Kempke, Nils-Christian via Gdb-patches
2022-09-26 14:03 ` [PING 4][PATCH " Kempke, Nils-Christian via Gdb-patches
2022-10-05 20:24 ` [PING 5][PATCH " Kempke, Nils-Christian via Gdb-patches
2022-10-13 8:53 ` [PING 6][PATCH " Kempke, Nils-Christian via Gdb-patches
2022-10-21 8:15 ` [PING 7][PATCH " Kempke, Nils-Christian via Gdb-patches
2023-01-09 20:26 ` Tom Tromey [this message]
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=87lemb8neo.fsf@tromey.com \
--to=tom@tromey.com \
--cc=aburgess@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=jinisusan.george@amd.com \
--cc=nils-christian.kempke@intel.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