public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: Steve Kargl <sgk@troutmask.apl.washington.edu>
To: Damian Rouson <damian@sourceryinstitute.org>
Cc: gfortran <fortran@gcc.gnu.org>, Jeff Hammond <jeff.science@gmail.com>
Subject: Re: Bug 84894 - [F2018] provide iso_fortran_binding.h
Date: Fri, 16 Mar 2018 00:25:00 -0000	[thread overview]
Message-ID: <20180316002458.GA74834@troutmask.apl.washington.edu> (raw)
In-Reply-To: <etPan.5aab05b7.4db64bb6.17fc@sourceryinstitute.org>

On Thu, Mar 15, 2018 at 04:45:59PM -0700, Damian Rouson wrote:

> 
> This bug is being submitted to track progress and interest in this
> feature and to preserve a link to the above file as a potential
> starting point. The lack of iso_fortran_bindin.h currently blocks
> MPICH 3.2 from providing gfortran users the mpi_f08 module that
> the MPI 3.1 standard requires.
> 

MPI 3.1 uses a header file that isn't in the Fortran
2008 Standard?  Seems like MPICH 3.2 will need to
generate the header file for each compiler that it
supports.  

-- 
Steve

  reply	other threads:[~2018-03-16  0:25 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 [this message]
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
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=20180316002458.GA74834@troutmask.apl.washington.edu \
    --to=sgk@troutmask.apl.washington.edu \
    --cc=damian@sourceryinstitute.org \
    --cc=fortran@gcc.gnu.org \
    --cc=jeff.science@gmail.com \
    /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).