From: Abdul Basit Ijaz <abdul.b.ijaz@intel.com>
To: gdb-patches@sourceware.org
Cc: abdul.b.ijaz@intel.com, aburgess@redhat.com
Subject: [PATCH v6 0/1] Fix arrays of variable length strings for FORTRAN
Date: Fri, 5 Jan 2024 14:19:11 +0100 [thread overview]
Message-ID: <20240105131912.22658-1-abdul.b.ijaz@intel.com> (raw)
From: "Ijaz, Abdul B" <abdul.b.ijaz@intel.com>
Hi All,
One build issue was left unmerged in V5 of this series where in V5
series patch is rebased only on latest master and feedback from Andrew on V3
series was already resolved in V4 series and there is no further feedback
on this since then.
V5 of this series can be found here:
https://sourceware.org/pipermail/gdb-patches/2024-January/205672.html
V4 of this series can be found here:
https://sourceware.org/pipermail/gdb-patches/2023-January/195836.html
V3 of this series can be found here:
https://sourceware.org/pipermail/gdb-patches/2022-May/188725.html
Changes since V4:
* Rebase patch on latest master and fix conflicts.
Following test configurations are tested on Ubuntu22.04 and no regression is seen:
gcc64/gcc32/native-gdbserver/native-extended-gdbserver(-m32).
I'm looking forward to comments.
Best Regards,
Abdul Basit
Ijaz, Abdul B (1):
fortran: Fix arrays of variable length strings for FORTRAN
gdb/c-valprint.c | 1 +
gdb/gdbtypes.c | 42 ++++++++++++++-
gdb/testsuite/gdb.fortran/string-types.exp | 4 +-
gdb/testsuite/gdb.fortran/vla-array.exp | 60 ++++++++++++++++++++++
gdb/testsuite/gdb.fortran/vla-array.f90 | 45 ++++++++++++++++
gdb/testsuite/gdb.opt/fortran-string.exp | 2 +-
6 files changed, 149 insertions(+), 5 deletions(-)
create mode 100644 gdb/testsuite/gdb.fortran/vla-array.exp
create mode 100644 gdb/testsuite/gdb.fortran/vla-array.f90
--
2.34.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:[~2024-01-05 13:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-05 13:19 Abdul Basit Ijaz [this message]
2024-01-05 13:19 ` [PATCH v6 1/1] fortran: " Abdul Basit Ijaz
2024-01-11 18:02 ` Tom Tromey
2024-01-12 18:57 ` Ijaz, Abdul B
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=20240105131912.22658-1-abdul.b.ijaz@intel.com \
--to=abdul.b.ijaz@intel.com \
--cc=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).