Don't encourage our users to write new fortran code ;) -Nathan Hjelm HPC-5, LANL
On Wed, Dec 04, 2013 at 02:28:44PM +0000, 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. > > 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 the mpi_f08 bindings; users can fully mix mpif.h, use mpi, and use > mpi_f08 in the same Fortran application. For example, they can just use > mpi_f08 when writing new code in their existing applications (where the rest > of the old/legacy code still uses mpif.h and/or use mpi), etc. > > > > On Dec 4, 2013, at 9:21 AM, "Gunter, David O" <d...@lanl.gov> wrote: > > > 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) <jsquy...@cisco.com> > > wrote: > > > >> 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 <hje...@lanl.gov> wrote: > >> > >>> 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 +0000, Jeff Squyres (jsquyres) wrote: > >>>> David -- > >>>> > >>>> Any possibility of upgrading to the v1.7 series? > >>>> > >>>> > >>>> On Nov 22, 2013, at 10:46 AM, "Barrett, Brian W" <bwba...@sandia.gov> > >>>> 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 Fortran > >>>>> headers, so this shouldn't be a problem going forward. > >>>>> > >>>>> Brian > >>>>> > >>>>> On 11/22/13 8:39 AM, "Dave Goodell (dgoodell)" <dgood...@cisco.com> > >>>>> wrote: > >>>>> > >>>>>> Jeff Squyres is usually our Fortran expert for this sort of issue, but > >>>>>> he's on vacation until after the Thanksgiving holiday in the US. So > >>>>>> please expect a modest delay in (properly) responding to your question. > >>>>>> > >>>>>> -Dave > >>>>>> > >>>>>> On Nov 21, 2013, at 9:37 AM, "Gunter, David O" <d...@lanl.gov> wrote: > >>>>>> > >>>>>>> We have a user complaining about warnings he is getting from his > >>>>>>> Fortran 95 code. > >>>>>>> > >>>>>>> The Intel compilers throw out this warning: > >>>>>>> > >>>>>>> warning #7346: The CHARACTER* form of a CHARACTER declaration is an > >>>>>>> obsolescent feature in Fortran 95. > >>>>>>> > >>>>>>> The warning stems from the following two lines in <mpi > >>>>>>> dir>/include/mpif-config.h: > >>>>>>> > >>>>>>> character*32 OMPI_GREEK_VERSION > >>>>>>> character*32 OMPI_SVN_VERSION > >>>>>>> > >>>>>>> Can we simply change those lines to the following: > >>>>>>> > >>>>>>> character(len=32) OMPI_GREEK_VERSION > >>>>>>> character(len=32) OMPI_SVN_VERSION > >>>>>>> > >>>>>>> What would break if that happened? > >>>>>>> > >>>>>>> Thanks, > >>>>>>> david > >>>>>>> -- > >>>>>>> David Gunter > >>>>>>> HPC-3 > >>>>>>> Los Alamos National Laboratory > >>>>>>> > >>>>>>> > >>>>>>> > >>>>>>> > >>>>>>> _______________________________________________ > >>>>>>> devel mailing list > >>>>>>> de...@open-mpi.org > >>>>>>> http://www.open-mpi.org/mailman/listinfo.cgi/devel > >>>>>> > >>>>>> _______________________________________________ > >>>>>> devel mailing list > >>>>>> de...@open-mpi.org > >>>>>> http://www.open-mpi.org/mailman/listinfo.cgi/devel > >>>>>> > >>>>> > >>>>> > >>>>> -- > >>>>> Brian W. Barrett > >>>>> Scalable System Software Group > >>>>> Sandia National Laboratories > >>>>> > >>>>> > >>>>> > >>>>> _______________________________________________ > >>>>> devel mailing list > >>>>> de...@open-mpi.org > >>>>> http://www.open-mpi.org/mailman/listinfo.cgi/devel > >>>> > >>>> > >>>> -- > >>>> Jeff Squyres > >>>> jsquy...@cisco.com > >>>> For corporate legal information go to: > >>>> http://www.cisco.com/web/about/doing_business/legal/cri/ > >>>> > >>>> _______________________________________________ > >>>> devel mailing list > >>>> de...@open-mpi.org > >>>> http://www.open-mpi.org/mailman/listinfo.cgi/devel > >>> _______________________________________________ > >>> devel mailing list > >>> de...@open-mpi.org > >>> http://www.open-mpi.org/mailman/listinfo.cgi/devel > >> > >> > >> -- > >> Jeff Squyres > >> jsquy...@cisco.com > >> For corporate legal information go to: > >> http://www.cisco.com/web/about/doing_business/legal/cri/ > >> > >> _______________________________________________ > >> devel mailing list > >> de...@open-mpi.org > >> http://www.open-mpi.org/mailman/listinfo.cgi/devel > > > > _______________________________________________ > > devel mailing list > > de...@open-mpi.org > > http://www.open-mpi.org/mailman/listinfo.cgi/devel > > > -- > Jeff Squyres > jsquy...@cisco.com > For corporate legal information go to: > http://www.cisco.com/web/about/doing_business/legal/cri/ > > _______________________________________________ > devel mailing list > de...@open-mpi.org > http://www.open-mpi.org/mailman/listinfo.cgi/devel
pgpwo2XEbPl6l.pgp
Description: PGP signature
