Gerald, (or who does this)
Since shared memory parallel programming with Fortran is now a Standard feature
of the language, we would like to support full parallelism through the use of
mpich and OpenCorrays.
We choose mpich as a default only because it is very stable. We choose
OpenCoarrays becau
> We choose mpich as a default only because it is very stable.
Why are why tying ourselves to one MPI implementation?
FX
Hi FX,
we don't really do. You can use other MPI implementation as well, albeit not all
features are implemented in all the others. For failed images support we needed
the fault tolerance support for MPI, which I see only in mpich from 3.2 on. The
other MPI implementations publicy available do not
Resending as plain text (although now I realize my reply is at least partially
redundant since reading Andre’s email):
On April 4, 2017 at 10:44:09 AM, FX
(fxcoud...@gmail.com(mailto:fxcoud...@gmail.com)) wrote:
> > We choose mpich as a default only because it is very stable.
>
> Why are wh
On April 4, 2017 at 9:48:23 AM, Jerry DeLisle
(jvdeli...@charter.net(mailto:jvdeli...@charter.net)) wrote:
> Gerald, (or who does this)
>
> Since shared memory parallel programming with Fortran is now a Standard
> feature
> of the language, we would like to support full parallelism th
On 04/04/2017 10:44 AM, FX wrote:
>> We choose mpich as a default only because it is very stable.
>
> Why are why tying ourselves to one MPI implementation?
>
> FX
>
Not tying ourselves at all. This just gives users who install gcc manually with
the ./configure process a default to use and only
Snapshot gcc-5-20170404 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/5-20170404/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 5 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/branches/gcc-5
