From: Bernhard Heckel <bernhard.heckel@intel.com>
To: gdb-patches@sourceware.org
Cc: qiyaoltc@gmail.com, brobecker@adacore.com, eliz@gnu.org
Subject: [Pushed][PATCH V4 0/3] fortran: Enable arrays of structures with dynamic member types.
Date: Tue, 26 Apr 2016 15:04:00 -0000 [thread overview]
Message-ID: <571F833D.1070602@intel.com> (raw)
In-Reply-To: <1460702519-30622-1-git-send-email-bernhard.heckel@intel.com>
On 15/04/2016 08:41, Bernhard Heckel wrote:
> Addressed in V4:
> [Patch V4 1/3]
> * gdbtypes.c (resolve_dynamic_struct): extra pair of parens and rephrase comment.
> (remove_dynamic_property): Fix misspelled word.
> value.c (set_internal_var): Add comments.
> Addressed in V3:
> [Patch V3 1/3]
> * value.c (value_address): Explicit compare against NULL.
> (set_value_component_location): Fix line too long.
> (set_value_component_location): Explicit compare against NULL.
> (clear_internalvar): Explicit compare against NULL.
> (set_internalvar): Fix line too long.
> Addressed in V2:
> * Commit-Msg: Added missing changes and added some more comments.
> * NEWS: Added new fortran features.
> * gdbtypes.c (several comments): Two blanks after dot.
> (resolve_dynamic_struct): Changed comment why length is not changed for fortran.
> * valarith.c (value_subscripted_rvalue): Replace variable by NULL.
> This patch series enables the user to evaluate:
> 1. Local structures with dynamic member types.
> 2. Local arrays of structs with dynamic member types.
> 3. Dynamic arrays of structs with static and/or dynamic member types.
>
> Bernhard Heckel (2):
> fort_dyn_array: Enable dynamic member types inside a structure.
> fort_dyn_array: Support evaluation of dynamic elements inside arrays.
>
> Keven Boell (1):
> fort_dyn_array: Use value constructor instead of raw-buffer
> manipulation.
>
> gdb/NEWS | 3 +
> gdb/f-valprint.c | 118 +++++++++----------------
> gdb/gdbtypes.c | 44 +++++++++-
> gdb/gdbtypes.h | 3 +
> gdb/testsuite/gdb.fortran/vla-type.exp | 153 +++++++++++++++++++++++++++++++++
> gdb/testsuite/gdb.fortran/vla-type.f90 | 104 ++++++++++++++++++++++
> gdb/valarith.c | 8 ++
> gdb/value.c | 39 ++++++++-
> 8 files changed, 387 insertions(+), 85 deletions(-)
> create mode 100755 gdb/testsuite/gdb.fortran/vla-type.exp
> create mode 100755 gdb/testsuite/gdb.fortran/vla-type.f90
>
Pushed the series.
Thanks for reviewing
Bernhard
Intel Deutschland GmbH
Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de
Managing Directors: Christin Eisenschmid, Christian Lamprechter
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928
prev parent reply other threads:[~2016-04-26 15:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-15 6:42 [PATCH " Bernhard Heckel
2016-04-15 6:42 ` [PATCH V4 1/3] fort_dyn_array: Enable dynamic member types inside a structure Bernhard Heckel
2016-04-21 6:03 ` [PING][PATCH V4 0/3] fortran: Enable arrays of structures with dynamic member types Bernhard Heckel
2016-04-26 12:10 ` [PING 2][PATCH " Bernhard Heckel
2016-04-26 13:48 ` Eli Zaretskii
2016-04-26 15:04 ` Bernhard Heckel [this message]
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=571F833D.1070602@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).