public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Bernhard Heckel <bernhard.heckel@intel.com>
To: qiyaoltc@gmail.com, eliz@gnu.org, brobecker@adacore.com
Cc: gdb-patches@sourceware.org, Bernhard Heckel <bernhard.heckel@intel.com>
Subject: [PATCH V3 0/6] Fortran: Resolve target types of pointers.
Date: Mon, 11 Jul 2016 15:12:00 -0000	[thread overview]
Message-ID: <1468249928-2169-1-git-send-email-bernhard.heckel@intel.com> (raw)

Addressed in V3:
- Don't resolve target types of pointers when resolving pointer types.
- Address pointers to dynamic types in C99 as well.
- Resolve dynamic target types of pointers when actual needed.
- Fix some type naming in Fortran testcases.


Addressed in V2:
- The type of the pointer should be known regardless it is 
  associated with target or not, [PATCH V2 1/5].
- Removed [PATCH V1 1/3], moved tests to [PATCH V2 2/5].
- Added tests to print derefenced pointers, [PATCH V2 2/5].
- Fix address print of not allocated arrays/pointer to 
  not allocated types, [PATCH V2 4/5]

Bernhard Heckel (6):
  Fortran: Testsuite, fix differences in type naming.
  Fortran: Resolve dynamic properties of pointer types.
  Typeprint: Resolve any dynamic target type of a pointer.
  Fortran: Typeprint, fix dangling types.
  Resolve dynamic target types of pointers.
  Fortran: Testsuite, add cyclic pointers.

 gdb/NEWS                                 |   2 +
 gdb/c-valprint.c                         |  22 +++++
 gdb/f-typeprint.c                        |  95 ++++++++++----------
 gdb/gdbtypes.c                           |  29 ++++++-
 gdb/testsuite/gdb.cp/vla-cxx.cc          |   9 ++
 gdb/testsuite/gdb.cp/vla-cxx.exp         |   9 ++
 gdb/testsuite/gdb.fortran/pointers.exp   | 143 +++++++++++++++++++++++++++++++
 gdb/testsuite/gdb.fortran/pointers.f90   | 109 +++++++++++++++++++++++
 gdb/testsuite/gdb.fortran/print_type.exp | 100 +++++++++++++++++++++
 gdb/testsuite/gdb.fortran/vla-ptype.exp  |  12 +--
 gdb/testsuite/gdb.fortran/vla-type.exp   |   7 +-
 gdb/testsuite/gdb.fortran/vla-value.exp  |  12 ++-
 gdb/testsuite/gdb.mi/mi-var-child-f.exp  |   7 +-
 gdb/testsuite/gdb.mi/mi-vla-fortran.exp  |  27 +++---
 gdb/typeprint.c                          |  19 ++++
 gdb/valops.c                             |  16 +++-
 gdb/valprint.c                           |   6 --
 17 files changed, 543 insertions(+), 81 deletions(-)
 create mode 100644 gdb/testsuite/gdb.fortran/pointers.exp
 create mode 100644 gdb/testsuite/gdb.fortran/pointers.f90
 create mode 100755 gdb/testsuite/gdb.fortran/print_type.exp

-- 
2.7.1.339.g0233b80

             reply	other threads:[~2016-07-11 15:12 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-11 15:12 Bernhard Heckel [this message]
2016-07-11 15:12 ` [PATCH V3 5/6] Resolve dynamic " Bernhard Heckel
2016-07-11 16:25   ` Eli Zaretskii
2016-07-11 15:12 ` [PATCH V3 4/6] Fortran: Typeprint, fix dangling types Bernhard Heckel
2016-07-11 15:12 ` [PATCH V3 6/6] Fortran: Testsuite, add cyclic pointers Bernhard Heckel
2016-07-11 15:12 ` [PATCH V3 3/6] Typeprint: Resolve any dynamic target type of a pointer Bernhard Heckel
2016-07-11 15:12 ` [PATCH V3 2/6] Fortran: Resolve dynamic properties of pointer types Bernhard Heckel
2016-07-11 15:12 ` [PATCH V3 1/6] Fortran: Testsuite, fix differences in type naming Bernhard Heckel
2016-07-15 14:03   ` Yao Qi
2016-08-08 11:19 ` [PING][PATCH V3 0/6] Fortran: Resolve target types of pointers Bernhard Heckel
2016-08-15 11:51   ` [PING 2][PATCH " Bernhard Heckel
2016-08-23 13:38     ` [PING 3][PATCH " Bernhard Heckel

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=1468249928-2169-1-git-send-email-bernhard.heckel@intel.com \
    --to=bernhard.heckel@intel.com \
    --cc=brobecker@adacore.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=qiyaoltc@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).