public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: Thomas Koenig <tkoenig@netcologne.de>
To: Benson Muite <benson_muite@emailplus.org>,
	Andre Vehreschild <vehre@gmx.de>, Jerry D <jvdelisle2@gmail.com>
Cc: Mikael Morin <morin-mikael@orange.fr>,
	Paul Richard Thomas <paul.richard.thomas@gmail.com>,
	GCC-Fortran-ML <fortran@gcc.gnu.org>,
	Lexi Pimenidis <lexi@badgersystems.de>
Subject: Re: Possible funding of gfortran work
Date: Wed, 31 May 2023 08:08:49 +0200	[thread overview]
Message-ID: <2f95809c-8f0b-7d75-ca62-aeee11c6bee0@netcologne.de> (raw)
In-Reply-To: <5bde7c1f-3524-7f2e-fd48-a4b97734e2b9@emailplus.org>

On 31.05.23 05:46, Benson Muite wrote:
 > On 5/30/23 23:08, Thomas Koenig via Fortran wrote:


 >>> * Complete language intrinsic parallel programming paradigm coarrays.
 >>> This
 >>>     includes completing native coarray support (thread based). As 
well as
 >>>     refactoring of the library based  coarray approach to support
 >>> coarrays in
 >>>     modules. I.e. research on how to support the use of coarrays in
 >>> modules that
 >>>     are not aware of coarrays (not compiled with its support enabled).
 >>
 > Is distributed memory support for co-arrays of interest as well? There
 > is a lot of code that uses MPI (for which there is some push for using
 > more modern Fortran features), and there are also other libraries such
 > as GASPI.

We already support OpenCoarrays via -fcoarray=lib, which is MPI-based
(or at least can use MPI).  I guess that OpenCoarrays could be modified
to use GASPI, but this would likely be a separate (if related) project.

We would have to check about license requirements, though - I'm not sure
if the implementation of GASPI is free enough for the Soverereign Tech
Fund (at least Wikipedia claims it's "pay for commercial users",
which would be consistent with the business model of the Fraunhofer
Institutes.)


 >> (There is Intel, which is dog-slow, and there is NAG, which costs
 >> money).
 > Is this also expected in Flang? See:
 > 
https://crd.lbl.gov/divisions/amcr/computer-science-amcr/class/research/caffeine/
 > 
https://crd.lbl.gov/divisions/amcr/computer-science-amcr/class/research/caffeine/
 > Probably good to make a case for two open source compilers.

We're concerned with gfortran here.  A lot of work and money has gone
into flang that I sometimes think would have been better spent on
gfortran, then we would be in a better position overall today.

But I am hoping that this initiative can cure at least part of that.

 >> Fortran remains one of the premier language for science, especially for
 >> high-performance computing and fields like quantum chemistry or
 >> computational fluid dynamics.
 >>
 >> gfortran is the default Fortran compiler on Linux systems, and lack of
 >> features and bugs in in gfortran hinder adoption of more modern, safer
 >> and more efficient language features. The project has been almost
 >> entirely volunteer-driven so far, but is currently suffering from
 >> a lack of active developers.  Funding will motivate experienced
 >> gfortran developers who have reduced their contributions to return
 >> to the project and advance it substantially.
 >>
 >>
 > Any possibilities for new contributors to participate?

We should avoid bringing people in who spend all the money just
familiarizing themselves with the compiler, producing no useful
output in the end.

I think that contributors should have demonstrated that they are
capable of working productively with gfortran, and the best way
to demonstrate that is to already have a track record of accepted
patches (preferably gfortran, but also gcc in general). That does not
mean that this track record needs to be years or decades old, but it
should exist.

Also, people recommended by a current contributor should be able
to participate; but we should probably discuss people who apply
on a case-by-case basis.

(The above is my personal opinion, please discuss if anybody has
a different opinion).

Best regards

	Thomas

  reply	other threads:[~2023-05-31  6:08 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-26  4:34 Jerry DeLisle
2023-05-26 17:09 ` Bernhard Reutner-Fischer
2023-05-26 21:22 ` Jerry D
2023-05-27  8:08   ` Thomas Koenig
2023-05-27 11:24     ` Andre Vehreschild
2023-05-27 16:19       ` Paul Richard Thomas
2023-05-28 14:26         ` Nicolas König
2023-05-28 15:07         ` Thomas Koenig
2023-05-28 19:25         ` Mikael Morin
2023-05-28 20:53           ` Jerry D
2023-05-30 13:32             ` Andre Vehreschild
2023-05-30 20:08               ` Thomas Koenig
2023-05-31  3:46                 ` Benson Muite
2023-05-31  6:08                   ` Thomas Koenig [this message]
2023-05-31  8:42                     ` Benson Muite
2023-05-31 12:23                     ` Andre Vehreschild
2023-05-31 14:08                       ` Damian Rouson
2023-06-01  9:18                         ` Andre Vehreschild
2023-06-01 10:56                           ` Bernhard Reutner-Fischer
2023-06-01 10:59                           ` Mikael Morin
2023-06-04  8:23                             ` Thomas Koenig
2023-06-05  8:08                             ` Andre Vehreschild
2023-06-05 11:44                               ` Mikael Morin
2023-06-06 13:06                                 ` Andre Vehreschild
2023-06-08 12:38                                   ` Mikael Morin
2023-06-14  8:28                                     ` Andre Vehreschild
2023-06-14  9:40                                       ` Mikael Morin
2023-06-14 18:48                                         ` Bernhard Reutner-Fischer
2023-06-01 11:12                           ` Benson Muite
2023-06-04  7:49                             ` Thomas Koenig
2023-06-05 10:12                               ` Andre Vehreschild
2023-06-05 10:07                             ` Andre Vehreschild
2023-06-05 12:16                               ` Thomas Koenig
2023-06-05 12:21                                 ` Andre Vehreschild
2023-06-08  5:34                               ` Benson Muite
2023-06-14  8:00                                 ` Andre Vehreschild
2023-06-02  0:53                           ` Jerry D
2023-06-05 10:09                             ` Andre Vehreschild

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=2f95809c-8f0b-7d75-ca62-aeee11c6bee0@netcologne.de \
    --to=tkoenig@netcologne.de \
    --cc=benson_muite@emailplus.org \
    --cc=fortran@gcc.gnu.org \
    --cc=jvdelisle2@gmail.com \
    --cc=lexi@badgersystems.de \
    --cc=morin-mikael@orange.fr \
    --cc=paul.richard.thomas@gmail.com \
    --cc=vehre@gmx.de \
    /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).