public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeff Hammond <jeff.science@gmail.com>
To: sgk@troutmask.apl.washington.edu
Cc: Damian Rouson <damian@sourceryinstitute.org>,
	gfortran <fortran@gcc.gnu.org>
Subject: Re: Bug 84894 - [F2018] provide iso_fortran_binding.h
Date: Fri, 16 Mar 2018 02:46:00 -0000	[thread overview]
Message-ID: <03A3D0A2-CB95-431C-B256-65E01F5B39C0@gmail.com> (raw)
In-Reply-To: <20180316020757.GA65948@troutmask.apl.washington.edu>



> 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’s in TS29113. Look at https://gcc.gnu.org/onlinedocs/gfortran/Further-Interoperability-of-Fortran-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=ll&objId=19442438&objAction=Open&viewType=1.
>> 
> 
> 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

  reply	other threads:[~2018-03-16  2:46 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-15 23:46 Damian Rouson
2018-03-16  0:25 ` Steve Kargl
2018-03-16  0:43   ` Jeff Hammond
2018-03-16  1:50     ` Damian Rouson
2018-03-16  2:08       ` Steve Kargl
2018-03-16  2:46         ` Jeff Hammond [this message]
2018-03-16  2:54           ` Jeff Hammond
2018-03-16  4:31           ` Steve Kargl
2018-03-16  6:01             ` Jeff Hammond
2018-03-16 10:31 Dominique d'Humières
2018-03-19 23:05 ` Damian Rouson
2018-03-20 15:13   ` Jeff Hammond
2018-03-20 14:14 Vladimír Fuka
2018-03-20 22:49 ` Damian Rouson

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=03A3D0A2-CB95-431C-B256-65E01F5B39C0@gmail.com \
    --to=jeff.science@gmail.com \
    --cc=damian@sourceryinstitute.org \
    --cc=fortran@gcc.gnu.org \
    --cc=sgk@troutmask.apl.washington.edu \
    /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).