From: Damian Rouson <damian@sourceryinstitute.org>
To: ams@codesourcery.com
Cc: Janne Blomqvist <blomqvist.janne@gmail.com>,
Toon Moene <toon@moene.org>,
gcc patches <gcc-patches@gcc.gnu.org>,
gfortran <fortran@gcc.gnu.org>
Subject: Re: [PATCH 08/25] Fix co-array allocation
Date: Wed, 19 Sep 2018 23:09:00 -0000 [thread overview]
Message-ID: <CACR8rveFtft+Sco3s0xz=Lr6Wfshjz-BbEb-ozbjH+2AfMApkA@mail.gmail.com> (raw)
In-Reply-To: <b79ef46e-563c-f1c8-4f48-c65c5b6ad0da@codesourcery.com>
On Wed, Sep 19, 2018 at 3:30 PM Andrew Stubbs <ams@codesourcery.com> wrote:
>
> If you want to port your tool to GCN that would be cool, but I suspect
> non-trivial.
>
To clarify, OpenCoarrays is not a tool. It is the parallel ABI required to
create executable programs capable of executing in multiple images as
required by the Fortran 2008 standard. Multi-image execution is the reason
coarray features exist so I hope the maintainers won't approve a patch that
impacts coarray features but has not been tested against OpenCoarrays,
which has its own test suite. Again, I would be glad to assist with
installing OpenCoarrays on your system. Whether it's trivial or not, it's
essential to protect against breaking a large feature set that is part of
Fortran 2008 and 2018.
Damian
next prev parent reply other threads:[~2018-09-19 23:09 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <024e798b9539b765a1259cfc9cb2f1dc480b24ca.1536144068.git.ams@codesourcery.com>
2018-09-05 16:54 ` Fwd: " Toon Moene
2018-09-05 17:02 ` Bernhard Reutner-Fischer
2018-09-05 18:07 ` Janne Blomqvist
2018-09-19 16:24 ` Andrew Stubbs
2018-09-19 21:18 ` Damian Rouson
2018-09-19 22:30 ` Andrew Stubbs
2018-09-19 23:09 ` Damian Rouson [this message]
2018-09-20 20:02 ` Thomas Koenig
2018-09-20 20:56 ` Damian Rouson
2018-09-21 7:33 ` Toon Moene
2018-09-23 11:40 ` Janne Blomqvist
2018-09-21 16:25 ` OpenCoarrays integration with gfortran Jerry DeLisle
2018-09-21 19:13 ` Janne Blomqvist
2018-09-21 19:37 ` Richard Biener
2018-09-21 20:17 ` Damian Rouson
2018-09-21 23:23 ` Jerry DeLisle
2018-09-23 9:47 ` Toon Moene
2018-09-23 16:48 ` Bernhard Reutner-Fischer
2018-09-23 19:17 ` Toon Moene
2018-09-23 20:19 ` Bernhard Reutner-Fischer
2018-09-24 10:58 ` Alastair McKinstry
2018-09-27 12:29 ` Richard Biener
2018-09-27 13:32 ` Jorge D'Elia
2018-09-20 15:56 ` [PATCH 08/25] Fix co-array allocation Janne Blomqvist
2018-09-20 16:23 ` Andrew Stubbs
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='CACR8rveFtft+Sco3s0xz=Lr6Wfshjz-BbEb-ozbjH+2AfMApkA@mail.gmail.com' \
--to=damian@sourceryinstitute.org \
--cc=ams@codesourcery.com \
--cc=blomqvist.janne@gmail.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=toon@moene.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).