public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: Damian Rouson <damian@sourceryinstitute.org>
To: Alessandro Fanfarillo <fanfarillo.gcc@gmail.com>
Cc: Tobias Burnus <tobias.burnus@physik.fu-berlin.de>,
	gcc-patches <gcc-patches@gcc.gnu.org>,
	gfortran <fortran@gcc.gnu.org>
Subject: Re: [Fortran, Patch] (RFC, Coarray) Implement TS18508's EVENTS
Date: Wed, 25 Nov 2015 19:14:00 -0000	[thread overview]
Message-ID: <40F9DF74-E703-41B6-A019-FCB8BEE37C6B@sourceryinstitute.org> (raw)
In-Reply-To: <CAHqFgjVtwTSsOtcTT+BedhzWeDBo4EZp7uLPHKz=PBQjTgH5HA@mail.gmail.com>


> On Nov 25, 2015, at 9:24 AM, Alessandro Fanfarillo <fanfarillo.gcc@gmail.com> wrote:
> 
> Dear all,
> 
> in attachment the previous patch compatible with the current trunk.
> The patch also includes the changes introduced in the latest TS 18508.
> 
> Built and regtested on x86_64-pc-linux-gnu.
> 
> PS: I will add the test cases in a different patch.

All,

As I mentioned previously, WG5 approved the latest TS 18508 document in September and forwarded it to SC22 for approval for publishing so it is essentially final.  This is an opportune time to commit the feature. I believe it also puts gfortran in the lead on Fortran 2015 parallel programming support.  I don’t think even the Cray compiler supports EVENTs yet.  Hopefully this is ok for committing during Stage 3 given that the original version of the patch was submitted by Tobias in April.

This feature could have significant, positive impact on parallel performance so it will be exciting to see it hit the trunk.  If it gets committed before my next short course, December 7-8, then I’ll incorporate some discussion of EVENTs into the course.

Damian

  reply	other threads:[~2015-11-25 19:14 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-29  7:55 Tobias Burnus
2015-11-25 17:25 ` Alessandro Fanfarillo
2015-11-25 19:14   ` Damian Rouson [this message]
2015-11-25 22:28   ` Paul Richard Thomas
2015-11-25 22:58     ` Steve Kargl
2015-11-26 16:51   ` Steve Kargl
2015-11-26 17:55     ` Alessandro Fanfarillo
2015-12-02 14:16     ` Alessandro Fanfarillo
2015-12-02 22:00       ` Steve Kargl
2015-12-03 19:46         ` Alessandro Fanfarillo
2015-12-17 12:22         ` Alessandro Fanfarillo
2015-12-17 14:57           ` Steve Kargl
2015-12-17 16:19             ` Alessandro Fanfarillo
2016-02-11 23:04               ` Alessandro Fanfarillo
2016-02-12 16:32                 ` Alessandro Fanfarillo

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=40F9DF74-E703-41B6-A019-FCB8BEE37C6B@sourceryinstitute.org \
    --to=damian@sourceryinstitute.org \
    --cc=fanfarillo.gcc@gmail.com \
    --cc=fortran@gcc.gnu.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=tobias.burnus@physik.fu-berlin.de \
    /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).