From: "Heckel, Bernhard" <bernhard.heckel@intel.com>
To: eliz@gnu.org
Cc: gdb-patches@sourceware.org, brobecker@adacore.com,
Yao Qi <qiyaoltc@gmail.com>
Subject: Re: [PATCH V2 1/3] fort_dyn_array: Enable dynamic member types inside a structure.
Date: Fri, 08 Apr 2016 06:13:00 -0000 [thread overview]
Message-ID: <57074BF1.7000708@intel.com> (raw)
In-Reply-To: <86inztl71v.fsf@gmail.com>
On 07/04/2016 18:25, Yao Qi wrote:
> Bernhard Heckel <bernhard.heckel@intel.com> writes:
>
>> diff --git a/gdb/NEWS b/gdb/NEWS
>> index be15902..056d56c 100644
>> --- a/gdb/NEWS
>> +++ b/gdb/NEWS
>> @@ -3,6 +3,9 @@
>>
>> *** Changes since GDB 7.11
>>
>> +* Fortran: Support structures with fields of dynamic types and
>> + arrays of dynamic types.
>> +
> To be clear, NEWS bits still need Eli's review.
>
Loop-in Eli
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
next prev parent reply other threads:[~2016-04-08 6:13 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
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 [this message]
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=57074BF1.7000708@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).