From: "Kempke, Nils-Christian" <nils-christian.kempke@intel.com>
To: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: RE: [PING][PATCH 00/11] Improve Fortran intrinsic types and procedures
Date: Fri, 25 Mar 2022 16:22:14 +0000 [thread overview]
Message-ID: <CY4PR1101MB20713D9ADB3CFDFC02255462B81A9@CY4PR1101MB2071.namprd11.prod.outlook.com> (raw)
Kindly pinging.
Cheers,
Nils
> -----Original Message-----
> From: Kempke, Nils-Christian <nils-christian.kempke@intel.com>
> Sent: Wednesday, March 9, 2022 11:39 AM
> To: gdb-patches@sourceware.org
> Cc: Kempke, Nils-Christian <nils-christian.kempke@intel.com>
> Subject: [PATCH 00/11] Improve Fortran intrinsic types and procedures
>
> This series completes some of the current intrinsics handling in the
> Fortran language part.
>
> Mainly, it adds the KIND parameter overload to all currently implemented
> intrinsic procedures (in patch #9). In doing so it refactors the overload
> handling in f-exp.y.
>
> It also improves some of the Fortran type handling and adds a few missing
> types and changes the default Locical type to be of KIND=4.
>
> Lastly, it adds two sections to the documentation that (hopefully) clearly
> describe which Fortran intrinsic procedures and types are available in
> GDB.
>
> All changes only affect the Fortran language part of GDB.
>
> Any feedback is highly appreciated.
> Thanks!
> Nils
>
> Nils-Christian Kempke (11):
> gdb/f-lang: add Integer*1 to Fortran builtin types
> gdb/f-lang: remove hidden ^L characters
> gdb/fortran: fix complex type in Fortran builtin types
> gdb/fortran: reformat build_fortran_types in f-lang.c
> gdb/fortran: change default logical type to builtin_logical
> gdb/fortran: clean-up Fortran intrinsic types
> gdb/fortran: Change GDB print for fortran default types
> gdb/fortran: rename f77_keywords to f_keywords
> gdb/fortran: rewrite intrinsic handling and add some missing overloads
> gdb/fortran/testsuite: add complex from integers test
> gdb/doc: add section about fortran intrinsic functions and types
>
> gdb/doc/gdb.texinfo | 138 ++++++-
> gdb/f-exp.h | 182 +++++++--
> gdb/f-exp.y | 394 ++++++++++++++------
> gdb/f-lang.c | 267 +++++++++----
> gdb/f-lang.h | 7 +-
> gdb/std-operator.def | 10 +-
> gdb/testsuite/gdb.fortran/complex.exp | 10 +-
> gdb/testsuite/gdb.fortran/complex.f90 | 7 +-
> gdb/testsuite/gdb.fortran/intrinsics.exp | 46 ++-
> gdb/testsuite/gdb.fortran/lbound-ubound.F90 | 49 ++-
> gdb/testsuite/gdb.fortran/lbound-ubound.exp | 27 +-
> gdb/testsuite/gdb.fortran/size.exp | 84 ++++-
> gdb/testsuite/gdb.fortran/size.f90 | 213 ++++++++---
> gdb/testsuite/gdb.fortran/type-kinds.exp | 2 +
> gdb/testsuite/gdb.fortran/types.exp | 34 +-
> 15 files changed, 1151 insertions(+), 319 deletions(-)
>
> --
> 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-25 16:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-25 16:22 Kempke, Nils-Christian [this message]
2022-04-01 15:43 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=CY4PR1101MB20713D9ADB3CFDFC02255462B81A9@CY4PR1101MB2071.namprd11.prod.outlook.com \
--to=nils-christian.kempke@intel.com \
--cc=gdb-patches@sourceware.org \
/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).