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: Joel Brobecker <brobecker@adacore.com>,
		"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH V5 0/6] Fortran: Resolve target types of pointers.
Date: Fri, 14 Oct 2016 13:21:00 -0000	[thread overview]
Message-ID: <CAH=s-PPezzmhLX_Ap3J8Ch-S5UhB9aJXmcxt3G6NqrtNDP8stg@mail.gmail.com> (raw)
In-Reply-To: <1476446044-10408-1-git-send-email-bernhard.heckel@intel.com>

On Fri, Oct 14, 2016 at 12:53 PM, Bernhard Heckel
<bernhard.heckel@intel.com> wrote:
> Addressed in V5:
> - Fixed several "line to long" issues
> - include <cstddef>
> - Don't compare bool-like values against 0/1

I don't think my comments here
https://sourceware.org/ml/gdb-patches/2016-10/msg00360.html
are addressed in this version.

-- 
Yao (齐尧)


  parent reply	other threads:[~2016-10-14 13:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-14 11:54 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 11:54 ` [PATCH V5 2/6] Fortran: Resolve dynamic properties of pointer 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 4/6] Fortran: Typeprint, fix dangling types Bernhard Heckel
2016-10-14 11:54 ` [PATCH V5 6/6] Fortran: Testsuite, add cyclic pointers Bernhard Heckel
2016-10-14 11:54 ` [PATCH V5 1/6] Fortran: Testsuite, fix differences in type naming Bernhard Heckel
2016-10-14 13:21 ` Yao Qi [this message]
2016-10-17  7:11   ` [PATCH V5 0/6] Fortran: Resolve target types of pointers 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-PPezzmhLX_Ap3J8Ch-S5UhB9aJXmcxt3G6NqrtNDP8stg@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