public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Yao Qi <qiyaoltc@gmail.com>
To: Bernhard Heckel <bernhard.heckel@intel.com>
Cc: qiyaoltc@gmail.com,  gdb-patches@sourceware.org,  brobecker@adacore.com
Subject: Re: [PATCH V4 3/3] fortran: Testsuite, fix different type naming across compilers.
Date: Mon, 18 Apr 2016 10:29:00 -0000	[thread overview]
Message-ID: <86r3e3jjmu.fsf@gmail.com> (raw)
In-Reply-To: <1460974046-1281-4-git-send-email-bernhard.heckel@intel.com>	(Bernhard Heckel's message of "Mon, 18 Apr 2016 12:07:26 +0200")

Bernhard Heckel <bernhard.heckel@intel.com> writes:

> 	* lib/fortran.exp: Add type definition for gfortran and ifort compiler.

the proc names should be mentioned in the last entry,

	* lib/fortran.exp (fortran_int4): New procedure.
        (fortran_real4, fortran_real8, fortran_complex4): Likewise.
        (fortran_logical4): Likewise.

Otherwise, patch is good to me.

-- 
Yao (齐尧)

  reply	other threads:[~2016-04-18 10:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-18 10:07 [PATCH V4 0/3] " Bernhard Heckel
2016-04-18 10:07 ` [PATCH V4 2/3] Testsuite: Fix compiling of shared libraries with ICC Bernhard Heckel
2016-04-18 10:26   ` Yao Qi
2016-04-18 12:18     ` [Pushed][PATCH " Heckel, Bernhard
2016-04-18 10:07 ` [PATCH V4 3/3] fortran: Testsuite, fix different type naming across compilers Bernhard Heckel
2016-04-18 10:29   ` Yao Qi [this message]
2016-04-18 12:19     ` [Pushed][PATCH " Heckel, Bernhard
2016-04-18 10:08 ` [PATCH V4 1/3] testsuite: Support detection of Intel compilers via test_compiler_version Bernhard Heckel
2016-04-18 10:26   ` Yao Qi
2016-04-18 12:17     ` [Pushed][PATCH " Heckel, Bernhard

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=86r3e3jjmu.fsf@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).