public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: "abdul.b.ijaz" <abijaz@ecsmtp.iul.intel.com>
To: gdb-patches@sourceware.org
Cc: abdul.b.ijaz@intel.com, andrew.burgess@embecosm.com
Subject: [PATCH v2 0/1] Fix variable length strings array for FORTRAN
Date: Fri, 27 Aug 2021 17:43:30 +0200	[thread overview]
Message-ID: <20210827154331.3915-1-abdul.b.ijaz@intel.com> (raw)

Hi All,

V2 patch contains the code review fixes for the inital patch.

V1 of this series can be found here:
https://sourceware.org/pipermail/gdb-patches/2021-August/181568.html

Changes since V1:
* Add check for stride in case of string type.
* Fixes for formatting and unrelated changes.
* Update commit message to indicate the reason for changing gdb/c-valprint.c.

GDB Testsuite is executed using the patch and there is no regression
seen as compare to master on Ubuntu 18.04 machine.

Best Regards,
Abdul Basit

Abdul Basit Ijaz (1):
  gdb: Fix arrays of variable length strings for FORTRAN

 gdb/c-valprint.c                        |  1 +
 gdb/gdbtypes.c                          | 16 +++++--
 gdb/testsuite/gdb.fortran/vla-array.exp | 57 +++++++++++++++++++++++++
 gdb/testsuite/gdb.fortran/vla-array.f90 | 44 +++++++++++++++++++
 4 files changed, 115 insertions(+), 3 deletions(-)
 create mode 100644 gdb/testsuite/gdb.fortran/vla-array.exp
 create mode 100644 gdb/testsuite/gdb.fortran/vla-array.f90

-- 
2.31.1


             reply	other threads:[~2021-08-27 15:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-27 15:43 abdul.b.ijaz [this message]
2021-08-27 15:43 ` [PATCH v2 1/1] gdb: Fix arrays of variable length strings " abdul.b.ijaz

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=20210827154331.3915-1-abdul.b.ijaz@intel.com \
    --to=abijaz@ecsmtp.iul.intel.com \
    --cc=abdul.b.ijaz@intel.com \
    --cc=andrew.burgess@embecosm.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).