From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 49963 invoked by alias); 16 Mar 2018 02:54:41 -0000 Mailing-List: contact fortran-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: fortran-owner@gcc.gnu.org Received: (qmail 49897 invoked by uid 89); 16 Mar 2018 02:54:36 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.6 required=5.0 tests=BAYES_00,FREEMAIL_FROM,HTML_MESSAGE,HTML_OBFUSCATE_05_10,KAM_SHORT,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 spammy=H*c:alternative, international, International, wishes X-HELO: mail-pg0-f41.google.com Received: from mail-pg0-f41.google.com (HELO mail-pg0-f41.google.com) (74.125.83.41) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 16 Mar 2018 02:54:34 +0000 Received: by mail-pg0-f41.google.com with SMTP id e9so3558818pgs.10 for ; Thu, 15 Mar 2018 19:54:34 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=moVkFL21kuJAmHNoGNKy+r36s77CjtVKBjGdcRlKBt0=; b=gsfRZiY/pIoL2aDpxZ3hMxUJCl/mCqlPEfTK2HNLhpAQI64Kwl8URV+/tvIK07nqpb xRi7bD8ZNOrBNi+NH7qzQZjRCxIeYj4y3P5dhGxGBZissfXEUjgX/fphZ6jLFcMmqmTF tFN8X79EA31m8zwiu3djWzLyJVzEIRq36s3FOgk+aH3IeG3oZcV3oLbTOaom65l6juVp sXDfHch/9fDvUA2wYMIkXGIZfOcpKAQISPcuwOq60bpcjFhdBRtQDwDv0+SMqAD3jwul 0jFz3DD9w3TAX3CVesnOGCG5XrUYt0D3aL4ydiRU+ZDtNzaORJiW3kHC/BSfAXDWhoDs btdA== X-Gm-Message-State: AElRT7HNlJKCX5L1tIBorZ/E5EzEXMIAjPLRHnhABmHmEx5GHMGT0rkg gAm5HDDzTT3wgLO/A5qcqO3QjO6V0T8yTcNzeus= X-Google-Smtp-Source: AG47ELtbdWwDt26qlWT6mp0ZEf+tgzU7CUnmsM2GbxE5EU0oq5QyoWLestIKWxRckMSvA6J6k5cFWjtoKkfuw6T9Ahg= X-Received: by 10.98.3.66 with SMTP id 63mr157818pfd.177.1521168872569; Thu, 15 Mar 2018 19:54:32 -0700 (PDT) MIME-Version: 1.0 References: <20180316002458.GA74834@troutmask.apl.washington.edu> <48A5C921-55D7-4EC8-8DC2-9006D4FBD4B6@gmail.com> <20180316020757.GA65948@troutmask.apl.washington.edu> <03A3D0A2-CB95-431C-B256-65E01F5B39C0@gmail.com> In-Reply-To: <03A3D0A2-CB95-431C-B256-65E01F5B39C0@gmail.com> From: Jeff Hammond Date: Fri, 16 Mar 2018 02:54:00 -0000 Message-ID: Subject: Re: Bug 84894 - [F2018] provide iso_fortran_binding.h To: sgk@troutmask.apl.washington.edu Cc: Damian Rouson , gfortran Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-SW-Source: 2018-03/txt/msg00080.txt.bz2 Sorry, I meant J3 not J5 but in any case, http://mpi-forum.org/docs/mpi-3.1/mpi31-report/node409.htm contains this: =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D *Rationale.* The features in TS 29113 on further interoperability with C were decided on by ISO/IEC JTC1/SC22/WG5 and designed by PL22.3 (formerly J3) to support a higher level of integration between Fortran-specific features and C than was provided in the Fortran 2008 standard; part of this design is based on requirements from the MPI Forum to support MPI-3.0. According to [41 ], ``an ISO/IEC TS is reviewed after three years in order to decide whether it will be confirmed for a further three years, revised to become an International Standard, or withdrawn. If the ISO/IEC TS is confirmed, it is reviewed again after a further three years, at which time it must either be transformed into an International Standard or be withdrawn.'' The TS 29113 contains the following language features that are needed for the MPI bindings in the mpi_f08 module: assumed-type and assumed-rank. It is important that any possible actual argument can be used for such dummy arguments, e.g., scalars, arrays, assumed-shape arrays, assumed-size arrays, allocatable arrays, and with any element type, e.g., REAL, CHARACTER*5, CHARACTER*(*), sequence derived types, or BIND(C) derived types. Especially for backward compatibility reasons, it is important that any possible actual argument in an implicit interface implementation of a choice buffer dummy argument (e.g., with mpif.h without argument-checking) can be used in an implementation with assumed-type and assumed-rank argument in an explicit interface (e.g., with the mpi_f08 module). A further feature useful for MPI is the extension of the semantics of the ASYNCHRONOUSattribute: In F2003 and F2008, this attribute could be used only to protect buffers of Fortran asynchronous I/O. With TS 29113, this attribute now also covers asynchronous communication occurring within library routines written in C. The MPI Forum hereby wishes to acknowledge this important effort by the Fortran PL22.3 and WG5 committee. (* End of rationale.*) =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D When we voted this into MPI-3, we thought it was going to appear in Fortran much sooner. In any case, all of the Fortran compiler implementors that attend the MPI Forum supported this. IBM, Intel, and Cray implemented it rather quickly. Jeff On Thu, Mar 15, 2018 at 7:45 PM Jeff Hammond wrote: > > > > On Mar 15, 2018, at 7:07 PM, Steve Kargl < > sgk@troutmask.apl.washington.edu> wrote: > > > >> On Thu, Mar 15, 2018 at 06:50:11PM -0700, Damian Rouson wrote: > >> > >>> On March 15, 2018 at 5:43:03 PM, Jeff Hammond (jeff.science@gmail.com > (mailto:jeff.science@gmail.com)) wrote: > >>> > >>> It=E2=80=99s in TS29113. Look at > https://gcc.gnu.org/onlinedocs/gfortran/Further-Interoperability-of-Fortr= an-with-C.html > for details. > >>> > >> > >> And the features described in TS29113 have been incorporated into the > Fortran 2018 Draft International Standard available at > http://isotc.iso.org/livelink/livelink?func=3Dll&objId=3D19442438&objActi= on=3DOpen&viewType=3D1 > . > >> > > > > The module name is mpi_f08 not mpi_f08_ts29113 or mpi_f18. > > Seems strange to name a module with a moniker that identifies > > a specific standard, which does not include the required > > information. > > Please talk to one of the J5 members who was part of both MPI-3 and > TS29113 efforts if you want the history. > > Is it your intent to filibuster this feature and prevent gfortran from > supporting MPI-3 or do you want to have a constructive conversation where > we talk about things that benefit users? > > Jeff --=20 Jeff Hammond jeff.science@gmail.com http://jeffhammond.github.io/