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

Re: [MPIWG Fortran] Draft MPI-3 Errata
by William Gropp 22 Sep '13

22 Sep '13

Thanks. I've installed it on the not-yet-released new web site (moved from ANL to UIUC); the ANL site is down and the filesystem is inaccessible. Bill William Gropp Director, Parallel Computing Institute Deputy Director for Research Institute for Advanced Computing Applications and Technologies Thomas M. Siebel Chair in Computer Science University of Illinois Urbana-Champaign On Sep 22, 2013, at 6:50 AM, Rolf Rabenseifner wrote: > Dear Bill, > > perfect. > > Thank you and best regards > Rolf > > ----- Original Message ----- >> From: "William Gropp" <wgropp(a)illinois.edu> >> To: "MPI-WG Fortran working group" <mpiwg-fortran(a)lists.mpi-forum.org> >> Sent: Saturday, September 21, 2013 9:56:40 PM >> Subject: Re: [MPIWG Fortran] Draft MPI-3 Errata >> Thanks, Rolf. Attached is an updated version. >> >> Bill >> >> >> >> William Gropp >> Director, Parallel Computing Institute >> Deputy Director for Research >> Institute for Advanced Computing Applications and Technologies >> Thomas M. Siebel Chair in Computer Science >> University of Illinois Urbana-Champaign >> >> >> >> >> On Sep 21, 2013, at 11:45 AM, Rolf Rabenseifner wrote: >> >>> Dear Bill, >>> >>> thank you for your fast integration. >>> The following small corrections are needed: >>> >>> p1:28-29 >>> Please substitute "to several declarations. Those must also be >>> removed." >>> by "to a routine declaration. This change is now removed." >>> >>> Reasons: >>> - I tried to always say that the removal of BIND(C) is only >>> in "routine" declarations. The BIND(C) handles and status >>> type in mpi_f08 stay BIND(C). >>> - It was only MPI_Comm_create_group() - i.e., one routine. >>> In all other routines in the old errata, the original MPI-3.0 >>> had already the BIND(C), i.e., it was not added by the old >>> errata. >>> - The note is about a previous errata document. >>> The second sentence should tell, that in the current version, >>> this bug is removed: "This change is now removed." >>> >>> p2:16-18 >>> Please change "specific procedure" into "linker". >>> >>> Reason: The "old text" you saw, was already MPI-3.0 + ticket 388, >>> And not the really existing MPI-3.0 text. >>> My apologies for this confusion. >>> >>> p3:17-23 - Please remove, because already part of p2:11-25. >>> >>> p4:29-35 - Please remove, because already part of p2:11-25. >>> >>> p5:33-39 - Please remove, because already part of p2:11-25. >>> >>> p18:5 - Please remove the word "SUBROUTINE". >>> (The upper case Routine Name is okay, >>> because it is a callback "constant".) >>> >>> p18:21 - Please remove the word "SUBROUTINE". >>> >>> p18:1-28 - Please move it to the end of the errata. >>> (due to the errata are sorted by location). >>> >>> Best regards >>> Rolf >>> >>> ----- Original Message ----- >>>> From: "William Gropp" <wgropp(a)illinois.edu> >>>> To: "MPI-WG Fortran working group" >>>> <mpiwg-fortran(a)lists.mpi-forum.org> >>>> Sent: Friday, September 20, 2013 5:05:14 PM >>>> Subject: [MPIWG Fortran] Draft MPI-3 Errata >>>> Because it is so extensive and some of the items in the errata were >>>> superseded by this errata, I'd like to have the Fortran WG review >>>> the >>>> errata before I post it. Let me know if there are any errors to >>>> correct. >>>> >>>> Note that the use of page numbers (which I have always felt was a >>>> mistake) leads to some misleading pointers, since the relevant >>>> material in section 17.1.5 is not on the first page of that >>>> section. >>>> Rather than correct that here, I'll recommend eliminating the use >>>> of >>>> page references in the text for MPI 3.1 and later. >>>> >>>> Bill >>>> >>>> >>>> William Gropp >>>> Director, Parallel Computing Institute >>>> Deputy Director for Research >>>> Institute for Advanced Computing Applications and Technologies >>>> Thomas M. Siebel Chair in Computer Science >>>> University of Illinois Urbana-Champaign >>>> >>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> mpiwg-fortran mailing list >>>> mpiwg-fortran(a)lists.mpi-forum.org >>>> http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran >>> >>> -- >>> Dr. Rolf Rabenseifner . . . . . . . . . .. email >>> rabenseifner(a)hlrs.de >>> High Performance Computing Center (HLRS) . phone >>> ++49(0)711/685-65530 >>> University of Stuttgart . . . . . . . . .. fax ++49(0)711 / >>> 685-65832 >>> Head of Dpmt Parallel Computing . . . >>> www.hlrs.de/people/rabenseifner >>> Nobelstr. 19, D-70550 Stuttgart, Germany . . . . (Office: Room >>> 1.307) >>> _______________________________________________ >>> 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 > > -- > Dr. Rolf Rabenseifner . . . . . . . . . .. email rabenseifner(a)hlrs.de > High Performance Computing Center (HLRS) . phone ++49(0)711/685-65530 > University of Stuttgart . . . . . . . . .. fax ++49(0)711 / 685-65832 > Head of Dpmt Parallel Computing . . . www.hlrs.de/people/rabenseifner > Nobelstr. 19, D-70550 Stuttgart, Germany . . . . (Office: Room 1.307) > _______________________________________________ > 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] Draft MPI-3 Errata
by Rolf Rabenseifner 22 Sep '13

22 Sep '13

Dear Bill, perfect. Thank you and best regards Rolf ----- Original Message ----- > From: "William Gropp" <wgropp(a)illinois.edu> > To: "MPI-WG Fortran working group" <mpiwg-fortran(a)lists.mpi-forum.org> > Sent: Saturday, September 21, 2013 9:56:40 PM > Subject: Re: [MPIWG Fortran] Draft MPI-3 Errata > Thanks, Rolf. Attached is an updated version. > > Bill > > > > William Gropp > Director, Parallel Computing Institute > Deputy Director for Research > Institute for Advanced Computing Applications and Technologies > Thomas M. Siebel Chair in Computer Science > University of Illinois Urbana-Champaign > > > > > On Sep 21, 2013, at 11:45 AM, Rolf Rabenseifner wrote: > > > Dear Bill, > > > > thank you for your fast integration. > > The following small corrections are needed: > > > > p1:28-29 > > Please substitute "to several declarations. Those must also be > > removed." > > by "to a routine declaration. This change is now removed." > > > > Reasons: > > - I tried to always say that the removal of BIND(C) is only > > in "routine" declarations. The BIND(C) handles and status > > type in mpi_f08 stay BIND(C). > > - It was only MPI_Comm_create_group() - i.e., one routine. > > In all other routines in the old errata, the original MPI-3.0 > > had already the BIND(C), i.e., it was not added by the old > > errata. > > - The note is about a previous errata document. > > The second sentence should tell, that in the current version, > > this bug is removed: "This change is now removed." > > > > p2:16-18 > > Please change "specific procedure" into "linker". > > > > Reason: The "old text" you saw, was already MPI-3.0 + ticket 388, > > And not the really existing MPI-3.0 text. > > My apologies for this confusion. > > > > p3:17-23 - Please remove, because already part of p2:11-25. > > > > p4:29-35 - Please remove, because already part of p2:11-25. > > > > p5:33-39 - Please remove, because already part of p2:11-25. > > > > p18:5 - Please remove the word "SUBROUTINE". > > (The upper case Routine Name is okay, > > because it is a callback "constant".) > > > > p18:21 - Please remove the word "SUBROUTINE". > > > > p18:1-28 - Please move it to the end of the errata. > > (due to the errata are sorted by location). > > > > Best regards > > Rolf > > > > ----- Original Message ----- > >> From: "William Gropp" <wgropp(a)illinois.edu> > >> To: "MPI-WG Fortran working group" > >> <mpiwg-fortran(a)lists.mpi-forum.org> > >> Sent: Friday, September 20, 2013 5:05:14 PM > >> Subject: [MPIWG Fortran] Draft MPI-3 Errata > >> Because it is so extensive and some of the items in the errata were > >> superseded by this errata, I'd like to have the Fortran WG review > >> the > >> errata before I post it. Let me know if there are any errors to > >> correct. > >> > >> Note that the use of page numbers (which I have always felt was a > >> mistake) leads to some misleading pointers, since the relevant > >> material in section 17.1.5 is not on the first page of that > >> section. > >> Rather than correct that here, I'll recommend eliminating the use > >> of > >> page references in the text for MPI 3.1 and later. > >> > >> Bill > >> > >> > >> William Gropp > >> Director, Parallel Computing Institute > >> Deputy Director for Research > >> Institute for Advanced Computing Applications and Technologies > >> Thomas M. Siebel Chair in Computer Science > >> University of Illinois Urbana-Champaign > >> > >> > >> > >> > >> > >> _______________________________________________ > >> mpiwg-fortran mailing list > >> mpiwg-fortran(a)lists.mpi-forum.org > >> http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran > > > > -- > > Dr. Rolf Rabenseifner . . . . . . . . . .. email > > rabenseifner(a)hlrs.de > > High Performance Computing Center (HLRS) . phone > > ++49(0)711/685-65530 > > University of Stuttgart . . . . . . . . .. fax ++49(0)711 / > > 685-65832 > > Head of Dpmt Parallel Computing . . . > > www.hlrs.de/people/rabenseifner > > Nobelstr. 19, D-70550 Stuttgart, Germany . . . . (Office: Room > > 1.307) > > _______________________________________________ > > 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 -- Dr. Rolf Rabenseifner . . . . . . . . . .. email rabenseifner(a)hlrs.de High Performance Computing Center (HLRS) . phone ++49(0)711/685-65530 University of Stuttgart . . . . . . . . .. fax ++49(0)711 / 685-65832 Head of Dpmt Parallel Computing . . . www.hlrs.de/people/rabenseifner Nobelstr. 19, D-70550 Stuttgart, Germany . . . . (Office: Room 1.307)

1 0

Re: [MPIWG Fortran] Draft MPI-3 Errata
by William Gropp 21 Sep '13

21 Sep '13

Thanks, Rolf. Attached is an updated version. Bill William Gropp Director, Parallel Computing Institute Deputy Director for Research Institute for Advanced Computing Applications and Technologies Thomas M. Siebel Chair in Computer Science University of Illinois Urbana-Champaign On Sep 21, 2013, at 11:45 AM, Rolf Rabenseifner wrote: > Dear Bill, > > thank you for your fast integration. > The following small corrections are needed: > > p1:28-29 > Please substitute "to several declarations. Those must also be removed." > by "to a routine declaration. This change is now removed." > > Reasons: > - I tried to always say that the removal of BIND(C) is only > in "routine" declarations. The BIND(C) handles and status > type in mpi_f08 stay BIND(C). > - It was only MPI_Comm_create_group() - i.e., one routine. > In all other routines in the old errata, the original MPI-3.0 > had already the BIND(C), i.e., it was not added by the old errata. > - The note is about a previous errata document. > The second sentence should tell, that in the current version, > this bug is removed: "This change is now removed." > > p2:16-18 > Please change "specific procedure" into "linker". > > Reason: The "old text" you saw, was already MPI-3.0 + ticket 388, > And not the really existing MPI-3.0 text. > My apologies for this confusion. > > p3:17-23 - Please remove, because already part of p2:11-25. > > p4:29-35 - Please remove, because already part of p2:11-25. > > p5:33-39 - Please remove, because already part of p2:11-25. > > p18:5 - Please remove the word "SUBROUTINE". > (The upper case Routine Name is okay, > because it is a callback "constant".) > > p18:21 - Please remove the word "SUBROUTINE". > > p18:1-28 - Please move it to the end of the errata. > (due to the errata are sorted by location). > > Best regards > Rolf > > ----- Original Message ----- >> From: "William Gropp" <wgropp(a)illinois.edu> >> To: "MPI-WG Fortran working group" <mpiwg-fortran(a)lists.mpi-forum.org> >> Sent: Friday, September 20, 2013 5:05:14 PM >> Subject: [MPIWG Fortran] Draft MPI-3 Errata >> Because it is so extensive and some of the items in the errata were >> superseded by this errata, I'd like to have the Fortran WG review the >> errata before I post it. Let me know if there are any errors to >> correct. >> >> Note that the use of page numbers (which I have always felt was a >> mistake) leads to some misleading pointers, since the relevant >> material in section 17.1.5 is not on the first page of that section. >> Rather than correct that here, I'll recommend eliminating the use of >> page references in the text for MPI 3.1 and later. >> >> Bill >> >> >> William Gropp >> Director, Parallel Computing Institute >> Deputy Director for Research >> Institute for Advanced Computing Applications and Technologies >> Thomas M. Siebel Chair in Computer Science >> University of Illinois Urbana-Champaign >> >> >> >> >> >> _______________________________________________ >> mpiwg-fortran mailing list >> mpiwg-fortran(a)lists.mpi-forum.org >> http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran > > -- > Dr. Rolf Rabenseifner . . . . . . . . . .. email rabenseifner(a)hlrs.de > High Performance Computing Center (HLRS) . phone ++49(0)711/685-65530 > University of Stuttgart . . . . . . . . .. fax ++49(0)711 / 685-65832 > Head of Dpmt Parallel Computing . . . www.hlrs.de/people/rabenseifner > Nobelstr. 19, D-70550 Stuttgart, Germany . . . . (Office: Room 1.307) > _______________________________________________ > 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] Draft MPI-3 Errata
by Rolf Rabenseifner 21 Sep '13

21 Sep '13

Dear Bill, thank you for your fast integration. The following small corrections are needed: p1:28-29 Please substitute "to several declarations. Those must also be removed." by "to a routine declaration. This change is now removed." Reasons: - I tried to always say that the removal of BIND(C) is only in "routine" declarations. The BIND(C) handles and status type in mpi_f08 stay BIND(C). - It was only MPI_Comm_create_group() - i.e., one routine. In all other routines in the old errata, the original MPI-3.0 had already the BIND(C), i.e., it was not added by the old errata. - The note is about a previous errata document. The second sentence should tell, that in the current version, this bug is removed: "This change is now removed." p2:16-18 Please change "specific procedure" into "linker". Reason: The "old text" you saw, was already MPI-3.0 + ticket 388, And not the really existing MPI-3.0 text. My apologies for this confusion. p3:17-23 - Please remove, because already part of p2:11-25. p4:29-35 - Please remove, because already part of p2:11-25. p5:33-39 - Please remove, because already part of p2:11-25. p18:5 - Please remove the word "SUBROUTINE". (The upper case Routine Name is okay, because it is a callback "constant".) p18:21 - Please remove the word "SUBROUTINE". p18:1-28 - Please move it to the end of the errata. (due to the errata are sorted by location). Best regards Rolf ----- Original Message ----- > From: "William Gropp" <wgropp(a)illinois.edu> > To: "MPI-WG Fortran working group" <mpiwg-fortran(a)lists.mpi-forum.org> > Sent: Friday, September 20, 2013 5:05:14 PM > Subject: [MPIWG Fortran] Draft MPI-3 Errata > Because it is so extensive and some of the items in the errata were > superseded by this errata, I'd like to have the Fortran WG review the > errata before I post it. Let me know if there are any errors to > correct. > > Note that the use of page numbers (which I have always felt was a > mistake) leads to some misleading pointers, since the relevant > material in section 17.1.5 is not on the first page of that section. > Rather than correct that here, I'll recommend eliminating the use of > page references in the text for MPI 3.1 and later. > > Bill > > > William Gropp > Director, Parallel Computing Institute > Deputy Director for Research > Institute for Advanced Computing Applications and Technologies > Thomas M. Siebel Chair in Computer Science > University of Illinois Urbana-Champaign > > > > > > _______________________________________________ > mpiwg-fortran mailing list > mpiwg-fortran(a)lists.mpi-forum.org > http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran -- Dr. Rolf Rabenseifner . . . . . . . . . .. email rabenseifner(a)hlrs.de High Performance Computing Center (HLRS) . phone ++49(0)711/685-65530 University of Stuttgart . . . . . . . . .. fax ++49(0)711 / 685-65832 Head of Dpmt Parallel Computing . . . www.hlrs.de/people/rabenseifner Nobelstr. 19, D-70550 Stuttgart, Germany . . . . (Office: Room 1.307)

1 0

Draft MPI-3 Errata
by William Gropp 20 Sep '13

20 Sep '13

Because it is so extensive and some of the items in the errata were superseded by this errata, I'd like to have the Fortran WG review the errata before I post it. Let me know if there are any errors to correct. Note that the use of page numbers (which I have always felt was a mistake) leads to some misleading pointers, since the relevant material in section 17.1.5 is not on the first page of that section. Rather than correct that here, I'll recommend eliminating the use of page references in the text for MPI 3.1 and later. Bill William Gropp Director, Parallel Computing Institute Deputy Director for Research Institute for Advanced Computing Applications and Technologies Thomas M. Siebel Chair in Computer Science University of Illinois Urbana-Champaign

1 0

Re: [MPIWG Fortran] Question about 388 errata
by Bill Long 18 Sep '13

18 Sep '13

OK from me. Cheers, Bill On 9/18/13 1:03 PM, Rolf Rabenseifner wrote: > I read all the discussion up to now, and the new proposal is in > https://svn.mpi-forum.org/trac/mpi-forum-web/attachment/ticket/388/errata-3… > > Page 7 lines 14-15 read > > For TS 29113 quality, new routines > are needed only for routines with choice buffer arguments. > > but should read > > If the accompanying Fortran compiler supports TS 29113, then new routines > are needed only for routines with choice buffer arguments. > > ____________ > Short explanation: We used the word "accompanying" already in the MPI standard > several times for the accompanying C++ compiler. > For Fortran we used in 17.1.7 the wording > "the Fortran compiler suite for which it is compiled." > I believe, here in this advice, the shortcut "accompanying" is good enough. > > With this, the round of reviews within the Fortran-WG starts again. > Please explicitly send an okay (or better wording). > > Best regards > Rolf > > -- 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 388 errata
by Rolf Rabenseifner 18 Sep '13

18 Sep '13

I read all the discussion up to now, and the new proposal is in https://svn.mpi-forum.org/trac/mpi-forum-web/attachment/ticket/388/errata-3… Page 7 lines 14-15 read For TS 29113 quality, new routines are needed only for routines with choice buffer arguments. but should read If the accompanying Fortran compiler supports TS 29113, then new routines are needed only for routines with choice buffer arguments. ____________ Short explanation: We used the word "accompanying" already in the MPI standard several times for the accompanying C++ compiler. For Fortran we used in 17.1.7 the wording "the Fortran compiler suite for which it is compiled." I believe, here in this advice, the shortcut "accompanying" is good enough. With this, the round of reviews within the Fortran-WG starts again. Please explicitly send an okay (or better wording). Best regards Rolf -- Dr. Rolf Rabenseifner . . . . . . . . . .. email rabenseifner(a)hlrs.de High Performance Computing Center (HLRS) . phone ++49(0)711/685-65530 University of Stuttgart . . . . . . . . .. fax ++49(0)711 / 685-65832 Head of Dpmt Parallel Computing . . . www.hlrs.de/people/rabenseifner Nobelstr. 19, D-70550 Stuttgart, Germany . . . . (Office: Room 1.307)

1 0

Re: [MPIWG Fortran] Question about 388 errata
by N.M. Maclaren 18 Sep '13

18 Sep '13

On Sep 18 2013, Bill Long wrote: > >I'm not sufficiently informed about earlier MPI discussions to know >which is intended, but wanted to point out the distinction. Rolf's >statement is essentially a requirement that all MPI vendors support the >new routines. Mine is just a statement of fact and does not impose a >requirement on the vendors. > >I'm satisfied with either intention, since I use both of the new >compilers and would always want (as a user, and provide as an MPI >vendor) the new routines anyway. When I can rely on the new interfaces, and get a moment to update my course, I will start to teach them. I suspect that most users and teachers will agree with us, so it really is fairly moot how this is phrased. Regards, Nick Maclaren.

1 0

Re: [MPIWG Fortran] Question about 388 errata
by Bill Long 18 Sep '13

18 Sep '13

On 9/18/13 6:03 AM, Rolf Rabenseifner wrote: > I propose in > https://svn.mpi-forum.org/trac/mpi-forum-web/attachment/ticket/388/errata-3… > > Page 7 lines 14-15 read > > For TS 29113 quality, new routines > are needed only for routines with choice buffer arguments. > > but should read > > If the Fortran compiler implements TS 29113, then new routines > are needed only for routines with choice buffer arguments. This seems to be conflating two concepts. Whether the Fortran compiler supports TS 29113 depends on the compiler vendor. But this is an Advice to the MPI library vendors. The sentence seems to read that having at least one Fortran vendor supporting TS 29113 forces MPI vendors to supply the extra routines. If that is the intent, then the first clause of the sentence is unnecessary, since there are already two compilers with TS 29113 support. The version I proposed: "To take advantage of the features enabled by TS 29113, new routines are needed only for routines with choice buffer arguments." unlinks the requirements and allows the MPI vendor to not implement the extra routines and choose to ignore that fact that some of its users might have a Fortran compiler with TS support. I'm not sufficiently informed about earlier MPI discussions to know which is intended, but wanted to point out the distinction. Rolf's statement is essentially a requirement that all MPI vendors support the new routines. Mine is just a statement of fact and does not impose a requirement on the vendors. I'm satisfied with either intention, since I use both of the new compilers and would always want (as a user, and provide as an MPI vendor) the new routines anyway. Cheers, Bill > > (We always use the short-cut TS 29113, the long version is in the bib-list) > > Jeff S., Jeff H., Craig, Bill L., > > please give an explicit okay (or a better text). > > Best regards > Rolf > > > > ----- Original Message ----- >> From: "William Gropp" <wgropp(a)illinois.edu> >> To: longb(a)cray.com, "MPI-WG Fortran working group" <mpiwg-fortran(a)lists.mpi-forum.org> >> Sent: Tuesday, September 17, 2013 1:04:57 AM >> Subject: Re: [MPIWG Fortran] Question about 388 errata >> What I need is a specific replacement for that sentence to which the >> WG agrees. ï¿½ Suggestions? >> >> >> Bill >> >> >> >> >> >> Williamï¿½ Gropp >> Director, Parallel Computing Institute >> Deputy Director for Research >> Institute for Advanced Computing Applications and Technologies Thomas >> M. Siebel Chair in Computer Science >> >> >> University of Illinois Urbana-Champaign >> >> >> >> >> >> >> On Sep 16, 2013, at 11:49 AM, Bill Long wrote: >> >> >> >> I think the intent is "To take advantage of the features enabled by TS >> 29113, new routines are needed...". ï¿½ The main thrust of the TS, as far >> as MPI is concerned, is the capability to pass an argument by (pointer >> to a ) descriptor, rather than as a plain address. ï¿½ This is only done >> for choice buffer arguments. >> >> The actual side effect of this is that for routines that do not have >> choice buffer arguments (MPI_Barrier.... ) ï¿½ the implementation layer >> in the C library is the same as before. ï¿½ Only for the ones with choice >> buffer arguments is there a need for both the legacy version (with a >> (void *) format parameter) and the new one that handles pointer to a >> descriptor. >> >> Cheers, >> Bill >> >> >> On 9/16/13 11:39 AM, Jeff Hammond wrote: >> >> >> I think "the Fortran compiler implements ISO/IEC TS 29113:2012" is >> more >> >> >> accurate. >> >> >> >> >> >> Jeff >> >> >> >> >> >> >> >> >> >> >> >> On Mon, Sep 16, 2013 at 10:56 AM, William Gropp < wgropp(a)illinois.edu >> >> >> < mailto:[email protected] >> wrote: >> >> >>> >> >> >>> There was one phrase that I found imprecise. ï¿½ Just what does "TS >> >> >> 29113 quality" mean? ï¿½ I can guess, but the standard should not make me >> >> >> guess. >> >> >>> >> >> >>> Bill >> >> >>> >> >> >>> William Gropp >> >> >>> Director, Parallel Computing Institute >> >> >>> Deputy Director for Research >> >> >>> Institute for Advanced Computing Applications and Technologies >> >> >>> Thomas M. Siebel Chair in Computer Science >> >> >>> University of Illinois Urbana-Champaign >> >> >>> >> >> >>> >> >> >>> >> >> >>> >> >> >>> >> >> >>> _______________________________________________ >> >> >>> mpiwg-fortran mailing list >> >> >>> mpiwg-fortran(a)lists.mpi-forum.org >> >> >> < mailto:[email protected] > >> >> >>> http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> -- >> >> >> Jeff Hammond >> >> >> jeff.science(a)gmail.com < mailto:[email protected] > >> >> >> >> >> >> >> >> >> _______________________________________________ >> >> >> 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 388 errata
by Jeff Hammond 18 Sep '13

18 Sep '13

Explicitly okay with me. Jeff Sent from my iPhone On Sep 18, 2013, at 7:56 AM, William Gropp <wgropp(a)illinois.edu> wrote: I like this, and prefer supports. Bill William Gropp Director, Parallel Computing Institute Deputy Director for Research Institute for Advanced Computing Applications and Technologies Thomas M. Siebel Chair in Computer Science University of Illinois Urbana-Champaign On Sep 18, 2013, at 5:11 AM, N.M. Maclaren wrote: On Sep 18 2013, Rolf Rabenseifner wrote: I propose in https://svn.mpi-forum.org/trac/mpi-forum-web/attachment/ticket/388/errata-3… Page 7 lines 14-15 read For TS 29113 quality, new routines are needed only for routines with choice buffer arguments. but should read If the Fortran compiler implements TS 29113, then new routines are needed only for routines with choice buffer arguments. (We always use the short-cut TS 29113, the long version is in the bib-list) Jeff S., Jeff H., Craig, Bill L., please give an explicit okay (or a better text). 'supports' might be better than 'implements', but that's a trivial point. I think that it's very clear, and better than before. Regards, Nick Maclaren. _______________________________________________ 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