Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Yao Qi <qiyaoltc@gmail.com>
To: Bernhard Heckel <bernhard.heckel@intel.com>
Cc: Yao Qi <qiyaoltc@gmail.com>,
	Joel Brobecker <brobecker@adacore.com>,
		"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH V4 2/6] Fortran: Resolve dynamic properties of pointer types.
Date: Wed, 05 Oct 2016 09:36:00 -0000	[thread overview]
Message-ID: <CAH=s-PP_n+oUKvAm=B0GKaAk38fR_k6x3+-obyRXLTioJqz1uw@mail.gmail.com> (raw)
In-Reply-To: <8660p7b2xc.fsf@gmail.com>

On Wed, Oct 5, 2016 at 9:44 AM, Yao Qi <qiyaoltc@gmail.com> wrote:
> Bernhard Heckel <bernhard.heckel@intel.com> writes:
>
>> 2016-07-08  Bernhard Heckel  <bernhard.heckel@intel.com>
>>
>> gdb/Changelog:
>>       * gdbtypes.c (resolve_dynamic_types_internal): Resolve pointer types.
>
> This line doesn't match the change, which is in is_dynamic_type_internal.
>
>>         (resolve_dynamic_pointer): New.
>
> Otherwise, patch is good to me.
>

Do we already have a test case which has a Fortran pointer which has
a dynamic associated property?  If no, we need to add one.

Patch 3/6 resolves dynamic target type of a pointer, a pointer points
to a dynamic type, but what does this patch do?

-- 
Yao (齐尧)


  reply	other threads:[~2016-10-05  9:36 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-07  6:38 [PATCH V4 0/6] Fortran: Resolve target types of pointers Bernhard Heckel
2016-09-07  6:38 ` [PATCH V4 2/6] Fortran: Resolve dynamic properties of pointer types Bernhard Heckel
2016-10-05  8:44   ` Yao Qi
2016-10-05  9:36     ` Yao Qi [this message]
2016-10-05 10:07       ` Bernhard Heckel
2016-09-07  6:38 ` [PATCH V4 6/6] Fortran: Testsuite, add cyclic pointers Bernhard Heckel
2016-10-13 14:08   ` Yao Qi
2016-09-07  6:38 ` [PATCH V4 3/6] Typeprint: Resolve any dynamic target type of a pointer Bernhard Heckel
     [not found]   ` <861szvayzg.fsf@gmail.com>
2016-10-05 11:03     ` Bernhard Heckel
2016-10-13 13:41       ` Yao Qi
2016-09-07  6:38 ` [PATCH V4 1/6] Fortran: Testsuite, fix differences in type naming Bernhard Heckel
2016-09-21 15:57   ` Yao Qi
2016-09-07  6:38 ` [PATCH V4 5/6] Resolve dynamic target types of pointers Bernhard Heckel
2016-09-07 14:24   ` Eli Zaretskii
2016-10-13 14:07   ` Yao Qi
2016-10-13 14:57     ` Bernhard Heckel
2016-10-17 10:32       ` Yao Qi
2016-10-17 11:25         ` Bernhard Heckel
2016-10-17 12:18           ` Bernhard Heckel
2016-10-20 11:52             ` Bernhard Heckel
2016-10-20 15:33             ` Yao Qi
2016-11-08  7:07               ` Bernhard Heckel
2016-11-08 11:26                 ` Yao Qi
2016-11-08 12:27                   ` Bernhard Heckel
2016-11-16 12:16                   ` Bernhard Heckel
2016-11-21 15:03                     ` Bernhard Heckel
2016-09-07  6:38 ` [PATCH V4 4/6] Fortran: Typeprint, fix dangling types Bernhard Heckel
2016-10-13 13:53   ` Yao Qi
2016-09-14 12:55 ` [PING][PATCH V4 0/6] Fortran: Resolve target types of pointers Bernhard Heckel
2016-09-28 12:45   ` Bernhard Heckel
2016-10-05  6:03     ` [ping 2][PATCH " Bernhard Heckel
2016-09-21  9:49 ` [ping 2] [PATCH " 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='CAH=s-PP_n+oUKvAm=B0GKaAk38fR_k6x3+-obyRXLTioJqz1uw@mail.gmail.com' \
    --to=qiyaoltc@gmail.com \
    --cc=bernhard.heckel@intel.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    /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