Don't encourage our users to write new fortran code ;)
-Nathan Hjelm
HPC-5, LANL
On Wed, Dec 04, 2013 at 02:28:44PM +, Jeff Squyres (jsquyres) wrote:
> FWIW, 1.7 also has the new MPI-3 "use mpi_f08" Fortran bindings, which are
> MUCH better than the old mpif.h and "use mpi" bindings.
>
>
FWIW, 1.7 also has the new MPI-3 "use mpi_f08" Fortran bindings, which are MUCH
better than the old mpif.h and "use mpi" bindings.
If they care, you should strongly encourage users to "use mpi_f08" in new
Fortran subroutines. Forward and backwards compatibility was a major design
point for
Thanks for the feedback and info. I think we can install 1.7x for those users
who don't want to deal with the warnings.
-david
--
David Gunter
HPC-3 PTools Team
On Dec 3, 2013, at 3:38 PM, Jeff Squyres (jsquyres)
> wrote:
You might want to
You might want to double check that it doesn't break ABI - hypothetically,
those are equivalent (I think), but I don't know what liberties the fortran
compiler and linker is allowed to take with those different forms.
On Dec 3, 2013, at 5:37 PM, Nathan Hjelm wrote:
> For
For general use we deploy only the super stable release. We do have 1.7.x in
friendly-testing on some machines.
David, I don't think that change will break ABI so it might be worth patching
before deploying. No further 1.6.x releases are planned.
-Nathan
On Tue, Dec 03, 2013 at 10:27:43PM
David --
Any possibility of upgrading to the v1.7 series?
On Nov 22, 2013, at 10:46 AM, "Barrett, Brian W" wrote:
> David (Gunter) -
>
> Which version of Open MPI are you using? It looks like the 1.7 series
> does not declare the internal version (GREEK / SVN) in the
David (Gunter) -
Which version of Open MPI are you using? It looks like the 1.7 series
does not declare the internal version (GREEK / SVN) in the Fortran
headers, so this shouldn't be a problem going forward.
Brian
On 11/22/13 8:39 AM, "Dave Goodell (dgoodell)" wrote: