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

Re: [MPIWG Fortran] Question about named constants
by Bill Long 18 Jun '15

18 Jun '15

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

1 0

Re: [MPIWG Fortran] Question about named constants
by William Gropp 18 Jun '15

18 Jun '15

This has more to do with whether things like MPI_INTEGER are compile-time constants (as they are in MPICH) or pointers to memory that are determined when the application is linked with the library. Bill On Jun 18, 2015, at 12:48 PM, Bill Long <longb(a)cray.com> wrote: > > > 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? >

1 0

Re: [MPIWG Fortran] Question about named constants
by Junchao Zhang 18 Jun '15

18 Jun '15

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. --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 >

1 0

Re: [MPIWG Fortran] Question about named constants
by Bill Long 18 Jun '15

18 Jun '15

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

1 0

Question about named constants
by Junchao Zhang 18 Jun '15

18 Jun '15

Hello, Fortran experts, I am a little puzzled by MPI-3.1 Chapter 2.5.4, 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. Then in F08, should MPI_INTEGER be declared as a parameter variable? 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. 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? Thank you! --Junchao Zhang

1 0

PDF review for #441
by Jeff Squyres (jsquyres) 11 Dec '14

11 Dec '14

Per ticket #441 which was passed yesterday, I have text ready to commit once a few people can review the PDF I generated to ensure that I transcribed the solution from the ticket to the text properly. Please review the PDF attached to #441: https://svn.mpi-forum.org/trac/mpi-forum-web/ticket/441 The new text is on page 626, lines 37-40. Please put your review on the ticket. Thanks! -- Jeff Squyres jsquyres(a)cisco.com For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/

1 0

Deprecate MPI_SIZEOF
by Jeff Squyres (jsquyres) 11 Dec '14

11 Dec '14

Ticket created, proposed PDF attached: https://svn.mpi-forum.org/trac/mpi-forum-web/ticket/465 -- Jeff Squyres jsquyres(a)cisco.com For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/

1 0

Re: [MPIWG Fortran] Simple / quick errata PDF reviews
by Bill Long 08 Dec '14

08 Dec '14

Hi Jeff, Thanks for the PDF links. They all look OK. I updated the three tickets with approval of the PDF changes. Cheers, Bill On Dec 8, 2014, at 5:50 AM, Jeff Squyres (jsquyres) <jsquyres(a)cisco.com> wrote: > Bill -- > > The intent of the review is to ensure that I faithfully put the text from the ticket into the actual MPI 3.1 document. So if you wouldn't mind checking to ensure that I did it right, that would be great. > > I uploaded all 3 PDFs here, in case your email client is stripping the PDFs for some reason: > > http://www.open-mpi.org/~jsquyres/mpi-forum/ > > Thanks! > > > On Dec 8, 2014, at 12:33 AM, Bill Long <longb(a)cray.com> wrote: > >> >> On Dec 6, 2014, at 3:52 AM, Jeff Squyres (jsquyres) <jsquyres(a)cisco.com> wrote: >> >>> Now that the bulk of the Fortran errata text has been committed, there are two more open errata tickets regarding the language bindings chapter. Can you please review the PDF to ensure that I have applied them correctly? Both are short / easy to review: >>> >>> 1. Ticket 393: Fortran module CONTAINS - Advice to implementors (the "Bill Long" ticket) >>> >>> https://svn.mpi-forum.org/trac/mpi-forum-web/ticket/393 >>> >>> Reader cache refresh: after much debate about CONTAINS, we resolved to add a simple AtoI that implies that you can implement the Fortran modules however you want, as long as the profiling rules are obeyed. >>> >>> *** PLEASE REVIEW: 1st attached PDF. The AtoI is added in the first PDF, on page 611, lines 27-30. >> >> My mail program says the attachment is an empty file. However, if the text is the same as in Comment 7 of the ticket, that’s fine with me. >> >> Cheers, >> Bill >> >> >>> >>> 2. Ticket 424: Incorrect Fortran type for flag in IMPROBE >>> >>> https://svn.mpi-forum.org/trac/mpi-forum-web/ticket/424 >>> >>> Reader cache refresh: trivial errata -- change the "flag" dummy parameter from INTEGER to LOGICAL. >>> >>> *** PLEASE REVIEW: 2nd attached PDF. Page 68, lines 21 and 27-28. >>> >>> -- >>> Jeff Squyres >>> jsquyres(a)cisco.com >>> For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/ >>> <mpi31-report-ticket-393.pdf><mpi31-report-ticket-424.pdf>_______________________________________________ >>> 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 Suport & 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 > > > -- > 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 Suport & 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] Oops: one more trivial errata PDF review
by Hubert Ritzdorf 08 Dec '14

08 Dec '14

I reviewed it and the ticket is correctly integrated. Hubert ________________________________________ From: mpiwg-fortran [mpiwg-fortran-bounces(a)lists.mpi-forum.org] on behalf of Jeff Squyres (jsquyres) [jsquyres(a)cisco.com] Sent: Saturday, December 06, 2014 3:00 PM To: MPI Fortran WG Subject: [MPIWG Fortran] Oops: one more trivial errata PDF review I missed that there is a 3rd trivial errata ticket to review: 3. Ticket 415: Errata: mpi_f08 MPI_Status must use INTEGER fields https://svn.mpi-forum.org/trac/mpi-forum-web/ticket/415 Reader cache refresh: trivial clarification to ensure that TYPE(MPI_Status) has INTEGER public fields (without this clarification, implementors could have used INTEGER(C_INT), for example). *** PLEASE REVIEW: Page 30, line 24. -- Jeff Squyres jsquyres(a)cisco.com For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/ Click https://www.mailcontrol.com/sr/RmeTlh+53a7WQxILzJ5p98vbwKNQcrHngaiIUx9XfgQ6… to report this email as spam.

1 0

Re: [MPIWG Fortran] Simple / quick errata PDF reviews
by Jeff Squyres (jsquyres) 08 Dec '14

08 Dec '14

Bill -- The intent of the review is to ensure that I faithfully put the text from the ticket into the actual MPI 3.1 document. So if you wouldn't mind checking to ensure that I did it right, that would be great. I uploaded all 3 PDFs here, in case your email client is stripping the PDFs for some reason: http://www.open-mpi.org/~jsquyres/mpi-forum/ Thanks! On Dec 8, 2014, at 12:33 AM, Bill Long <longb(a)cray.com> wrote: > > On Dec 6, 2014, at 3:52 AM, Jeff Squyres (jsquyres) <jsquyres(a)cisco.com> wrote: > >> Now that the bulk of the Fortran errata text has been committed, there are two more open errata tickets regarding the language bindings chapter. Can you please review the PDF to ensure that I have applied them correctly? Both are short / easy to review: >> >> 1. Ticket 393: Fortran module CONTAINS - Advice to implementors (the "Bill Long" ticket) >> >> https://svn.mpi-forum.org/trac/mpi-forum-web/ticket/393 >> >> Reader cache refresh: after much debate about CONTAINS, we resolved to add a simple AtoI that implies that you can implement the Fortran modules however you want, as long as the profiling rules are obeyed. >> >> *** PLEASE REVIEW: 1st attached PDF. The AtoI is added in the first PDF, on page 611, lines 27-30. > > My mail program says the attachment is an empty file. However, if the text is the same as in Comment 7 of the ticket, that’s fine with me. > > Cheers, > Bill > > >> >> 2. Ticket 424: Incorrect Fortran type for flag in IMPROBE >> >> https://svn.mpi-forum.org/trac/mpi-forum-web/ticket/424 >> >> Reader cache refresh: trivial errata -- change the "flag" dummy parameter from INTEGER to LOGICAL. >> >> *** PLEASE REVIEW: 2nd attached PDF. Page 68, lines 21 and 27-28. >> >> -- >> Jeff Squyres >> jsquyres(a)cisco.com >> For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/ >> <mpi31-report-ticket-393.pdf><mpi31-report-ticket-424.pdf>_______________________________________________ >> 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 Suport & 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 -- Jeff Squyres jsquyres(a)cisco.com For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/

1 0