From: "Dominique d'Humières" <dominiq@lps.ens.fr>
To: "jvdelisle@charter.net" <jvdelisle@charter.net>
Cc: gfortran <fortran@gcc.gnu.org>, gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: PATCH ATTACHED Re: [PATCH, Fortran] PR78659 Spurious "requires DTIO" reported against namelist statement
Date: Sat, 13 May 2017 11:56:00 -0000 [thread overview]
Message-ID: <65CBC4BE-7A9F-4312-82EC-CF4F6EFC408F@lps.ens.fr> (raw)
Dear Jerry,
> And the actual patch ...
Are you sure this the right patch? It seems mostly applied on trunk.
TIA
Dominique
PS I saw some ‘return 1;’ which should probably ‘return true;’
next reply other threads:[~2017-05-13 11:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-13 11:56 Dominique d'Humières [this message]
2017-05-13 16:31 ` Jerry DeLisle
-- strict thread matches above, loose matches on Subject: below --
2017-05-11 15:35 Jerry DeLisle
2017-05-11 15:46 ` PATCH ATTACHED " Jerry DeLisle
2017-05-11 17:23 ` Paul Richard Thomas
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=65CBC4BE-7A9F-4312-82EC-CF4F6EFC408F@lps.ens.fr \
--to=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).