This meter represents your reputation at a 100% scale based on your level of participation on the site.
Find out more
The MPICH folks have released an RC candidate for MPICH 3.0:
A new preview release of MPICH, 3.0rc1, is now available for download. The primary focus of this release is to provide full support for the MPI-3 standard. Other smaller features including support for ARM v7 native atomics are also included.
This meter represents your reputation at a 100% scale based on your level of participation on the site.
Find out more
In my last post, I talked about why MPI wrapper compilers are Good for you. The short version is that it is faaar easier to use a wrapper compiler than to force users to figure out what compiler and linker flags the MPI implementation needs — because sometimes they need a lot of flags.
Hence, MPI wrappers are Good for you. They can save you a lot of pain.
That being said, they can also hurt portability, as one user noted on the Open MPI user’s mailing list recently.
This meter represents your reputation at a 100% scale based on your level of participation on the site.
Find out more
An interesting thread on the Open MPI user’s mailing list came up the other day: a user wanted Open MPI’s “mpicc” wrapper compiler to accept the same command line options as MPICH’s “mpicc” wrapper. On the surface, this is a very reasonable request. After all, MPI is all about portability — so why not make the wrapper compilers be the same?
Unfortunately, this request exposes a can of worms and at least one unfortunate truth: the MPI API is portable, but other aspects of MPI are not, such as compiling/linking MPI applications, launching MPI jobs, etc.
Let’s first explore what wrapper compilers are, and why they’re good for you.