From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-patches-return-486005-listarch-gcc-patches=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 116230 invoked by alias); 19 Sep 2018 23:09:04 -0000
Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-patches.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-patches/>
List-Post: <mailto:gcc-patches@gcc.gnu.org>
List-Help: <mailto:gcc-patches-help@gcc.gnu.org>
Sender: gcc-patches-owner@gcc.gnu.org
Received: (qmail 116195 invoked by uid 89); 19 Sep 2018 23:09:02 -0000
Authentication-Results: sourceware.org; auth=none
X-Spam-SWARE-Status: No, score=-2.1 required=5.0 tests=AWL,BAYES_00,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 spammy=H*c:alternative, images
X-HELO: mail-wr1-f47.google.com
Received: from mail-wr1-f47.google.com (HELO mail-wr1-f47.google.com) (209.85.221.47) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 19 Sep 2018 23:09:01 +0000
Received: by mail-wr1-f47.google.com with SMTP id v17-v6so7420949wrr.9        for <gcc-patches@gcc.gnu.org>; Wed, 19 Sep 2018 16:09:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;        d=sourceryinstitute.org; s=google;        h=mime-version:references:in-reply-to:from:date:message-id:subject:to         :cc;        bh=jB4+Zsr82dpu2nAIP1v8XWogeWeXMr453niZlWPA4fs=;        b=kvNgY5gK7BWHhVBdf5wOH48143fQB59Bk3kbUXRTCqTgUUrwRYPROmlrW8fs5RpTKX         MPBVMGskN4lICLCOXIbdrk4gdcy3LgQ9oVliYS7qWIY5QapNjkGidy/NKUMyhTt6Kv49         H+s5N54TzCQe3bP65u3LtavDJBz1lp9pPzE7fqzhyhPtaItsIaQxZGH+JTiw+RgyTqpK         jt1OOEKjXABhvS3CW/zydQczEdAVOY68MybQYZPoWwDClgd0a9fehI3Ayk2qG2IodTdK         /6Np31K2wM0jwCrb1WNOpujmDXwaowvpsQuBSOThFlH0Xqjil7CECGV0am8kWVAoOqah         bnDQ==
MIME-Version: 1.0
References: <024e798b9539b765a1259cfc9cb2f1dc480b24ca.1536144068.git.ams@codesourcery.com> <7f5064c3-afc6-b7b5-cade-f03af5b86331@moene.org> <CAO9iq9HSBfLANeKKUD=8byyNoujnWG2+Q7wGGWwXf3jmiS5ddA@mail.gmail.com> <9290b55e-b12a-838a-5943-0c72d040dc3f@codesourcery.com> <CACR8rve1hkPdFOUid1qYxv7nuuh1RVRwPpXbrB_TjuMMCZJpWQ@mail.gmail.com> <b79ef46e-563c-f1c8-4f48-c65c5b6ad0da@codesourcery.com>
In-Reply-To: <b79ef46e-563c-f1c8-4f48-c65c5b6ad0da@codesourcery.com>
From: Damian Rouson <damian@sourceryinstitute.org>
Date: Thu, 20 Sep 2018 01:21:00 -0000
Message-ID: <CACR8rveFtft+Sco3s0xz=Lr6Wfshjz-BbEb-ozbjH+2AfMApkA@mail.gmail.com>
Subject: Re: [PATCH 08/25] Fix co-array allocation
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>
Content-Type: text/plain; charset="UTF-8"
X-SW-Source: 2018-09/txt/msg01108.txt.bz2

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