public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: Steve Kargl <sgk@troutmask.apl.washington.edu>
To: Jeff Hammond <jeff.science@gmail.com>
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 04:31:00 -0000	[thread overview]
Message-ID: <20180316043126.GA82134@troutmask.apl.washington.edu> (raw)
In-Reply-To: <03A3D0A2-CB95-431C-B256-65E01F5B39C0@gmail.com>

On Thu, Mar 15, 2018 at 07:45:24PM -0700, Jeff Hammond wrote:
> 
> 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?

I don't speak for gfortran/gcc development or developers.

I am not preventing a feature.  Anyone, including you, are
more than welcomed to submit a patch.  iso_fortran_binding.h
won't be in gcc 8.1 as it is too late in the development 
cycle.  I also predict, that unless Anyone, including you,
step up to plate that this header won't appear for a very
long time in gfortran.  It's quite simple.  Too many bugs
and features to implement, too few developers.

I simply find it odd that MPI 3.1 implemented a module
named mpi_f08 that uses features not included in the
F2008 Standard.

I fix bugs in gfortran as a hobby.  29 bugs since the
beginning of the year.  The oldest was 10 years old.  The
newest bug was 9 days old.  I've reviewed a number of
patches from other contributors as they have reviewed
my patches.

As to filibustering, I have no intension of implementing
iso_fortran_binding.h.   If Anyone, including you or
someone associated with OpenCoarray, implements 
iso_fortran_binding.h before close of stage 4 for gcc 
8.1, I will review the patch and help shepard it into
the tree.

The ball is in your court.

-- 
Steve

  parent reply	other threads:[~2018-03-16  4:31 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
2018-03-16  2:54           ` Jeff Hammond
2018-03-16  4:31           ` Steve Kargl [this message]
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=20180316043126.GA82134@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).