From: Andrew Burgess <aburgess@redhat.com>
To: gdb-patches@sourceware.org
Cc: Andrew Burgess <aburgess@redhat.com>
Subject: [PATCH 0/3] Fortran assumed rank array support
Date: Wed, 23 Mar 2022 11:59:55 +0000 [thread overview]
Message-ID: <cover.1648036751.git.aburgess@redhat.com> (raw)
In-Reply-To: <20220323115809.GT1212730@redhat.com>
Feedback welcome,
Thanks,
Andrew
---
Andrew Burgess (2):
gdb: small simplification in dwarf2_locexpr_baton_eval
gdb/dwarf: pass an array of values to the dwarf evaluator
rupothar (1):
gdb: add support for Fortran's ASSUMED RANK arrays
gdb/dwarf2/loc.c | 26 ++---
gdb/dwarf2/loc.h | 8 +-
gdb/dwarf2/read.c | 19 +++-
gdb/gdbtypes.c | 127 +++++++++++++++++++---
gdb/gdbtypes.h | 7 ++
gdb/gnu-v3-abi.c | 2 +-
gdb/testsuite/gdb.fortran/assumedrank.exp | 86 +++++++++++++++
gdb/testsuite/gdb.fortran/assumedrank.f90 | 41 +++++++
8 files changed, 281 insertions(+), 35 deletions(-)
create mode 100644 gdb/testsuite/gdb.fortran/assumedrank.exp
create mode 100644 gdb/testsuite/gdb.fortran/assumedrank.f90
--
2.25.4
next prev parent reply other threads:[~2022-03-23 12:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-19 17:57 [PATCH] Support for Fortran's ASSUMED RANK Potharla, Rupesh
2022-01-21 19:07 ` Andrew Burgess
2022-01-22 7:17 ` Potharla, Rupesh
2022-01-28 7:49 ` Potharla, Rupesh
2022-02-06 13:39 ` Andrew Burgess
2022-03-16 11:54 ` Potharla, Rupesh
2022-03-23 11:58 ` Andrew Burgess
2022-03-23 11:59 ` Andrew Burgess [this message]
2022-03-23 11:59 ` [PATCH 1/3] gdb: small simplification in dwarf2_locexpr_baton_eval Andrew Burgess
2022-04-01 19:11 ` Tom Tromey
2022-03-23 11:59 ` [PATCH 2/3] gdb/dwarf: pass an array of values to the dwarf evaluator Andrew Burgess
2022-04-01 19:16 ` Tom Tromey
2022-03-23 11:59 ` [PATCH 3/3] gdb: add support for Fortran's ASSUMED RANK arrays Andrew Burgess
2022-04-01 19:38 ` Tom Tromey
2022-04-03 16:21 ` Andrew Burgess
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=cover.1648036751.git.aburgess@redhat.com \
--to=aburgess@redhat.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).