From: Yao Qi <qiyaoltc@gmail.com>
To: Bernhard Heckel <bernhard.heckel@intel.com>
Cc: gdb-patches@sourceware.org, brobecker@adacore.com,
Keven Boell <keven.boell@intel.com>
Subject: Re: [PATCH V2 3/3] fort_dyn_array: Use value constructor instead of raw-buffer manipulation.
Date: Thu, 07 Apr 2016 16:22:00 -0000 [thread overview]
Message-ID: <86mvp5l77f.fsf@gmail.com> (raw)
In-Reply-To: <1459936659-19039-4-git-send-email-bernhard.heckel@intel.com> (Bernhard Heckel's message of "Wed, 6 Apr 2016 11:57:39 +0200")
Bernhard Heckel <bernhard.heckel@intel.com> writes:
> 2014-05-28 Sanimir Agovic <sanimir.agovic@intel.com>
> Keven Boell <keven.boell@intel.com>
> Bernhard Heckel <bernhard.heckel@intel.com>
>
> gdb/Changelog:
> * f-valprint.c (f77_create_arrayprint_offset_tbl): Remove
> function.
> (F77_DIM_SIZE, F77_DIM_OFFSET): Remove macro.
> (f77_print_array_1): Use value_subscript to subscript a
> value array.
> (f77_print_array): Remove call to f77_create_arrayprint_offset_tbl.
> (f_val_print): Use value_field to construct a field value.
>
> gdb/testsuite/Changelog:
> * vla-type.exp: Print structure from toplevel.
Patch is good to me.
--
Yao (齐尧)
next prev parent reply other threads:[~2016-04-07 16:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-06 9:58 [PATCH V2 0/3] fortran: Enable arrays of structures with dynamic member types Bernhard Heckel
2016-04-06 9:58 ` [PATCH V2 3/3] fort_dyn_array: Use value constructor instead of raw-buffer manipulation Bernhard Heckel
2016-04-07 16:22 ` Yao Qi [this message]
2016-04-06 9:58 ` [PATCH V2 1/3] fort_dyn_array: Enable dynamic member types inside a structure Bernhard Heckel
2016-04-07 16:19 ` Yao Qi
2016-04-07 16:26 ` Yao Qi
2016-04-08 6:13 ` Heckel, Bernhard
2016-04-14 13:45 ` Joel Brobecker
2016-04-06 9:58 ` [PATCH V2 2/3] fort_dyn_array: Support evaluation of dynamic elements inside arrays Bernhard Heckel
2016-04-07 16:21 ` 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=86mvp5l77f.fsf@gmail.com \
--to=qiyaoltc@gmail.com \
--cc=bernhard.heckel@intel.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=keven.boell@intel.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).