From: Yao Qi <qiyaoltc@gmail.com>
To: Bernhard Heckel <bernhard.heckel@intel.com>
Cc: eliz@gnu.org, brobecker@adacore.com, gdb-patches@sourceware.org
Subject: Re: [PATCH V3 1/6] Fortran: Testsuite, fix differences in type naming.
Date: Fri, 15 Jul 2016 14:03:00 -0000 [thread overview]
Message-ID: <86d1mfdmmt.fsf@gmail.com> (raw)
In-Reply-To: <1468249928-2169-2-git-send-email-bernhard.heckel@intel.com> (Bernhard Heckel's message of "Mon, 11 Jul 2016 17:12:03 +0200")
Bernhard Heckel <bernhard.heckel@intel.com> writes:
Patch is good to me.
> +# Depending on the compiler being used, the type names can be printed differently.
> +set real [fortran_real4]
> +
This line is too long, multiple instances of this problem.
--
Yao (齐尧)
next prev parent reply other threads:[~2016-07-15 14:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-11 15:12 [PATCH V3 0/6] Fortran: Resolve target types of pointers Bernhard Heckel
2016-07-11 15:12 ` [PATCH V3 1/6] Fortran: Testsuite, fix differences in type naming Bernhard Heckel
2016-07-15 14:03 ` Yao Qi [this message]
2016-07-11 15:12 ` [PATCH V3 2/6] Fortran: Resolve dynamic properties of pointer types Bernhard Heckel
2016-07-11 15:12 ` [PATCH V3 3/6] Typeprint: Resolve any dynamic target type of a pointer Bernhard Heckel
2016-07-11 15:12 ` [PATCH V3 6/6] Fortran: Testsuite, add cyclic pointers Bernhard Heckel
2016-07-11 15:12 ` [PATCH V3 4/6] Fortran: Typeprint, fix dangling types Bernhard Heckel
2016-07-11 15:12 ` [PATCH V3 5/6] Resolve dynamic target types of pointers Bernhard Heckel
2016-07-11 16:25 ` Eli Zaretskii
2016-08-08 11:19 ` [PING][PATCH V3 0/6] Fortran: Resolve " Bernhard Heckel
2016-08-15 11:51 ` [PING 2][PATCH " Bernhard Heckel
2016-08-23 13:38 ` [PING 3][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=86d1mfdmmt.fsf@gmail.com \
--to=qiyaoltc@gmail.com \
--cc=bernhard.heckel@intel.com \
--cc=brobecker@adacore.com \
--cc=eliz@gnu.org \
--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).