public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Yao Qi <qiyaoltc@gmail.com>
To: Tim Wiederhake <tim.wiederhake@intel.com>
Cc: gdb-patches@sourceware.org,  Bernhard Heckel <bernhard.heckel@intel.com>
Subject: Re: [PATCH 2/4] Fortran: Testsuite, fix differences in type naming.
Date: Mon, 04 Sep 2017 13:25:00 -0000	[thread overview]
Message-ID: <864lsieguc.fsf@gmail.com> (raw)
In-Reply-To: <1503317966-12486-3-git-send-email-tim.wiederhake@intel.com> (Tim	Wiederhake's message of "Mon, 21 Aug 2017 14:19:24 +0200")

Tim Wiederhake <tim.wiederhake@intel.com> writes:

> gdb/Testsuite/Changelog:

s/Testsuite/testsuite/

> 	* gdb.fortran/vla-value.exp: Use type names defined in
> 	libfortran.

"Use type name from fortran_real4".

> 	* gdb.mi/mi-var-child-f.exp: Likewise.

"Use type name from fortran_int4".

> 	* gdb.mi/mi-vla-fortran.exp: Likewise.

otherwise, patch is good to me.

-- 
Yao (齐尧)

  reply	other threads:[~2017-09-04 13:25 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-21 12:20 [PATCH 0/4] More Fortran Patches Tim Wiederhake
2017-08-21 12:20 ` [PATCH 1/4] Fix indentation for printing Fortran types with pointers Tim Wiederhake
2017-09-04 13:35   ` Yao Qi
2017-09-08 13:19     ` Wiederhake, Tim
2017-08-21 12:20 ` [PATCH 3/4] fortran: Testsuite, fix typos in vla-value Tim Wiederhake
2017-09-04 13:26   ` Yao Qi
2017-09-08 13:17     ` Wiederhake, Tim
2017-08-21 12:20 ` [PATCH 2/4] Fortran: Testsuite, fix differences in type naming Tim Wiederhake
2017-09-04 13:25   ` Yao Qi [this message]
2017-09-08 13:17     ` Wiederhake, Tim
2017-08-21 12:20 ` [PATCH 4/4] Remove C/C++ relevant code in Fortran specific file Tim Wiederhake
2017-09-04 13:32   ` Yao Qi
2017-09-08 13:18     ` Wiederhake, Tim

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=864lsieguc.fsf@gmail.com \
    --to=qiyaoltc@gmail.com \
    --cc=bernhard.heckel@intel.com \
    --cc=gdb-patches@sourceware.org \
    --cc=tim.wiederhake@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).