public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Bernhard Heckel <bernhard.heckel@intel.com>
To: qiyaoltc@gmail.com
Cc: gdb-patches@sourceware.org, Bernhard Heckel <bernhard.heckel@intel.com>
Subject: [PATCH V2 7/7] Fortran, typeprint: Forward level of details to be printed for pointers.
Date: Fri, 13 May 2016 09:35:00 -0000	[thread overview]
Message-ID: <1463132086-17451-8-git-send-email-bernhard.heckel@intel.com> (raw)
In-Reply-To: <1463132086-17451-1-git-send-email-bernhard.heckel@intel.com>

Variable "show" was hardcoded to zero for pointer and reference types.
This implementation didn't allow a correct "whatis" print
for those types and results in same output for "ptype" and "whatis".

Before:
(gdb) whatis t3p
type = PTR TO -> ( Type t3
    integer(kind=4) :: t3_i
    Type t2 :: t2_n
End Type t3 )

After:
(gdb) whatis t3p
type = PTR TO -> ( Type t3 )

2016-05-09  Bernhard Heckel  <bernhard.heckel@intel.com>

gdb/Changelog:
	* f-typeprint.c (f_type_print_base): Replace 0 by show.

gdb/testsuite/Changelog:
	* gdb.fortran/type.f90: Add pointer variable.
	* gdb.fortran/whatis_type.exp: Add whatis/ptype of pointers.

---
 gdb/f-typeprint.c                         |  4 ++--
 gdb/testsuite/gdb.fortran/type.f90        | 10 ++++++++--
 gdb/testsuite/gdb.fortran/whatis_type.exp |  7 +++++++
 3 files changed, 17 insertions(+), 4 deletions(-)

diff --git a/gdb/f-typeprint.c b/gdb/f-typeprint.c
index 350def0..920c21f 100644
--- a/gdb/f-typeprint.c
+++ b/gdb/f-typeprint.c
@@ -308,12 +308,12 @@ f_type_print_base (struct type *type, struct ui_file *stream, int show,
 
     case TYPE_CODE_PTR:
       fprintf_filtered (stream, "PTR TO -> ( ");
-      f_type_print_base (TYPE_TARGET_TYPE (type), stream, 0, level);
+      f_type_print_base (TYPE_TARGET_TYPE (type), stream, show, level);
       break;
 
     case TYPE_CODE_REF:
       fprintf_filtered (stream, "REF TO -> ( ");
-      f_type_print_base (TYPE_TARGET_TYPE (type), stream, 0, level);
+      f_type_print_base (TYPE_TARGET_TYPE (type), stream, show, level);
       break;
 
     case TYPE_CODE_VOID:
diff --git a/gdb/testsuite/gdb.fortran/type.f90 b/gdb/testsuite/gdb.fortran/type.f90
index 00dc650..ad3d6ee 100644
--- a/gdb/testsuite/gdb.fortran/type.f90
+++ b/gdb/testsuite/gdb.fortran/type.f90
@@ -33,7 +33,10 @@ program type
 
   type (t1) :: t1v
   type (t2) :: t2v
-  type (t3) :: t3v
+  type (t3), target :: t3v
+  type(t3), pointer :: t3p
+
+  nullify (t3p)
 
   t1v%t1_i = 42
   t1v%t1_r = 42.24
@@ -42,6 +45,9 @@ program type
   t2v%t1_n%t1_i = 21
   t3v%t3_i = 3
   t3v%t2_n%t2_i = 32
-  t3v%t2_n%t1_n%t1_i = 321    ! bp1
+  t3v%t2_n%t1_n%t1_i = 321
+
+  t3p => t3v
+  nullify (t3p)    ! bp1
 
 end program type
diff --git a/gdb/testsuite/gdb.fortran/whatis_type.exp b/gdb/testsuite/gdb.fortran/whatis_type.exp
index 955f853..6ebcb52 100644
--- a/gdb/testsuite/gdb.fortran/whatis_type.exp
+++ b/gdb/testsuite/gdb.fortran/whatis_type.exp
@@ -44,6 +44,7 @@ gdb_test "whatis t2" "type = Type t2"
 gdb_test "whatis t2v" "type = Type t2"
 gdb_test "whatis t3" "type = Type t3"
 gdb_test "whatis t3v" "type = Type t3"
+gdb_test "whatis t3p" "type = PTR TO -> \\( Type t3 \\)"
 
 gdb_test "ptype t1" \
   [multi_line "type = Type t1" \
@@ -69,3 +70,9 @@ gdb_test "ptype t3v" \
               "    $int :: t3_i" \
               "    Type t2 :: t2_n" \
               "End Type t3"]
+
+gdb_test "ptype t3p" \
+  [multi_line "type = PTR TO -> \\( Type t3" \
+              "    $int :: t3_i" \
+              "    Type t2 :: t2_n" \
+              "End Type t3 \\)"]
-- 
2.7.1.339.g0233b80

  parent reply	other threads:[~2016-05-13  9:35 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-13  9:34 [PATCH V2 0/7] Fortran, typeprint Bernhard Heckel
2016-05-13  9:35 ` [PATCH V2 2/7] Fortran, typeprint: Fix wrong indentation when ptype nested structures Bernhard Heckel
2016-05-13 14:05   ` Yao Qi
2016-05-13  9:35 ` [PATCH V2 4/7] Fortran, typeprint: Decrease level of details when printing elements of a structure Bernhard Heckel
2016-05-13 14:12   ` Yao Qi
2016-05-13  9:35 ` Bernhard Heckel [this message]
2016-05-13 15:57   ` [PATCH V2 7/7] Fortran, typeprint: Forward level of details to be printed for pointers Yao Qi
2016-05-13  9:35 ` [PATCH V2 1/7] Fortran, testsuite: Use multi_line in whatis_type testcase Bernhard Heckel
2016-05-13 14:01   ` Yao Qi
2016-05-13  9:35 ` [PATCH V2 5/7] Fortran, testsuite: Add testcases for nested structures Bernhard Heckel
2016-05-13 14:17   ` Yao Qi
2016-05-13  9:35 ` [PATCH V2 6/7] Fortran, testsuite: Fix duplicate testcase name Bernhard Heckel
2016-05-13 14:20   ` Yao Qi
2016-05-17 12:53     ` Bernhard Heckel
2016-05-18 13:29       ` Bernhard Heckel
2016-05-23 11:15       ` [PING][PATCH " Bernhard Heckel
2016-05-23 13:22       ` [PATCH " Yao Qi
2016-05-13  9:35 ` [PATCH V2 3/7] Fortran, typeprint: Take level of details into account when printing elements of a structure Bernhard Heckel
2016-05-13 15:58   ` Yao Qi
2016-05-25  7:13 ` [PUSHED][PATCH V2 0/7] Fortran, typeprint 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=1463132086-17451-8-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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).