This is the mail archive of the
mailing list for the GCC project.
Re: Patching the GCC build system to build MPICH and OpenCoarrays
- From: Damian Rouson <damian at sourceryinstitute dot org>
- To: Richard Biener <richard dot guenther at gmail dot com>
- Cc: GCC Development <gcc at gcc dot gnu dot org>, Jerry DeLisle <jvdelisle at charter dot net>, gfortran <fortran at gcc dot gnu dot org>, Filippone, Salvatore <salvatore dot filippone at cranfield dot ac dot uk>, Daniel Celis Garza <daniel dot celisgarza at hmc dot ox dot ac dot uk>
- Date: Tue, 3 Apr 2018 20:24:32 -1000
- Subject: Re: Patching the GCC build system to build MPICH and OpenCoarrays
- References: <etPan.firstname.lastname@example.org> <CAFiYyc1QsNLJ7ecy16gL70WO-EekW2WGc7x9HMmCx9LLL8VyVA@mail.gmail.com>
On April 3, 2018 at 1:36:37 AM, Richard Biener (email@example.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
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
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.