On Sun, Apr 8, 2018 at 8:56 PM, Damian Rouson
wrote:
> On April 4, 2018 at 1:12:25 AM, Richard Biener
> (richard.guent...@gmail.com(mailto:richard.guent...@gmail.com)) wrote:
>
>> In that case user programs compiled with -fcoarray=lib are but gfortran
>> or libgfortran itself is not linked agains
On April 4, 2018 at 1:12:25 AM, Richard Biener
(richard.guent...@gmail.com(mailto:richard.guent...@gmail.com)) wrote:
> In that case user programs compiled with -fcoarray=lib are but gfortran
> or libgfortran itself is not linked against OpenCoarrays?
Yes. OpenCoarrays produces the parallel ru
On Wed, Apr 4, 2018 at 8:24 AM, Damian Rouson
wrote:
> On April 3, 2018 at 1:36:37 AM, Richard Biener (richard.guent...@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
On April 3, 2018 at 1:36:37 AM, Richard Biener (richard.guent...@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
On Sat, Mar 31, 2018 at 2:44 AM, Damian Rouson
wrote:
> All,
>
> Jerry DeLisle, Daniel Celis Garza, and I would greatly appreciate feedback on
> our approach to patching the GCC build system to build MPICH and OpenCoarrays
> after it builds gfortran (gfortran requires MPI and
All,
Jerry DeLisle, Daniel Celis Garza, and I would greatly appreciate feedback on
our approach to patching the GCC build system to build MPICH and OpenCoarrays
after it builds gfortran (gfortran requires MPI and OpenCoarrays to support the
parallel features of Fortran 2008 and Fortran 2018
