From: Bernhard Heckel <bernhard.heckel@intel.com>
To: qiyaoltc@gmail.com
Cc: gdb-patches@sourceware.org, Bernhard Heckel <bernhard.heckel@intel.com>
Subject: [PATCH 0/4] Fortran, typeprint
Date: Tue, 10 May 2016 14:16:00 -0000 [thread overview]
Message-ID: <1462889739-30359-1-git-send-email-bernhard.heckel@intel.com> (raw)
This series fixes various issues in fortran's typeprint.
Tested on Ubuntu1504, Fedora23, Fedora21
Bernhard Heckel (4):
Fortran, typeprint: Fix wrong indentation when ptype nested
structures.
Fortran, typeprint: Take level of details into account when printing
elements of a structure.
Fortran, typeprint: Decrease level of details when printing elements
of a structure.
Fortran, typeprint: Forward level of details to be printed for
pointers.
gdb/f-typeprint.c | 33 ++++++++++--------
gdb/testsuite/gdb.fortran/type.f90 | 26 +++++++++++++-
gdb/testsuite/gdb.fortran/whatis_type.exp | 53 +++++++++++++++++++++++-----
3 files changed, 87 insertions(+), 25 deletions(-)
next reply other threads:[~2016-05-10 14:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-10 14:16 Bernhard Heckel [this message]
2016-05-10 14:16 ` [PATCH 3/4] Fortran, typeprint: Decrease level of details when printing elements of a structure Bernhard Heckel
2016-05-11 13:40 ` Yao Qi
2016-05-12 8:00 ` Bernhard Heckel
2016-05-10 14:16 ` [PATCH 1/4] Fortran, typeprint: Fix wrong indentation when ptype nested structures Bernhard Heckel
2016-05-11 11:58 ` Yao Qi
2016-05-11 11:59 ` Yao Qi
2016-05-10 14:16 ` [PATCH 2/4] Fortran, typeprint: Take level of details into account when printing elements of a structure Bernhard Heckel
2016-05-11 12:09 ` Yao Qi
2016-05-12 12:06 ` Yao Qi
2016-05-12 12:42 ` Bernhard Heckel
2016-05-10 14:18 ` [PATCH 4/4] Fortran, typeprint: Forward level of details to be printed for pointers Bernhard Heckel
2016-05-11 13:42 ` Yao Qi
2016-05-13 14:27 ` Yao Qi
2016-05-13 15:55 ` Yao Qi
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=1462889739-30359-1-git-send-email-bernhard.heckel@intel.com \
--to=bernhard.heckel@intel.com \
--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