June 2015 - mpiwg-fortran - mailman3.cels.anl.gov

Re: [MPIWG Fortran] Question about named constants
by Craig Rasmusen 30 Jun '15

30 Jun '15

I looked at the Open MPI implementation and it looks like in Fortran we made them pointers to memory initialized in C so that MPI_INTEGER would have the same value across languages. MPI_INTEGER is definitely not a Fortran parameter in the Open MPI implementation, -craig On Fri, Jun 19, 2015 at 5:45 AM, William Gropp <wgropp(a)illinois.edu> wrote: > Given the intent of the wording with respect to C, I don’t think the test > is valid (in C, the clear intent was that handles could be pointers > resolved only at link time). > > Bill > > On Jun 18, 2015, at 10:19 PM, Bill Long <longb(a)cray.com> wrote: > > > > > On Jun 18, 2015, at 5:52 PM, Junchao Zhang <jczhang(a)mcs.anl.gov> wrote: > > > >> In OpenMPI F08, those predefined MPI datatypes are not "parameter > variables". Thus OMPI failed to compile an MPICH F08 test, which has > >> > >> INTEGER, PARAMETER :: nb=2 > >> TYPE(MPI_DATATYPE) :: types(nb)=(/MPI_DOUBLE_PRECISION, MPI_CHAR/) > >> > >> Jeff Squyres and I discussed in emails. I don't know whether this is > correct according to the MPI spec. > > > > Given the wording in the spec, I’m not sure either. BTW, there is no > such thing as a “parameter variable”. Something with the parameter > attribute is a constant, and hence not a variable. It is true that an > initialization expression in a type declaration is required to be a > constant expression. If OMPI is declaring these datatypes as variables > instead of constants, then there would be a problem compiling the above > code using their module. > > > > Cheers, > > Bill > > > > > > > >> > >> > >> > >> --Junchao Zhang > >> > >> On Thu, Jun 18, 2015 at 12:48 PM, Bill Long <longb(a)cray.com> wrote: > >> > >> On Jun 18, 2015, at 11:05 AM, Junchao Zhang <jczhang(a)mcs.anl.gov> > wrote: > >> > >>> Hello, Fortran experts, > >>> I am a little puzzled by MPI-3.1 Chapter 2.5.4, > >> > >> Not surprising. The (mis)use of terminology is confusing at best. > >> > >>> > >>> All named constants, with the exceptions noted below for Fortran, can > be used in > >>> initialization expressions or assignments, but not necessarily in > array declarations or as > >>> labels in C switch or Fortran select/case statements. This implies > named constants > >>> to be link-time but not necessarily compile-time constants. > >> > >> In Fortran “named constant” is a defined term. They are declared with > the PARAMETER attribute. And can be used in most places where literal > constants can be used, including array declarations. They cannot be used > as statement labels, though I think the reference to “Fortran select/case > statements” intends to talk about case-values, and not labels. Named > constants can be used as case-values. > >> > >>> > >>> Then in F08, should MPI_INTEGER be declared as a parameter variable? > >> > >> Yes. That’s what I did in my prototype mpi_f08 modules. > >> > >>> If no, then I get an error when compiling this initialization > expression with gfortran > >>> type(MPI_Datatype) :: dtype = MPI_INTEGER > >>> > >>> Error: Parameter 'mpi_integer' at (1) has not been declared or is a > variable, which does not reduce to a constant expression > >>> > >>> If yes, then of course I can use MPI_INTEGER in Fortran select/case. > >> > >> Right. > >> > >>> > >>> Another question is what is the meaning of "link-time constants". I > could not find in MPI. Does it mean I can use MPI_INTEGER after main before > MPI_Init? > >> > >> I suspect this is a historical artifact where some special head > standing was needed to correctly define MPI_INTEGER based on whether the > code was compiled with -i4 or -i8 (or equivalent, depending on the > compiler). For the modern case of using the mpi_f08 module, you just > compile the mpi_f08 module twice (once with -i4 and once with -i8) and then > have the compile command select the right actual module to reference based > on how the using program unit is compiled. Generally, values of objects > are not set at link time; addresses of objects are set at link time. MPI > objects that represent addresses (MPI_BOTTOM ??) are examples. If > MPI_INTEGER is accessible, you can reference it. If should not have > anything to do with whether MPI_Init has been called. > >> > >> Perhaps some of the MPI historians can shed more light on this > terminology. I suspect it would be completely moot if we got rid of mpif.h. > >> > >> Cheers, > >> Bill > >> > >> > >>> > >>> Thank you! > >>> > >>> --Junchao Zhang > >>> _______________________________________________ > >>> mpiwg-fortran mailing list > >>> mpiwg-fortran(a)lists.mpi-forum.org > >>> http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran > >> > >> Bill Long > longb(a)cray.com > >> Fortran Technical Support & voice: > 651-605-9024 > >> Bioinformatics Software Development fax: > 651-605-9142 > >> Cray Inc./ Cray Plaza, Suite 210/ 380 Jackson St./ St. Paul, MN 55101 > >> > >> > >> _______________________________________________ > >> mpiwg-fortran mailing list > >> mpiwg-fortran(a)lists.mpi-forum.org > >> http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran > >> > >> _______________________________________________ > >> mpiwg-fortran mailing list > >> mpiwg-fortran(a)lists.mpi-forum.org > >> http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran > > > > Bill Long > longb(a)cray.com > > Fortran Technical Support & voice: > 651-605-9024 > > Bioinformatics Software Development fax: > 651-605-9142 > > Cray Inc./ Cray Plaza, Suite 210/ 380 Jackson St./ St. Paul, MN 55101 > > > > > > _______________________________________________ > > mpiwg-fortran mailing list > > mpiwg-fortran(a)lists.mpi-forum.org > > http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran > > _______________________________________________ > mpiwg-fortran mailing list > mpiwg-fortran(a)lists.mpi-forum.org > http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran >

1 0

Re: [MPIWG Fortran] What compilers support TS 29113?
by N.M. Maclaren 25 Jun '15

25 Jun '15

On Jun 24 2015, Bill Long wrote: > > I think the "except for" is a pretty significant hole here. Yes. What it means is that it works only for arrays of intrinsic types. That accounts for the majority of uses, but not all. And it's not a reasonably thing to document as a restriction. >It is > certainly possible for a C programmer to take the TS 29113 descriptions > and write a header file and the utility functions specified there. Which doesn't help in this case, because it's not the missing functions that are the problem, but the generated code. Regards, Nick Maclaren.

1 0

Re: [MPIWG Fortran] What compilers support TS 29113?
by Hubert Ritzdorf 25 Jun '15

25 Jun '15

My intention was to implement, test and work with the new Fortran features within my NEC version of the MPI library. Therefore I was looking for compiler support. My versions of intel compilers didn't support any features of TS 29113. I don't have access to Cray compilers. NEC compilers didn't support it. At this time, gfortran 4.9.1 supports parts of TS 29113 features and was my only possibility to use Fortran subarrays without copy in/copy out at MPI 3.0 interfaces. Therefore, I used gfortran 4.9.1 and implemented a work around for the standard include file. I implemented the TS 29113 support as special C functions for Fortran, not as "simple" Fortran wrappers. I simply wanted to share my experiences with TS29113 and gfortran and highlight the problems I found. I didn't want demoralizing programmers since gfortran doesn't claim full support of TS 29113 such as Bill Gropp already explained in his mail. I didn't test it together with MPICH. Hubert ________________________________________ From: mpiwg-fortran [mpiwg-fortran-bounces(a)lists.mpi-forum.org] on behalf of Bill Long [longb(a)cray.com] Sent: Wednesday, June 24, 2015 3:16 PM To: MPI-WG Fortran working group Subject: Re: [MPIWG Fortran] What compilers support TS 29113? I think the “except for” is a pretty significant hole here. It is certainly possible for a C programmer to take the TS 29113 descriptions and write a header file and the utility functions specified there. However, there are some missing parts to having a working implementation for Fortran users. To implement the allocate / deallocate functions you need to know how the Fortran compiler allocates and deallocates memory. Not a big issue for MPI, but this one is: The Fortran compiler has to do the descriptor conversions on the caller side if the C descriptor is different from the internal Fortran one. Compiler support for the new descriptor was the big missing piece in gfortran 4.9.1. I thought the intention was to change the gfortran descriptor to match the C one, to simplify calls. If that’s not in 5.1.0, there is still a big hole. Cheers, Bill On Jun 24, 2015, at 8:02 AM, Jeff Hammond <jeff.science(a)gmail.com> wrote: > The "except for"="does not work" standard is a fantastic way to > demoralize every programmer this side of Don Knuth. Has MPICH ever > worked? > > Jeff > > On Wed, Jun 24, 2015 at 5:11 AM, William Gropp <wgropp(a)illinois.edu> wrote: >> Sounds interesting and useful. However, “except for” is the same as “does not work” when talking about standards. >> >> Bill >> >> William Gropp >> Director, Parallel Computing Institute >> Thomas M. Siebel Chair in Computer Science >> Chief Scientist, NCSA >> University of Illinois Urbana-Champaign >> >> >> >> >> >> On Jun 24, 2015, at 3:29 AM, Hubert Ritzdorf <Hubert.Ritzdorf(a)EMEA.NEC.COM> wrote: >> >>> Hi, >>> >>> I used gfortran 4.9.1 and I have build an include file which adopted the definitions of the missing >>> ISO_Fortran_binding.h to the implementation of gfortran (include file libgfortran.h) . >>> Using this I could implement the Fortran binding for TS29113. It works except for arrays of derived Fortran Types >>> which are always transferred via copy in/copy out. >>> >>> Hubert >>> ________________________________________ >>> From: mpiwg-fortran [mpiwg-fortran-bounces(a)lists.mpi-forum.org] on behalf of William Gropp [wgropp(a)illinois.edu] >>> Sent: Tuesday, June 23, 2015 9:34 PM >>> To: MPI-WG Fortran working group >>> Subject: Re: [MPIWG Fortran] What compilers support TS 29113? >>> >>> gfortran no, not even with 5.1.0 . It does have a lot of F 2008, but not even all of it, according to https://gcc.gnu.org/wiki/Fortran2008Status and https://gcc.gnu.org/wiki/TS29113Status . >>> Gfortran 5.1 fails the MPICH test because ISO_Fortran_binding.h isn’t available for GCC 5.1 (I don’t know if that’s the right test, but that’s what it does). See also https://gcc.gnu.org/onlinedocs/gfortran/Further-Interoperability-of-Fortran… . >>> >>> Bill >>> >>> William Gropp >>> Director, Parallel Computing Institute >>> Thomas M. Siebel Chair in Computer Science >>> Chief Scientist, NCSA >>> University of Illinois Urbana-Champaign >>> >>> >>> >>> >>> >>> On Jun 23, 2015, at 2:01 PM, Jeff Squyres (jsquyres) <jsquyres(a)cisco.com> wrote: >>> >>>> On Jun 23, 2015, at 11:51 AM, Bill Long <longb(a)cray.com> wrote: >>>>> >>>>> gfortran - yes (4.9 works on my Mac) >>>> >>>> I thought fortran 4.9 did not have the standardized TS 29113 dope vector...? >>>> >>>>> Cray - yes (8.3 for sure, or later). >>>> >>>> I knew about Cray, but I thought it was the only one. That may be incorrect and/or outdated information. >>>> >>>>> Not sure about others. People who build libraries (mpich, OpenMPI, ...) would know based on which ones can compiler their mpi_f08 module. >>>> >>>> Open MPI currently only has the non-TS-29113 interfaces for mpi_f08. We're looking into whether it's time to implement the TS 29113 interfaces; that's the origin of my question. :-) >>>> >>>> -- >>>> Jeff Squyres >>>> jsquyres(a)cisco.com >>>> For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/ >>>> >>>> _______________________________________________ >>>> mpiwg-fortran mailing list >>>> mpiwg-fortran(a)lists.mpi-forum.org >>>> http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran >>> >>> _______________________________________________ >>> mpiwg-fortran mailing list >>> mpiwg-fortran(a)lists.mpi-forum.org >>> http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran >>> >>> >>> Click https://www.mailcontrol.com/sr/op!XYE2yjUjGX2PQPOmvUiQSa3+T5MHvx+zSoc3i1rpp… to report this email as spam. >>> _______________________________________________ >>> mpiwg-fortran mailing list >>> mpiwg-fortran(a)lists.mpi-forum.org >>> http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran >> >> _______________________________________________ >> mpiwg-fortran mailing list >> mpiwg-fortran(a)lists.mpi-forum.org >> http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran > > > > -- > Jeff Hammond > jeff.science(a)gmail.com > http://jeffhammond.github.io/ > _______________________________________________ > mpiwg-fortran mailing list > mpiwg-fortran(a)lists.mpi-forum.org > http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran Bill Long longb(a)cray.com Fortran Technical Support & voice: 651-605-9024 Bioinformatics Software Development fax: 651-605-9142 Cray Inc./ Cray Plaza, Suite 210/ 380 Jackson St./ St. Paul, MN 55101 _______________________________________________ mpiwg-fortran mailing list mpiwg-fortran(a)lists.mpi-forum.org http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran

1 0

Re: [MPIWG Fortran] What compilers support TS 29113?
by Bill Long 24 Jun '15

24 Jun '15

I think the “except for” is a pretty significant hole here. It is certainly possible for a C programmer to take the TS 29113 descriptions and write a header file and the utility functions specified there. However, there are some missing parts to having a working implementation for Fortran users. To implement the allocate / deallocate functions you need to know how the Fortran compiler allocates and deallocates memory. Not a big issue for MPI, but this one is: The Fortran compiler has to do the descriptor conversions on the caller side if the C descriptor is different from the internal Fortran one. Compiler support for the new descriptor was the big missing piece in gfortran 4.9.1. I thought the intention was to change the gfortran descriptor to match the C one, to simplify calls. If that’s not in 5.1.0, there is still a big hole. Cheers, Bill On Jun 24, 2015, at 8:02 AM, Jeff Hammond <jeff.science(a)gmail.com> wrote: > The "except for"="does not work" standard is a fantastic way to > demoralize every programmer this side of Don Knuth. Has MPICH ever > worked? > > Jeff > > On Wed, Jun 24, 2015 at 5:11 AM, William Gropp <wgropp(a)illinois.edu> wrote: >> Sounds interesting and useful. However, “except for” is the same as “does not work” when talking about standards. >> >> Bill >> >> William Gropp >> Director, Parallel Computing Institute >> Thomas M. Siebel Chair in Computer Science >> Chief Scientist, NCSA >> University of Illinois Urbana-Champaign >> >> >> >> >> >> On Jun 24, 2015, at 3:29 AM, Hubert Ritzdorf <Hubert.Ritzdorf(a)EMEA.NEC.COM> wrote: >> >>> Hi, >>> >>> I used gfortran 4.9.1 and I have build an include file which adopted the definitions of the missing >>> ISO_Fortran_binding.h to the implementation of gfortran (include file libgfortran.h) . >>> Using this I could implement the Fortran binding for TS29113. It works except for arrays of derived Fortran Types >>> which are always transferred via copy in/copy out. >>> >>> Hubert >>> ________________________________________ >>> From: mpiwg-fortran [mpiwg-fortran-bounces(a)lists.mpi-forum.org] on behalf of William Gropp [wgropp(a)illinois.edu] >>> Sent: Tuesday, June 23, 2015 9:34 PM >>> To: MPI-WG Fortran working group >>> Subject: Re: [MPIWG Fortran] What compilers support TS 29113? >>> >>> gfortran no, not even with 5.1.0 . It does have a lot of F 2008, but not even all of it, according to https://gcc.gnu.org/wiki/Fortran2008Status and https://gcc.gnu.org/wiki/TS29113Status . >>> Gfortran 5.1 fails the MPICH test because ISO_Fortran_binding.h isn’t available for GCC 5.1 (I don’t know if that’s the right test, but that’s what it does). See also https://gcc.gnu.org/onlinedocs/gfortran/Further-Interoperability-of-Fortran… . >>> >>> Bill >>> >>> William Gropp >>> Director, Parallel Computing Institute >>> Thomas M. Siebel Chair in Computer Science >>> Chief Scientist, NCSA >>> University of Illinois Urbana-Champaign >>> >>> >>> >>> >>> >>> On Jun 23, 2015, at 2:01 PM, Jeff Squyres (jsquyres) <jsquyres(a)cisco.com> wrote: >>> >>>> On Jun 23, 2015, at 11:51 AM, Bill Long <longb(a)cray.com> wrote: >>>>> >>>>> gfortran - yes (4.9 works on my Mac) >>>> >>>> I thought fortran 4.9 did not have the standardized TS 29113 dope vector...? >>>> >>>>> Cray - yes (8.3 for sure, or later). >>>> >>>> I knew about Cray, but I thought it was the only one. That may be incorrect and/or outdated information. >>>> >>>>> Not sure about others. People who build libraries (mpich, OpenMPI, ...) would know based on which ones can compiler their mpi_f08 module. >>>> >>>> Open MPI currently only has the non-TS-29113 interfaces for mpi_f08. We're looking into whether it's time to implement the TS 29113 interfaces; that's the origin of my question. :-) >>>> >>>> -- >>>> Jeff Squyres >>>> jsquyres(a)cisco.com >>>> For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/ >>>> >>>> _______________________________________________ >>>> mpiwg-fortran mailing list >>>> mpiwg-fortran(a)lists.mpi-forum.org >>>> http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran >>> >>> _______________________________________________ >>> mpiwg-fortran mailing list >>> mpiwg-fortran(a)lists.mpi-forum.org >>> http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran >>> >>> >>> Click https://www.mailcontrol.com/sr/op!XYE2yjUjGX2PQPOmvUiQSa3+T5MHvx+zSoc3i1rpp… to report this email as spam. >>> _______________________________________________ >>> mpiwg-fortran mailing list >>> mpiwg-fortran(a)lists.mpi-forum.org >>> http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran >> >> _______________________________________________ >> mpiwg-fortran mailing list >> mpiwg-fortran(a)lists.mpi-forum.org >> http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran > > > > -- > Jeff Hammond > jeff.science(a)gmail.com > http://jeffhammond.github.io/ > _______________________________________________ > mpiwg-fortran mailing list > mpiwg-fortran(a)lists.mpi-forum.org > http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran Bill Long longb(a)cray.com Fortran Technical Support & voice: 651-605-9024 Bioinformatics Software Development fax: 651-605-9142 Cray Inc./ Cray Plaza, Suite 210/ 380 Jackson St./ St. Paul, MN 55101

1 0

Re: [MPIWG Fortran] What compilers support TS 29113?
by Jeff Hammond 24 Jun '15

24 Jun '15

The "except for"="does not work" standard is a fantastic way to demoralize every programmer this side of Don Knuth. Has MPICH ever worked? Jeff On Wed, Jun 24, 2015 at 5:11 AM, William Gropp <wgropp(a)illinois.edu> wrote: > Sounds interesting and useful. However, “except for” is the same as “does not work” when talking about standards. > > Bill > > William Gropp > Director, Parallel Computing Institute > Thomas M. Siebel Chair in Computer Science > Chief Scientist, NCSA > University of Illinois Urbana-Champaign > > > > > > On Jun 24, 2015, at 3:29 AM, Hubert Ritzdorf <Hubert.Ritzdorf(a)EMEA.NEC.COM> wrote: > >> Hi, >> >> I used gfortran 4.9.1 and I have build an include file which adopted the definitions of the missing >> ISO_Fortran_binding.h to the implementation of gfortran (include file libgfortran.h) . >> Using this I could implement the Fortran binding for TS29113. It works except for arrays of derived Fortran Types >> which are always transferred via copy in/copy out. >> >> Hubert >> ________________________________________ >> From: mpiwg-fortran [mpiwg-fortran-bounces(a)lists.mpi-forum.org] on behalf of William Gropp [wgropp(a)illinois.edu] >> Sent: Tuesday, June 23, 2015 9:34 PM >> To: MPI-WG Fortran working group >> Subject: Re: [MPIWG Fortran] What compilers support TS 29113? >> >> gfortran no, not even with 5.1.0 . It does have a lot of F 2008, but not even all of it, according to https://gcc.gnu.org/wiki/Fortran2008Status and https://gcc.gnu.org/wiki/TS29113Status . >> Gfortran 5.1 fails the MPICH test because ISO_Fortran_binding.h isn’t available for GCC 5.1 (I don’t know if that’s the right test, but that’s what it does). See also https://gcc.gnu.org/onlinedocs/gfortran/Further-Interoperability-of-Fortran… . >> >> Bill >> >> William Gropp >> Director, Parallel Computing Institute >> Thomas M. Siebel Chair in Computer Science >> Chief Scientist, NCSA >> University of Illinois Urbana-Champaign >> >> >> >> >> >> On Jun 23, 2015, at 2:01 PM, Jeff Squyres (jsquyres) <jsquyres(a)cisco.com> wrote: >> >>> On Jun 23, 2015, at 11:51 AM, Bill Long <longb(a)cray.com> wrote: >>>> >>>> gfortran - yes (4.9 works on my Mac) >>> >>> I thought fortran 4.9 did not have the standardized TS 29113 dope vector...? >>> >>>> Cray - yes (8.3 for sure, or later). >>> >>> I knew about Cray, but I thought it was the only one. That may be incorrect and/or outdated information. >>> >>>> Not sure about others. People who build libraries (mpich, OpenMPI, ...) would know based on which ones can compiler their mpi_f08 module. >>> >>> Open MPI currently only has the non-TS-29113 interfaces for mpi_f08. We're looking into whether it's time to implement the TS 29113 interfaces; that's the origin of my question. :-) >>> >>> -- >>> Jeff Squyres >>> jsquyres(a)cisco.com >>> For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/ >>> >>> _______________________________________________ >>> mpiwg-fortran mailing list >>> mpiwg-fortran(a)lists.mpi-forum.org >>> http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran >> >> _______________________________________________ >> mpiwg-fortran mailing list >> mpiwg-fortran(a)lists.mpi-forum.org >> http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran >> >> >> Click https://www.mailcontrol.com/sr/op!XYE2yjUjGX2PQPOmvUiQSa3+T5MHvx+zSoc3i1rpp… to report this email as spam. >> _______________________________________________ >> mpiwg-fortran mailing list >> mpiwg-fortran(a)lists.mpi-forum.org >> http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran > > _______________________________________________ > mpiwg-fortran mailing list > mpiwg-fortran(a)lists.mpi-forum.org > http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran -- Jeff Hammond jeff.science(a)gmail.com http://jeffhammond.github.io/

1 0

Re: [MPIWG Fortran] What compilers support TS 29113?
by William Gropp 24 Jun '15

24 Jun '15

Sounds interesting and useful. However, “except for” is the same as “does not work” when talking about standards. Bill William Gropp Director, Parallel Computing Institute Thomas M. Siebel Chair in Computer Science Chief Scientist, NCSA University of Illinois Urbana-Champaign On Jun 24, 2015, at 3:29 AM, Hubert Ritzdorf <Hubert.Ritzdorf(a)EMEA.NEC.COM> wrote: > Hi, > > I used gfortran 4.9.1 and I have build an include file which adopted the definitions of the missing > ISO_Fortran_binding.h to the implementation of gfortran (include file libgfortran.h) . > Using this I could implement the Fortran binding for TS29113. It works except for arrays of derived Fortran Types > which are always transferred via copy in/copy out. > > Hubert > ________________________________________ > From: mpiwg-fortran [mpiwg-fortran-bounces(a)lists.mpi-forum.org] on behalf of William Gropp [wgropp(a)illinois.edu] > Sent: Tuesday, June 23, 2015 9:34 PM > To: MPI-WG Fortran working group > Subject: Re: [MPIWG Fortran] What compilers support TS 29113? > > gfortran no, not even with 5.1.0 . It does have a lot of F 2008, but not even all of it, according to https://gcc.gnu.org/wiki/Fortran2008Status and https://gcc.gnu.org/wiki/TS29113Status . > Gfortran 5.1 fails the MPICH test because ISO_Fortran_binding.h isn’t available for GCC 5.1 (I don’t know if that’s the right test, but that’s what it does). See also https://gcc.gnu.org/onlinedocs/gfortran/Further-Interoperability-of-Fortran… . > > Bill > > William Gropp > Director, Parallel Computing Institute > Thomas M. Siebel Chair in Computer Science > Chief Scientist, NCSA > University of Illinois Urbana-Champaign > > > > > > On Jun 23, 2015, at 2:01 PM, Jeff Squyres (jsquyres) <jsquyres(a)cisco.com> wrote: > >> On Jun 23, 2015, at 11:51 AM, Bill Long <longb(a)cray.com> wrote: >>> >>> gfortran - yes (4.9 works on my Mac) >> >> I thought fortran 4.9 did not have the standardized TS 29113 dope vector...? >> >>> Cray - yes (8.3 for sure, or later). >> >> I knew about Cray, but I thought it was the only one. That may be incorrect and/or outdated information. >> >>> Not sure about others. People who build libraries (mpich, OpenMPI, ...) would know based on which ones can compiler their mpi_f08 module. >> >> Open MPI currently only has the non-TS-29113 interfaces for mpi_f08. We're looking into whether it's time to implement the TS 29113 interfaces; that's the origin of my question. :-) >> >> -- >> Jeff Squyres >> jsquyres(a)cisco.com >> For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/ >> >> _______________________________________________ >> mpiwg-fortran mailing list >> mpiwg-fortran(a)lists.mpi-forum.org >> http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran > > _______________________________________________ > mpiwg-fortran mailing list > mpiwg-fortran(a)lists.mpi-forum.org > http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran > > > Click https://www.mailcontrol.com/sr/op!XYE2yjUjGX2PQPOmvUiQSa3+T5MHvx+zSoc3i1rpp… to report this email as spam. > _______________________________________________ > mpiwg-fortran mailing list > mpiwg-fortran(a)lists.mpi-forum.org > http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran

1 0

Re: [MPIWG Fortran] What compilers support TS 29113?
by Hubert Ritzdorf 24 Jun '15

24 Jun '15

Hi, I used gfortran 4.9.1 and I have build an include file which adopted the definitions of the missing ISO_Fortran_binding.h to the implementation of gfortran (include file libgfortran.h) . Using this I could implement the Fortran binding for TS29113. It works except for arrays of derived Fortran Types which are always transferred via copy in/copy out. Hubert ________________________________________ From: mpiwg-fortran [mpiwg-fortran-bounces(a)lists.mpi-forum.org] on behalf of William Gropp [wgropp(a)illinois.edu] Sent: Tuesday, June 23, 2015 9:34 PM To: MPI-WG Fortran working group Subject: Re: [MPIWG Fortran] What compilers support TS 29113? gfortran no, not even with 5.1.0 . It does have a lot of F 2008, but not even all of it, according to https://gcc.gnu.org/wiki/Fortran2008Status and https://gcc.gnu.org/wiki/TS29113Status . Gfortran 5.1 fails the MPICH test because ISO_Fortran_binding.h isn’t available for GCC 5.1 (I don’t know if that’s the right test, but that’s what it does). See also https://gcc.gnu.org/onlinedocs/gfortran/Further-Interoperability-of-Fortran… . Bill William Gropp Director, Parallel Computing Institute Thomas M. Siebel Chair in Computer Science Chief Scientist, NCSA University of Illinois Urbana-Champaign On Jun 23, 2015, at 2:01 PM, Jeff Squyres (jsquyres) <jsquyres(a)cisco.com> wrote: > On Jun 23, 2015, at 11:51 AM, Bill Long <longb(a)cray.com> wrote: >> >> gfortran - yes (4.9 works on my Mac) > > I thought fortran 4.9 did not have the standardized TS 29113 dope vector...? > >> Cray - yes (8.3 for sure, or later). > > I knew about Cray, but I thought it was the only one. That may be incorrect and/or outdated information. > >> Not sure about others. People who build libraries (mpich, OpenMPI, ...) would know based on which ones can compiler their mpi_f08 module. > > Open MPI currently only has the non-TS-29113 interfaces for mpi_f08. We're looking into whether it's time to implement the TS 29113 interfaces; that's the origin of my question. :-) > > -- > Jeff Squyres > jsquyres(a)cisco.com > For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/ > > _______________________________________________ > mpiwg-fortran mailing list > mpiwg-fortran(a)lists.mpi-forum.org > http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran _______________________________________________ mpiwg-fortran mailing list mpiwg-fortran(a)lists.mpi-forum.org http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran Click https://www.mailcontrol.com/sr/op!XYE2yjUjGX2PQPOmvUiQSa3+T5MHvx+zSoc3i1rpp… to report this email as spam.

1 0

Re: [MPIWG Fortran] What compilers support TS 29113?
by William Gropp 23 Jun '15

23 Jun '15

gfortran no, not even with 5.1.0 . It does have a lot of F 2008, but not even all of it, according to https://gcc.gnu.org/wiki/Fortran2008Status and https://gcc.gnu.org/wiki/TS29113Status . Gfortran 5.1 fails the MPICH test because ISO_Fortran_binding.h isn’t available for GCC 5.1 (I don’t know if that’s the right test, but that’s what it does). See also https://gcc.gnu.org/onlinedocs/gfortran/Further-Interoperability-of-Fortran… . Bill William Gropp Director, Parallel Computing Institute Thomas M. Siebel Chair in Computer Science Chief Scientist, NCSA University of Illinois Urbana-Champaign On Jun 23, 2015, at 2:01 PM, Jeff Squyres (jsquyres) <jsquyres(a)cisco.com> wrote: > On Jun 23, 2015, at 11:51 AM, Bill Long <longb(a)cray.com> wrote: >> >> gfortran - yes (4.9 works on my Mac) > > I thought fortran 4.9 did not have the standardized TS 29113 dope vector...? > >> Cray - yes (8.3 for sure, or later). > > I knew about Cray, but I thought it was the only one. That may be incorrect and/or outdated information. > >> Not sure about others. People who build libraries (mpich, OpenMPI, ...) would know based on which ones can compiler their mpi_f08 module. > > Open MPI currently only has the non-TS-29113 interfaces for mpi_f08. We're looking into whether it's time to implement the TS 29113 interfaces; that's the origin of my question. :-) > > -- > Jeff Squyres > jsquyres(a)cisco.com > For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/ > > _______________________________________________ > mpiwg-fortran mailing list > mpiwg-fortran(a)lists.mpi-forum.org > http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran

1 0

Re: [MPIWG Fortran] What compilers support TS 29113?
by Lionel, Steve 23 Jun '15

23 Jun '15

Intel Fortran 16 will support all of TS29113, including C descriptors and ISO_Fortran_binding.h. There's a public beta ending soon - see https://software.intel.com/en-us/forums/topic/549312 On Jun 23, 2015, at 1:44 PM, Jeff Squyres (jsquyres) <jsquyres(a)cisco.com> wrote: > I have not been following the development of modern Fortran compilers recently... > > Have any new Fortran compiler releases added support for TS 29113? > > E.g., does gfortran 5.0 support it? Ifort 15? .?

1 0

Re: [MPIWG Fortran] What compilers support TS 29113?
by Junchao Zhang 23 Jun '15

23 Jun '15

I think xlf can satisfy MPI F08, https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/W4bf… I tired to build MPICH F08 with xlf but gave up in the end. It requires root privilege to install. After I bothered our admin, it turned out the trial tarball did not contain correct files supposed to have. --Junchao Zhang On Tue, Jun 23, 2015 at 1:51 PM, Bill Long <longb(a)cray.com> wrote: > > On Jun 23, 2015, at 1:44 PM, Jeff Squyres (jsquyres) <jsquyres(a)cisco.com> > wrote: > > > I have not been following the development of modern Fortran compilers > recently... > > > > Have any new Fortran compiler releases added support for TS 29113? > > > > E.g., does gfortran 5.0 support it? Ifort 15? …? > > gfortran - yes (4.9 works on my Mac) > > Cray - yes (8.3 for sure, or later). > > Not sure about others. People who build libraries (mpich, OpenMPI, ...) > would know based on which ones can compiler their mpi_f08 module. > > Cheers, > Bill > > > > > -- > > Jeff Squyres > > jsquyres(a)cisco.com > > For corporate legal information go to: > http://www.cisco.com/web/about/doing_business/legal/cri/ > > > > _______________________________________________ > > mpiwg-fortran mailing list > > mpiwg-fortran(a)lists.mpi-forum.org > > http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran > > Bill Long > longb(a)cray.com > Fortran Technical Support & voice: > 651-605-9024 > Bioinformatics Software Development fax: 651-605-9142 > Cray Inc./ Cray Plaza, Suite 210/ 380 Jackson St./ St. Paul, MN 55101 > > > _______________________________________________ > mpiwg-fortran mailing list > mpiwg-fortran(a)lists.mpi-forum.org > http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran >

1 0