From: Damian Rouson <damian@sourceryinstitute.org>
To: Richard Biener <richard.guenther@gmail.com>
Cc: "GCC Development" <gcc@gcc.gnu.org>,
"Jerry DeLisle" <jvdelisle@charter.net>,
gfortran <fortran@gcc.gnu.org>,
"Filippone, Salvatore" <salvatore.filippone@cranfield.ac.uk>,
"Daniel Celis Garza" <daniel.celisgarza@hmc.ox.ac.uk>
Subject: Re: Patching the GCC build system to build MPICH and OpenCoarrays
Date: Wed, 04 Apr 2018 06:24:00 -0000 [thread overview]
Message-ID: <etPan.5ac46fa0.42069fb5.35eb@sourceryinstitute.org> (raw)
In-Reply-To: <CAFiYyc1QsNLJ7ecy16gL70WO-EekW2WGc7x9HMmCx9LLL8VyVA@mail.gmail.com>
On April 3, 2018 at 1:36:37 AM, Richard Biener (richard.guenther@gmail.com) wrote:
You probably only want a new target_module for the MPI library. Note
it's name has to match that of the directory containing the sources
which
as far as I see is 'mpich', not 'libmpi'.
Thanks! I’ll ask Daniel to respond if he has further questions.
May I ask again why mpi/opencoarrays should be built together with
gfortran rather than separately? Does gfortran or any of its current
target libraries
link against them?
Yes, gfortran links to OpenCoarrays via the -fcoarray=lib argument. OpenCoarrays provides the only parallel implementations of gfortran’s Coarray ABI (http://bit.ly/Coarray-ABI). Any Fortran program that uses the large set of parallel features in Fortran 2008 and Fortran 2018 must have OpenCoarrays installed in order for the code to execute in parallel.
We have found MPICH to be the most robust option and it has the only released support for some of the more advanced requirements such as the Fortran 2018 fault-tolerance features. However, there will be configure options for using MPI implementations other than MPICH.
Damian
next prev parent reply other threads:[~2018-04-04 6:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-31 0:44 Damian Rouson
2018-04-03 11:36 ` Richard Biener
2018-04-04 6:24 ` Damian Rouson [this message]
2018-04-04 11:12 ` Richard Biener
2018-04-08 18:56 ` Damian Rouson
2018-04-09 11:43 ` Richard Biener
2018-04-04 13:09 ` Toon Moene
2018-04-04 18:05 ` 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=etPan.5ac46fa0.42069fb5.35eb@sourceryinstitute.org \
--to=damian@sourceryinstitute.org \
--cc=daniel.celisgarza@hmc.ox.ac.uk \
--cc=fortran@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=jvdelisle@charter.net \
--cc=richard.guenther@gmail.com \
--cc=salvatore.filippone@cranfield.ac.uk \
/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).