From: Bernhard Heckel <bernhard.heckel@intel.com>
To: qiyaoltc@gmail.com, brobecker@adacore.com
Cc: gdb-patches@sourceware.org, Bernhard Heckel <bernhard.heckel@intel.com>
Subject: [PATCH V5 2/6] Fortran: Resolve dynamic properties of pointer types.
Date: Fri, 14 Oct 2016 11:54:00 -0000 [thread overview]
Message-ID: <1476446044-10408-3-git-send-email-bernhard.heckel@intel.com> (raw)
In-Reply-To: <1476446044-10408-1-git-send-email-bernhard.heckel@intel.com>
In Fortran a pointer may have a dynamic associated property.
2016-07-08 Bernhard Heckel <bernhard.heckel@intel.com>
gdb/Changelog:
* gdbtypes.c (is_dynamic_type_internal): Resolve pointer types.
(resolve_dynamic_pointer): New.
---
gdb/gdbtypes.c | 29 ++++++++++++++++++++++++++++-
1 file changed, 28 insertions(+), 1 deletion(-)
diff --git a/gdb/gdbtypes.c b/gdb/gdbtypes.c
index ad890ca..33a8b7c 100644
--- a/gdb/gdbtypes.c
+++ b/gdb/gdbtypes.c
@@ -1806,7 +1806,8 @@ is_dynamic_type_internal (struct type *type, int top_level)
type = check_typedef (type);
/* We only want to recognize references at the outermost level. */
- if (top_level && TYPE_CODE (type) == TYPE_CODE_REF)
+ if (top_level &&
+ (TYPE_CODE (type) == TYPE_CODE_REF || TYPE_CODE (type) == TYPE_CODE_PTR))
type = check_typedef (TYPE_TARGET_TYPE (type));
/* Types that have a dynamic TYPE_DATA_LOCATION are considered
@@ -2105,6 +2106,28 @@ resolve_dynamic_struct (struct type *type,
return resolved_type;
}
+/* Worker for pointer types. */
+
+static struct type *
+resolve_dynamic_pointer (struct type *type,
+ struct property_addr_info *addr_stack)
+{
+ struct dynamic_prop *prop;
+ CORE_ADDR value;
+
+ type = copy_type (type);
+
+ /* Resolve associated property. */
+ prop = TYPE_ASSOCIATED_PROP (type);
+ if (prop != NULL && dwarf2_evaluate_property (prop, NULL, addr_stack, &value))
+ {
+ TYPE_DYN_PROP_ADDR (prop) = value;
+ TYPE_DYN_PROP_KIND (prop) = PROP_CONST;
+ }
+
+ return type;
+}
+
/* Worker for resolved_dynamic_type. */
static struct type *
@@ -2153,6 +2176,10 @@ resolve_dynamic_type_internal (struct type *type,
break;
}
+ case TYPE_CODE_PTR:
+ resolved_type = resolve_dynamic_pointer (type, addr_stack);
+ break;
+
case TYPE_CODE_ARRAY:
resolved_type = resolve_dynamic_array (type, addr_stack);
break;
--
2.7.1.339.g0233b80
next prev parent reply other threads:[~2016-10-14 11:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-14 11:54 [PATCH V5 0/6] Fortran: Resolve target types of pointers Bernhard Heckel
2016-10-14 11:54 ` [PATCH V5 1/6] Fortran: Testsuite, fix differences in type naming Bernhard Heckel
2016-10-14 11:54 ` Bernhard Heckel [this message]
2016-10-14 11:54 ` [PATCH V5 4/6] Fortran: Typeprint, fix dangling types Bernhard Heckel
2016-10-14 11:54 ` [PATCH V5 5/6] Resolve dynamic target types of pointers Bernhard Heckel
2016-10-14 13:05 ` Eli Zaretskii
2016-10-14 11:54 ` [PATCH V5 6/6] Fortran: Testsuite, add cyclic pointers Bernhard Heckel
2016-10-14 11:54 ` [PATCH V5 3/6] Typeprint: Resolve any dynamic target type of a pointer Bernhard Heckel
2016-10-14 13:21 ` [PATCH V5 0/6] Fortran: Resolve target types of pointers Yao Qi
2016-10-17 7:11 ` 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=1476446044-10408-3-git-send-email-bernhard.heckel@intel.com \
--to=bernhard.heckel@intel.com \
--cc=brobecker@adacore.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