From: Paul Richard Thomas <paul.richard.thomas@gmail.com>
To: "Dominique d'Humières" <dominiq@lps.ens.fr>
Cc: "fortran@gcc.gnu.org" <fortran@gcc.gnu.org>,
"jvdelisle@charter.net" <jvdelisle@charter.net>,
gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH gfortran] PR 60751 - Extra comma in WRITE statement not diagnosed
Date: Sat, 11 Jun 2016 18:35:00 -0000 [thread overview]
Message-ID: <CAGkQGi++KBwXsxNRfA8Et+1t1+oiQtsD8hxqs-+00m4zCS4aNw@mail.gmail.com> (raw)
In-Reply-To: <D1B97C07-DD7E-4513-A50A-728E83E8804B@lps.ens.fr>
Dear Dominique,
That looks OK to me for 5 through 7-branches.
Thanks
Paul
On 10 June 2016 at 19:05, Dominique d'Humières <dominiq@lps.ens.fr> wrote:
> The attached patch fixes pr60751 by allowing extra comma in WRITE statement for std=legacy only, tested on x86_64-apple-darwin15. Is it OK for trunk, and the gcc-5 and 6 branches?
>
> TIA
>
> Dominique
>
--
The difference between genius and stupidity is; genius has its limits.
Albert Einstein
prev parent reply other threads:[~2016-06-11 18:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-10 17:05 Dominique d'Humières
2016-06-11 18:35 ` Paul Richard Thomas [this message]
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=CAGkQGi++KBwXsxNRfA8Et+1t1+oiQtsD8hxqs-+00m4zCS4aNw@mail.gmail.com \
--to=paul.richard.thomas@gmail.com \
--cc=dominiq@lps.ens.fr \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=jvdelisle@charter.net \
/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).