public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: "Ijaz, Abdul B" <abdul.b.ijaz@intel.com>
To: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Cc: "tom@tromey.com" <tom@tromey.com>,
	"JiniSusan.George@amd.com" <JiniSusan.George@amd.com>
Subject: [PING 8][PATCH v5 0/3] Fortran entry and DW_TAG_entry_point
Date: Mon, 4 Sep 2023 08:19:46 +0000	[thread overview]
Message-ID: <SA1PR11MB6846982588503BFE1730EADFCBE9A@SA1PR11MB6846.namprd11.prod.outlook.com> (raw)

Ping!

Patch v5 3/3 fix for the  feedback from Tom is already approved by him (https://sourceware.org/pipermail/gdb-patches/2023-January/195499.html)
For rest waiting for approval or any feedback for v5 series of patches.

Thanks,
Abdul Basit
________________________________
From: Kempke, Nils-Christian <mailto:nils-christian.kempke@intel.com>
Sent: Friday, October 21, 2022  08:15:59 GMT 2022
To: mailto:gdb-patches@sourceware.org <mailto:gdb-patches@sourceware.org>; Kempke, Nils-Christian <mailto:nils-christian.kempke@intel.com>
Cc: mailto:jinisusan.george@amd.com <mailto:jinisusan.george@amd.com>; mailto:tom@tromey.com <mailto:tom@tromey.com>
Subject: Re: [PING 7][PATCH v5 0/3] Fortran entry and DW_TAG_entry_point

Ping!

Thanks,
Nils
________________________________
From: Kempke, Nils-Christian <mailto:nils-christian.kempke@intel.com>
Sent: Thursday, October 13, 2022 10:53 AM
To: mailto:gdb-patches@sourceware.org <mailto:gdb-patches@sourceware.org>; Kempke, Nils-Christian <mailto:nils-christian.kempke@intel.com>
Cc: mailto:jinisusan.george@amd.com <mailto:jinisusan.george@amd.com>; mailto:tom@tromey.com <mailto:tom@tromey.com>
Subject: Re: [PING 6][PATCH v5 0/3] Fortran entry and DW_TAG_entry_point

Ping!

Thanks,
Nils
________________________________
From: Gdb-patches <gdb-patches-bounces+nils-christian.kempke=mailto:intel.com@sourceware.org> on behalf of Kempke, Nils-Christian via Gdb-patches <mailto:gdb-patches@sourceware.org>
Sent: Wednesday, October 5, 2022 10:24 PM
To: mailto:gdb-patches@sourceware.org <mailto:gdb-patches@sourceware.org>
Cc: mailto:jinisusan.george@amd.com <mailto:jinisusan.george@amd.com>; mailto:tom@tromey.com <mailto:tom@tromey.com>
Subject: Re: [PING 5][PATCH v5 0/3] Fortran entry and DW_TAG_entry_point

Ping!

Thanks,
Nils
________________________________
From: Kempke, Nils-Christian <mailto:nils-christian.kempke@intel.com>
Sent: Monday, September 26, 2022 4:03 PM
To: mailto:gdb-patches@sourceware.org <mailto:gdb-patches@sourceware.org>; Kempke, Nils-Christian <mailto:nils-christian.kempke@intel.com>
Cc: mailto:jinisusan.george@amd.com <mailto:jinisusan.george@amd.com>; mailto:tom@tromey.com <mailto:tom@tromey.com>
Subject: Re: [PING 4][PATCH v5 0/3] Fortran entry and DW_TAG_entry_point

Ping!

Thanks,
NIls
________________________________
From: Gdb-patches <gdb-patches-bounces+nils-christian.kempke=mailto:intel.com@sourceware.org> on behalf of Kempke, Nils-Christian via Gdb-patches <mailto:gdb-patches@sourceware.org>
Sent: Monday, September 19, 2022 12:21 PM
To: mailto:gdb-patches@sourceware.org <mailto:gdb-patches@sourceware.org>
Cc: mailto:jinisusan.george@amd.com <mailto:jinisusan.george@amd.com>; mailto:tom@tromey.com <mailto:tom@tromey.com>
Subject: Re: [PING 3][PATCH v5 0/3] Fortran entry and DW_TAG_entry_point

Ping!

Thanks,
Nils
________________________________
From: Kempke, Nils-Christian <mailto:nils-christian.kempke@intel.com>
Sent: Tuesday, August 30, 2022 4:45 PM
To: mailto:gdb-patches@sourceware.org <mailto:gdb-patches@sourceware.org>; Kempke, Nils-Christian <mailto:nils-christian.kempke@intel.com>
Cc: mailto:jinisusan.george@amd.com <mailto:jinisusan.george@amd.com>; mailto:tom@tromey.com <mailto: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=mailto:intel.com@sourceware.org> on behalf of Kempke, Nils-Christian via Gdb-patches <mailto:gdb-patches@sourceware.org>
Sent: Tuesday, August 23, 2022 4:40 PM
To: mailto:gdb-patches@sourceware.org <mailto:gdb-patches@sourceware.org>
Cc: mailto:jinisusan.george@amd.com <mailto:jinisusan.george@amd.com>; mailto:tom@tromey.com <mailto:tom@tromey.com>
Subject: Re: [PING][PATCH v5 0/3] Fortran entry and DW_TAG_entry_point

Ping!

Thanks, Nils
________________________________
From: Kempke, Nils-Christian <mailto:nils-christian.kempke@intel.com>
Sent: Monday, August 8, 2022 7:00 PM
To: mailto:gdb-patches@sourceware.org <mailto:gdb-patches@sourceware.org>
Cc: mailto:aburgess@redhat.com <mailto:aburgess@redhat.com>; mailto:jinisusan.george@amd.com <mailto:jinisusan.george@amd.com>; mailto:tom@tromey.com <mailto:tom@tromey.com>; Kempke, Nils-Christian <mailto: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>
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

             reply	other threads:[~2023-09-04  8:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-04  8:19 Ijaz, Abdul B [this message]
2023-09-19 15:52 ` 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=SA1PR11MB6846982588503BFE1730EADFCBE9A@SA1PR11MB6846.namprd11.prod.outlook.com \
    --to=abdul.b.ijaz@intel.com \
    --cc=JiniSusan.George@amd.com \
    --cc=gdb-patches@sourceware.org \
    --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).