From: "Kempke, Nils-Christian" <nils-christian.kempke@intel.com>
To: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Cc: "tom@tromey.com" <tom@tromey.com>
Subject: RE: [PING][PATCH v2 0/2] gdb/fortran: add support for accessing fields of extended types
Date: Mon, 21 Mar 2022 17:03:39 +0000 [thread overview]
Message-ID: <CY4PR1101MB2071FF2FC6D391567AA541D8B8169@CY4PR1101MB2071.namprd11.prod.outlook.com> (raw)
Kindly pinging.
Cheers,
Nils
> -----Original Message-----
> From: Kempke, Nils-Christian <nils-christian.kempke@intel.com>
> Sent: Monday, March 7, 2022 3:21 PM
> To: gdb-patches@sourceware.org
> Cc: tom@tromey.com; Kempke, Nils-Christian <nils-
> christian.kempke@intel.com>
> Subject: [PATCH v2 0/2] gdb/fortran: add support for accessing fields of
> extended types
>
> Hi all,
>
> V1 of these patches can be found here:
>
> https://sourceware.org/pipermail/gdb-patches/2022-January/185103.html
>
> Changes since V1 only relate to patch one of this series (since patch
> was already approved). After the
> discussion here
>
> https://sourceware.org/pipermail/gdb-patches/2022-January/185186.html
>
> I for now opted for only resolving to a type name of an inherited
> structure when the language is actually set to Fortran. The other two
> options of 'resolving Fortran structs elsewhere' or 'adding a language
> specific query method' seemed overly complicated to me. Still, if
> anyone has objections/favors a different approach I'm happy do change
> the implementation.
>
> So the changes to V1 of this series are:
> * PATCH 1/2: add language check to limit the member access by
> base name to Fortran only.
> * PATCH 2/2: no changes.
>
> Thanks,
>
> Nils
>
> Bernhard Heckel (2):
> gdb/fortran: add support for accessing fields of extended types
> gdb/fortran: print fortran extended types with ptype
>
> gdb/f-exp.y | 7 +-
> gdb/f-lang.h | 11 +
> gdb/f-typeprint.c | 24 ++-
> gdb/testsuite/gdb.fortran/oop_extend_type.exp | 190
> ++++++++++++++++++
> gdb/testsuite/gdb.fortran/oop_extend_type.f90 | 69 +++++++
> gdb/valops.c | 9 +
> 6 files changed, 306 insertions(+), 4 deletions(-)
> create mode 100755 gdb/testsuite/gdb.fortran/oop_extend_type.exp
> create mode 100755 gdb/testsuite/gdb.fortran/oop_extend_type.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
next reply other threads:[~2022-03-21 17:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-21 17:03 Kempke, Nils-Christian [this message]
2022-03-28 17:42 Kempke, Nils-Christian
2022-04-04 8:13 ` Kempke, Nils-Christian
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=CY4PR1101MB2071FF2FC6D391567AA541D8B8169@CY4PR1101MB2071.namprd11.prod.outlook.com \
--to=nils-christian.kempke@intel.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).