From: Damian Rouson <damian@sourceryinstitute.org>
To: gfortran <fortran@gcc.gnu.org>
Cc: "Alessandro Fanfarillo" <elfanfa@ucar.edu>,
"Soren Rasmussen" <s.c.rasmussen@gmail.com>,
"Filippone, Salvatore" <salvatore.filippone@cranfield.ac.uk>
Subject: Re: Draft patch: Fortran 2015 teams support and extension
Date: Wed, 27 Sep 2017 17:45:00 -0000 [thread overview]
Message-ID: <etPan.59cbe3be.559c0124.19a@sourceryinstitute.org> (raw)
In-Reply-To: <etPan.59b85079.5096c97c.18b@sourceryinstitute.org>
**PING**
Soren has arrived at Cranfield University to begin his Ph.D. studies on work that is expected to include further development of the Fortran 2015 teams feature. If anyone is available to review the patch sent on September 12, please let us know. If so desired, I can provide some funding for the review.
Damian
On September 12, 2017 at 2:24:10 PM, Damian Rouson (damian@sourceryinstitute.org) wrote:
All,
With Alessandro’s approval, I’m submitting the attached draft patch showing his edits for supporting Fortran 2015 teams, which in my estimation is the one remaining big piece of Fortran 2015 missing from gfortran. The patch also adds an extension: a get_communicator function that returns an MPI communicator if libcaf_mpi is the linked ABI. There are known issues with the team_number function, but it works for the attached tests. I believe Alessandro might have time to work on team_number in a couple of weeks. Also, there are known issues with teams that contain failed images. I’m hopeful that entering Cranfield University Ph.D. student Soren Rasmussen will work on the interaction with failed images as a much longer-term project that will not make it into this patch.
I’m submitting this now to request a review that will give us early guidance regarding the necessary steps for this patch to be approved for committing to the trunk. I’ve also created a pull request on GitHub that provides a graphical interface to all the changes and allows for adding comments, including comments tied to specific lines:
https://github.com/gcc-mirror/gcc/pull/14
It would be great if review comments could be inserted at the above URL (click the Commits tab and then the first commit), but replies to this email are also welcome. To test this patch, build the opencoarrays-teams branch of OpenCoarrays and the teams branch of the following fork of the GCC git mirror: https://github.com/sourceryinstitute/gcc.
I have not created a ChangeLog but would be glad to do so if someone can explain the process unless that’s too preliminary at this stage.
Damian
next prev parent reply other threads:[~2017-09-27 17:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-12 21:24 Damian Rouson
2017-09-27 17:45 ` Damian Rouson [this message]
2017-09-28 13:32 ` Paul Richard Thomas
2017-10-07 5:15 ` Jerry DeLisle
2017-10-08 0:07 ` Damian Rouson
2017-10-08 12:40 ` Paul Richard Thomas
2017-10-25 2:46 ` Jerry DeLisle
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=etPan.59cbe3be.559c0124.19a@sourceryinstitute.org \
--to=damian@sourceryinstitute.org \
--cc=elfanfa@ucar.edu \
--cc=fortran@gcc.gnu.org \
--cc=s.c.rasmussen@gmail.com \
--cc=salvatore.filippone@cranfield.ac.uk \
/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).