From: Mikael Morin <mikael.morin@sfr.fr>
To: Damian Rouson <damian@sourceryinstitute.org>
Cc: Alessandro Fanfarillo <fanfarillo.gcc@gmail.com>,
gcc-patches <gcc-patches@gcc.gnu.org>,
gfortran <fortran@gcc.gnu.org>
Subject: Re: [Fortran, Patch] Passing function pointer to co_reduce
Date: Fri, 17 Jul 2015 09:28:00 -0000 [thread overview]
Message-ID: <55A8C4A5.3070308@sfr.fr> (raw)
In-Reply-To: <CB7A1507-16A2-4AFE-B2C4-65FE5C6C753D@sourceryinstitute.org>
Le 16/07/2015 16:34, Damian Rouson a écrit :
> Alternatively, if itÂ’s easy, please feel free to add the directives and commit.
>
It's not very difficult, but there is some pain getting the number of
escape backslashes right.
Never mind, I'll take care of it all.
Mikael
next prev parent reply other threads:[~2015-07-17 9:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-13 15:31 Alessandro Fanfarillo
2015-07-15 13:13 ` Mikael Morin
2015-07-16 14:58 ` Damian Rouson
2015-07-17 9:28 ` Mikael Morin [this message]
2015-07-17 13:54 ` Mikael Morin
2015-07-17 14:42 ` Damian Rouson
2015-07-17 14:43 ` Alessandro Fanfarillo
2015-07-17 18:47 ` Steve Kargl
2015-07-17 19:47 ` Mikael Morin
2015-07-17 20:47 ` Mikael Morin
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=55A8C4A5.3070308@sfr.fr \
--to=mikael.morin@sfr.fr \
--cc=damian@sourceryinstitute.org \
--cc=fanfarillo.gcc@gmail.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.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).