Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Keven Boell <keven.boell@intel.com>
To: gdb-patches@sourceware.org
Cc: sanimir.agovic@intel.com, keven.boell@intel.com
Subject: [PATCH 00/23] Fortran dynamic array support
Date: Wed, 04 Jun 2014 05:54:00 -0000	[thread overview]
Message-ID: <1401861266-6240-1-git-send-email-keven.boell@intel.com> (raw)

This patch series add Fortran dynamic array support to gdb.

It allows the user to evaluate a dynamic array like an ordinary static array
e.g. print its elements instead of printing the pointer to the array.
In addition the size of a dynamic array can be retrieved with gdbs builtin
sizeof operator. Furthermore this series add support for Fortran stride support.

	1| integer, allocatable :: ary(:)
	2| allocate(ary(5))
	3| ary(:) = 42

	(gdb) print ary
	$1 = (42, 42, 42, 42, 42)

	(gdb) print sizeof (ary)
	$2 = 20

	(gdb) ptype ary
	type = integer(kind=4) (5)

This series is a follow up for the following C99 variable length array
support series:
	https://sourceware.org/ml/gdb-patches/2013-12/msg00625.html


Keven Boell (23):
  dwarf: add dwarf3 DW_OP_push_object_address opcode
  dwarf: add DW_AT_data_location support
  vla: introduce allocated/associated flags
  vla: make dynamic fortran arrays functional.
  vla: make field selection work with vla
  vla: reconstruct value to compute bounds of target type
  vla: use value constructor instead of raw-buffer manipulation
  vla: get dynamic array corner cases to work
  vla: changed string length semantic.
  vla: get Fortran dynamic strings working.
  vla: add stride support to fortran arrays.
  test: basic tests for dynamic array evaluations in Fortran.
  test: evaluate Fortran dynamic arrays of types.
  test: evaluate dynamic arrays using Fortran primitives.
  test: dynamic arrays passed to subroutines.
  test: correct ptype of dynamic arrays in Fortran.
  test: evaluating allocation/association status
  test: dynamic arrays passed to functions.
  test: accessing dynamic array history values.
  test: dynamic string evaluations.
  test: basic MI test for the dynamic array support.
  test: test sizeof for dynamic fortran arrays.
  test: stride support for dynamic arrays.

 gdb/c-valprint.c                                   |   11 +-
 gdb/dwarf2expr.c                                   |    6 +
 gdb/dwarf2expr.h                                   |    4 -
 gdb/dwarf2loc.c                                    |   65 ++++-
 gdb/dwarf2loc.h                                    |   10 +
 gdb/dwarf2read.c                                   |  179 ++++++++++++-
 gdb/f-typeprint.c                                  |   62 +++--
 gdb/f-valprint.c                                   |  118 +++------
 gdb/gdbtypes.c                                     |  268 ++++++++++++++++++--
 gdb/gdbtypes.h                                     |   57 +++++
 gdb/testsuite/gdb.fortran/vla-alloc-assoc.exp      |   65 +++++
 gdb/testsuite/gdb.fortran/vla-datatypes.exp        |   82 ++++++
 gdb/testsuite/gdb.fortran/vla-datatypes.f90        |   51 ++++
 gdb/testsuite/gdb.fortran/vla-func.exp             |   61 +++++
 gdb/testsuite/gdb.fortran/vla-func.f90             |   71 ++++++
 gdb/testsuite/gdb.fortran/vla-history.exp          |   62 +++++
 gdb/testsuite/gdb.fortran/vla-ptype-sub.exp        |   87 +++++++
 gdb/testsuite/gdb.fortran/vla-ptype.exp            |   96 +++++++
 gdb/testsuite/gdb.fortran/vla-sizeof.exp           |   46 ++++
 gdb/testsuite/gdb.fortran/vla-stride.exp           |   51 ++++
 gdb/testsuite/gdb.fortran/vla-stride.f90           |   30 +++
 gdb/testsuite/gdb.fortran/vla-strings.exp          |  104 ++++++++
 gdb/testsuite/gdb.fortran/vla-strings.f90          |   38 +++
 gdb/testsuite/gdb.fortran/vla-sub.f90              |   82 ++++++
 gdb/testsuite/gdb.fortran/vla-type.exp             |  127 ++++++++++
 gdb/testsuite/gdb.fortran/vla-type.f90             |  107 ++++++++
 .../gdb.fortran/vla-value-sub-arbitrary.exp        |   35 +++
 gdb/testsuite/gdb.fortran/vla-value-sub-finish.exp |   49 ++++
 gdb/testsuite/gdb.fortran/vla-value-sub.exp        |   90 +++++++
 gdb/testsuite/gdb.fortran/vla-value.exp            |  148 +++++++++++
 gdb/testsuite/gdb.fortran/vla.f90                  |   56 ++++
 gdb/testsuite/gdb.mi/mi-vla-fortran.exp            |  182 +++++++++++++
 gdb/testsuite/gdb.mi/vla.f90                       |   42 +++
 gdb/typeprint.c                                    |    7 +
 gdb/valarith.c                                     |   23 +-
 gdb/valprint.c                                     |   40 +++
 gdb/valprint.h                                     |    4 +
 gdb/value.c                                        |   52 +++-
 38 files changed, 2512 insertions(+), 156 deletions(-)
 create mode 100644 gdb/testsuite/gdb.fortran/vla-alloc-assoc.exp
 create mode 100644 gdb/testsuite/gdb.fortran/vla-datatypes.exp
 create mode 100644 gdb/testsuite/gdb.fortran/vla-datatypes.f90
 create mode 100644 gdb/testsuite/gdb.fortran/vla-func.exp
 create mode 100644 gdb/testsuite/gdb.fortran/vla-func.f90
 create mode 100644 gdb/testsuite/gdb.fortran/vla-history.exp
 create mode 100644 gdb/testsuite/gdb.fortran/vla-ptype-sub.exp
 create mode 100644 gdb/testsuite/gdb.fortran/vla-ptype.exp
 create mode 100644 gdb/testsuite/gdb.fortran/vla-sizeof.exp
 create mode 100644 gdb/testsuite/gdb.fortran/vla-stride.exp
 create mode 100644 gdb/testsuite/gdb.fortran/vla-stride.f90
 create mode 100644 gdb/testsuite/gdb.fortran/vla-strings.exp
 create mode 100644 gdb/testsuite/gdb.fortran/vla-strings.f90
 create mode 100644 gdb/testsuite/gdb.fortran/vla-sub.f90
 create mode 100644 gdb/testsuite/gdb.fortran/vla-type.exp
 create mode 100644 gdb/testsuite/gdb.fortran/vla-type.f90
 create mode 100644 gdb/testsuite/gdb.fortran/vla-value-sub-arbitrary.exp
 create mode 100644 gdb/testsuite/gdb.fortran/vla-value-sub-finish.exp
 create mode 100644 gdb/testsuite/gdb.fortran/vla-value-sub.exp
 create mode 100644 gdb/testsuite/gdb.fortran/vla-value.exp
 create mode 100644 gdb/testsuite/gdb.fortran/vla.f90
 create mode 100644 gdb/testsuite/gdb.mi/mi-vla-fortran.exp
 create mode 100644 gdb/testsuite/gdb.mi/vla.f90

-- 
1.7.9.5


             reply	other threads:[~2014-06-04  5:54 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-04  5:54 Keven Boell [this message]
2014-06-04  5:54 ` [PATCH 04/23] vla: make dynamic fortran arrays functional Keven Boell
2014-06-16 21:02   ` Jan Kratochvil
2014-06-17 13:53     ` Keven Boell
2014-06-17 17:26       ` Jan Kratochvil
2014-06-04  5:54 ` [PATCH 11/23] vla: add stride support to fortran arrays Keven Boell
2014-06-04  5:54 ` [PATCH 23/23] test: stride support for dynamic arrays Keven Boell
2014-06-04  5:54 ` [PATCH 15/23] test: dynamic arrays passed to subroutines Keven Boell
2014-06-04  5:54 ` [PATCH 20/23] test: dynamic string evaluations Keven Boell
2014-06-16 18:41   ` Jan Kratochvil
2014-06-17 13:52     ` Keven Boell
2014-06-04  5:54 ` [PATCH 13/23] test: evaluate Fortran dynamic arrays of types Keven Boell
2014-06-16 20:57   ` Jan Kratochvil
2014-06-04  5:54 ` [PATCH 08/23] vla: get dynamic array corner cases to work Keven Boell
2014-06-04  5:54 ` [PATCH 03/23] vla: introduce allocated/associated flags Keven Boell
2014-06-04  5:54 ` [PATCH 05/23] vla: make field selection work with vla Keven Boell
2014-06-04  5:54 ` [PATCH 06/23] vla: reconstruct value to compute bounds of target type Keven Boell
2014-06-04  5:54 ` [PATCH 07/23] vla: use value constructor instead of raw-buffer manipulation Keven Boell
2014-06-04  5:54 ` [PATCH 14/23] test: evaluate dynamic arrays using Fortran primitives Keven Boell
2014-06-04  5:54 ` [PATCH 10/23] vla: get Fortran dynamic strings working Keven Boell
2014-06-04  5:54 ` [PATCH 12/23] test: basic tests for dynamic array evaluations in Fortran Keven Boell
2014-06-04  5:54 ` [PATCH 16/23] test: correct ptype of dynamic arrays " Keven Boell
2014-06-04  5:55 ` [PATCH 22/23] test: test sizeof for dynamic fortran arrays Keven Boell
2014-06-04  5:55 ` [PATCH 01/23] dwarf: add dwarf3 DW_OP_push_object_address opcode Keven Boell
2014-06-05 20:47   ` Tom Tromey
2014-06-11 12:30     ` Keven Boell
2014-06-10  9:54   ` Joel Brobecker
2014-06-11 12:26     ` Keven Boell
2014-06-11 13:08       ` Joel Brobecker
2014-06-12  7:57         ` Keven Boell
2014-06-12 15:47           ` Joel Brobecker
2014-06-17 13:52             ` Keven Boell
2014-06-21 15:21               ` Joel Brobecker
2014-07-07 15:29                 ` Joel Brobecker
2014-06-04  5:55 ` [PATCH 18/23] test: dynamic arrays passed to functions Keven Boell
2014-06-04  5:55 ` [PATCH 19/23] test: accessing dynamic array history values Keven Boell
2014-06-04  5:55 ` [PATCH 17/23] test: evaluating allocation/association status Keven Boell
2014-06-04  5:55 ` [PATCH 21/23] test: basic MI test for the dynamic array support Keven Boell
2014-06-04  5:55 ` [PATCH 09/23] vla: changed string length semantic Keven Boell
2014-06-04  5:55 ` [PATCH 02/23] dwarf: add DW_AT_data_location support Keven Boell
2014-06-10 12:10   ` Joel Brobecker
2014-06-11 12:29     ` Keven Boell
2014-06-14 13:21     ` Jan Kratochvil
2014-06-04  7:10 ` [PATCH 00/23] Fortran dynamic array support Eli Zaretskii
2014-06-04 12:50 ` Joel Brobecker
2014-06-14 18:57 ` Jan Kratochvil
2014-06-14 19:39   ` Jan Kratochvil
2014-06-17 13:54     ` Keven Boell
2014-06-17 17:20       ` Jan Kratochvil

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=1401861266-6240-1-git-send-email-keven.boell@intel.com \
    --to=keven.boell@intel.com \
    --cc=gdb-patches@sourceware.org \
    --cc=sanimir.agovic@intel.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