From: "Kempke, Nils-Christian" <nils-christian.kempke@intel.com>
To: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Cc: "jinisusan.george@amd.com" <jinisusan.george@amd.com>,
"tom@tromey.com" <tom@tromey.com>
Subject: Re: [PING 3][PATCH v5 0/3] Fortran entry and DW_TAG_entry_point
Date: Mon, 19 Sep 2022 10:21:38 +0000 [thread overview]
Message-ID: <CY4PR1101MB2071CD01C00415EF5FDA1FC0B84D9@CY4PR1101MB2071.namprd11.prod.outlook.com> (raw)
Message-ID: <20220919102138.ZryGZ2a5UXxiOh-5YNSxUlXwkTKd3wxFYZ3XHL13Ryc@z> (raw)
In-Reply-To: <CY4PR1101MB20716F523B0DC219BADE140AB8799@CY4PR1101MB2071.namprd11.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 3891 bytes --]
Ping!
Thanks,
Nils
________________________________
From: Kempke, Nils-Christian <nils-christian.kempke@intel.com>
Sent: Tuesday, August 30, 2022 4:45 PM
To: gdb-patches@sourceware.org <gdb-patches@sourceware.org>; Kempke, Nils-Christian <nils-christian.kempke@intel.com>
Cc: jinisusan.george@amd.com <jinisusan.george@amd.com>; tom@tromey.com <tom@tromey.com>
Subject: Re: [PING 2][PATCH v5 0/3] Fortran entry and DW_TAG_entry_point
Ping!
Thanks,
Nils
________________________________
From: Gdb-patches <gdb-patches-bounces+nils-christian.kempke=intel.com@sourceware.org> on behalf of Kempke, Nils-Christian via Gdb-patches <gdb-patches@sourceware.org>
Sent: Tuesday, August 23, 2022 4:40 PM
To: gdb-patches@sourceware.org <gdb-patches@sourceware.org>
Cc: jinisusan.george@amd.com <jinisusan.george@amd.com>; tom@tromey.com <tom@tromey.com>
Subject: Re: [PING][PATCH v5 0/3] Fortran entry and DW_TAG_entry_point
Ping!
Thanks, Nils
________________________________
From: Kempke, Nils-Christian <nils-christian.kempke@intel.com>
Sent: Monday, August 8, 2022 7:00 PM
To: gdb-patches@sourceware.org <gdb-patches@sourceware.org>
Cc: aburgess@redhat.com <aburgess@redhat.com>; jinisusan.george@amd.com <jinisusan.george@amd.com>; tom@tromey.com <tom@tromey.com>; Kempke, Nils-Christian <nils-christian.kempke@intel.com>
Subject: [PATCH v5 0/3] Fortran entry and DW_TAG_entry_point
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.
v1 can be found here:
https://sourceware.org/pipermail/gdb-patches/2022-March/186900.html
v2 can be found here:
https://sourceware.org/pipermail/gdb-patches/2022-April/187853.html
v3 can be found here:
https://sourceware.org/pipermail/gdb-patches/2022-July/190556.html
v4 can be found here:
https://sourceware.org/pipermail/gdb-patches/2022-July/190691.html
Any feedback is highly appreciated,
thanks!
Nils
Nils-Christian Kempke (3):
gdb, dwarf: move part of dwarf2_get_pc_bounds into separate function
gdb, dwarf: add assert to dwarf2_get_pc_bounds
dwarf, fortran: add support for DW_TAG_entry_point
gdb/dwarf2/abbrev.c | 1 +
gdb/dwarf2/cooked-index.h | 3 +-
gdb/dwarf2/index-write.c | 3 +-
gdb/dwarf2/read.c | 137 +++++++++--
gdb/testsuite/gdb.dwarf2/dw2-entry-points.c | 43 ++++
gdb/testsuite/gdb.dwarf2/dw2-entry-points.exp | 215 ++++++++++++++++++
gdb/testsuite/gdb.fortran/entry-point.exp | 84 +++++++
gdb/testsuite/gdb.fortran/entry-point.f90 | 67 ++++++
8 files changed, 529 insertions(+), 24 deletions(-)
create mode 100644 gdb/testsuite/gdb.dwarf2/dw2-entry-points.c
create mode 100644 gdb/testsuite/gdb.dwarf2/dw2-entry-points.exp
create mode 100644 gdb/testsuite/gdb.fortran/entry-point.exp
create mode 100644 gdb/testsuite/gdb.fortran/entry-point.f90
--
2.25.1
Intel Deutschland GmbH
Registered Address: Am Campeon 10, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de<http://www.intel.de> <http://www.intel.de>
Managing Directors: Christin Eisenschmid, Sharon Heck, Tiffany Doon Silva
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928
Intel Deutschland GmbH
Registered Address: Am Campeon 10, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de <http://www.intel.de>
Managing Directors: Christin Eisenschmid, Sharon Heck, Tiffany Doon Silva
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928
next prev parent reply other threads:[~2022-09-19 10:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-08 17:00 [PATCH " Nils-Christian Kempke
2022-08-08 17:00 ` [PATCH v5 1/3] gdb, dwarf: move part of dwarf2_get_pc_bounds into separate function Nils-Christian Kempke
2022-08-23 14:40 ` [PING][PATCH v5 0/3] Fortran entry and DW_TAG_entry_point Kempke, Nils-Christian
2022-08-30 14:45 ` [PING 2][PATCH " Kempke, Nils-Christian
2022-08-30 14:45 ` Kempke, Nils-Christian
2022-09-19 10:21 ` Kempke, Nils-Christian [this message]
2022-09-19 10:21 ` [PING 3][PATCH " Kempke, Nils-Christian
2022-09-26 14:03 ` [PING 4][PATCH " Kempke, Nils-Christian
2022-09-26 14:03 ` Kempke, Nils-Christian
2022-10-05 20:24 ` [PING 5][PATCH " Kempke, Nils-Christian
2022-10-05 20:24 ` Kempke, Nils-Christian
2022-10-13 8:53 ` [PING 6][PATCH " Kempke, Nils-Christian
2022-10-13 8:53 ` Kempke, Nils-Christian
2022-10-21 8:15 ` [PING 7][PATCH " Kempke, Nils-Christian
2022-10-21 8:15 ` Kempke, Nils-Christian
2023-01-09 20:26 ` [PATCH " Tom Tromey
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=CY4PR1101MB2071CD01C00415EF5FDA1FC0B84D9@CY4PR1101MB2071.namprd11.prod.outlook.com \
--to=nils-christian.kempke@intel.com \
--cc=gdb-patches@sourceware.org \
--cc=jinisusan.george@amd.com \
--cc=tom@tromey.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).