- mpi-forum - mailman3.cels.anl.gov

Vote announcement for the July 2023 meeting of the MPI Forum
by Rolf Rabenseifner 09 May '23

09 May '23

Dear forum members, (correction: it is for the July 2023 meeting) I would like to make the following announcements for the next MPI Forum Meeting (July 10-13, 2023): - 2nd votes on #669 Add operation state 'enabled' and 'local calls' into Terms Rolf Issue https://github.com/mpi-forum/mpi-issues/issues/669 PR https://github.com/mpi-forum/mpi-standard/pull/788 #457 Improvements around the word "rank" in the Process Topologies chapter Christoph,Rolf Issue https://github.com/mpi-forum/mpi-issues/issues/457 PR https://github.com/mpi-forum/mpi-standard/pull/804 #485 Fix Incorrect Usage of Rank/Task/etc. in Language Bindings Chapter Rolf,Puri Issue https://github.com/mpi-forum/mpi-issues/issues/485 PR https://github.com/mpi-forum/mpi-standard/pull/803 PDF https://github.com/mpi-forum/mpi-standard/files/10831598/mpi41-report_Issue… - errata reading and vote on #679 Errata: Noncollective (for procedure) and nonpersistent are not defined Rolf Issue https://github.com/mpi-forum/mpi-issues/issues/679 PR https://github.com/mpi-forum/mpi-standard/pull/820 PDF https://github.com/mpi-forum/mpi-standard/files/11432286/mpi41-report_Issue… - pre-announcement for errata reading and vote on --> See also virtual meeting, June 7, 2023 !!! #705 Errata: Fortran has only compile-time constants Rolf,Joseph Issue https://github.com/mpi-forum/mpi-issues/issues/705 (together with https://github.com/mpi-forum/mpi-issues/issues/657 Rolf, Jeff H.) PR https://github.com/mpi-forum/mpi-standard/pull/822 #710 Errata: 'Pending communication' not defined in MPI_Comm_disconnect Rolf Issue https://github.com/mpi-forum/mpi-issues/issues/710 PR https://github.com/mpi-forum/mpi-standard/pull/823 #676 Errata: 'Pending operation' not defined, pending proper definition Rolf,Joseph Issue https://github.com/mpi-forum/mpi-issues/issues/676 PR https://github.com/mpi-forum/mpi-standard/pull/824 Best regards Rolf Rabenseifner -- Dr. Rolf Rabenseifner . . . . . . . . . .. . . rabenseifner(a)hlrs.de . High Performance Computing Center (HLRS) . . . ++49(0)711/685-65530 . University of Stuttgart . . . . . . www.hlrs.de/people/rabenseifner . Nobelstr. 19, 70569 Stuttgart, Germany

1 0

Re: [Mpi-forum] Vote announcement for the May 2023 meeting of the MPI Forum
by Rolf Rabenseifner 09 May '23

09 May '23

Dear forum members, I would like to make the following announcements for the next MPI Forum Meeting (May 2-5, 2023): - 2nd votes on #669 Add operation state 'enabled' and 'local calls' into Terms Rolf Issue https://github.com/mpi-forum/mpi-issues/issues/669 PR https://github.com/mpi-forum/mpi-standard/pull/788 #457 Improvements around the word "rank" in the Process Topologies chapter Christoph,Rolf Issue https://github.com/mpi-forum/mpi-issues/issues/457 PR https://github.com/mpi-forum/mpi-standard/pull/804 #485 Fix Incorrect Usage of Rank/Task/etc. in Language Bindings Chapter Rolf,Puri Issue https://github.com/mpi-forum/mpi-issues/issues/485 PR https://github.com/mpi-forum/mpi-standard/pull/803 PDF https://github.com/mpi-forum/mpi-standard/files/10831598/mpi41-report_Issue… - errata reading and vote on #679 Errata: Noncollective (for procedure) and nonpersistent are not defined Rolf Issue https://github.com/mpi-forum/mpi-issues/issues/679 PR https://github.com/mpi-forum/mpi-standard/pull/820 PDF https://github.com/mpi-forum/mpi-standard/files/11432286/mpi41-report_Issue… - pre-announcement for errata reading and vote on --> See also virtual meeting, June 7, 2023 !!! #705 Errata: Fortran has only compile-time constants Rolf,Joseph Issue https://github.com/mpi-forum/mpi-issues/issues/705 (together with https://github.com/mpi-forum/mpi-issues/issues/657 Rolf, Jeff H.) PR https://github.com/mpi-forum/mpi-standard/pull/822 #710 Errata: 'Pending communication' not defined in MPI_Comm_disconnect Rolf Issue https://github.com/mpi-forum/mpi-issues/issues/710 PR https://github.com/mpi-forum/mpi-standard/pull/823 #676 Errata: 'Pending operation' not defined, pending proper definition Rolf,Joseph Issue https://github.com/mpi-forum/mpi-issues/issues/676 PR https://github.com/mpi-forum/mpi-standard/pull/824 Best regards Rolf Rabenseifner -- Dr. Rolf Rabenseifner . . . . . . . . . .. . . rabenseifner(a)hlrs.de . High Performance Computing Center (HLRS) . . . ++49(0)711/685-65530 . University of Stuttgart . . . . . . www.hlrs.de/people/rabenseifner . Nobelstr. 19, 70569 Stuttgart, Germany

1 0

Re: [Mpi-forum] All MPI implementors: Implementation of MPI constants in C and Fortran / MPI meeting May 3, 2023 9am CDT discussion
by Jeff Hammond 04 May '23

04 May '23

Many constants cannot be used in "fixed array length in a declaration" because they are negative numbers, which is not only legal but the only choice for MPI_UNDEFINED, so you cannot use that criteria for anything. We say "All named constants, with the exceptions noted below for Fortran, can be used in initialization expressions or assignments," which means the following is valid: #include <mpi.h> static int x = MPI_ANY_SOURCE; int main(void) { return 0; } C static global initialization of integers requires compile-time constants (example below). While we may have implied that all constants could be link-time constants, this is only possible for non-integer constants, i.e. handles and buffer address constants. % cat init.c extern int w; static int* p = &w; static int q = w; % gcc -c init.c init.c:3:16: error: initializer element is not a compile-time constant static int q = w; ^ 1 error generated. Jeff On Tue, May 2, 2023 at 9:51 PM Rolf Rabenseifner via mpi-forum < mpi-forum(a)lists.mpi-forum.org> wrote: > > Dear implementor of an MPI library, > > Based on the discussion today in the MPI forum meeting, > I have the following urgent question to you: > > Did you implement all MPI constants that are described in Annex A.1.1 > as of type "const int (or unnamed enum)" > as "C integer constant expression" > (according to the specification of the C language)? > > If yes, then all is okay and the proposed change of the MPI standard in > https://github.com/mpi-forum/mpi-standard/pull/821/files > will not require any change of your MPI implementation. > > If not, then please can you tell which MPI constant(s) MPI_XXX > > - have you implemented in a way that > > - it still can be used in an initialization expression, > i.e., in a application statement like > int x=MPI_XXX; > - but it cannot be used as a case-label in a switch statement like > switch(MPI_XXX) { > case MPI_XXX: printf("XXX\n"); > default: ; > } > - and cannot be used as a fixed array length in a declaration like > float x[MPI_XXX]; > > - and how implemented you such an MPI constant that this problem arises? > > We'll discuss this again tomorrow May 3, 2023 at the beginning > of the MPI forum meeting. > > See you hopefully at the meeting, > and hopefully reporting that you have no problem with the proposal, > > kind regards > Rolf > > > ----- Original Message ----- > > From: "Rolf Rabenseifner" <rabenseifner(a)hlrs.de> > > To: "Main MPI Forum mailing list" <mpi-forum(a)lists.mpi-forum.org> > > Cc: "Puri Bangalore" <pvbangalore(a)ua.edu>, "Claudia Blaas-Schenner" < claudia.blaas-schenner(a)tuwien.ac.at>, "Jeff > > Hammond" <jeff.science(a)gmail.com> > > Sent: Tuesday, May 2, 2023 2:04:01 PM > > Subject: Re: Informal meeting announcement for the May 2023 meeting of the MPI Forum > > > Der forum memebers, dear Wesley, > > > > please can we add in the agenda after > > > > Informal Errata Reading 705 Fortran has only compile-time constants Rolf > > > > an additional slot > > > > Errata Discussion 657 All C const int (or unnamed enum) as compile-time > > constants Rolf, Jeff H. > > > > Bestr regards > > Rolf > > > > > > ----- Original Message ----- > >> From: "Rolf Rabenseifner" <rabenseifner(a)hlrs.de> > >> To: "Main MPI Forum mailing list" <mpi-forum(a)lists.mpi-forum.org> > >> Cc: "Puri Bangalore" <pvbangalore(a)ua.edu>, "Claudia Blaas-Schenner" > >> <claudia.blaas-schenner(a)tuwien.ac.at> > >> Sent: Saturday, April 29, 2023 7:38:00 AM > >> Subject: Informal meeting announcement for the May 2023 meeting of the MPI Forum > > > >> Dear forum members, > >> > >> I would like to make the following announcements for the next MPI Forum Meeting > >> (May 2-5, 2023): > >> > >> - informal reading and discussion > >> #705 Errata: Fortran has only compile-time constants Rolf > >> Issue https://github.com/mpi-forum/mpi-issues/issues/705 > >> PR https://github.com/mpi-forum/mpi-standard/pull/819 > >> PDF > >> https://github.com/mpi-forum/mpi-standard/files/11358444/mpi41-report_Issue… > >> > >> This errata should be completely discussed in next (May 2-5, 2023) meeting. > >> It is then planned to have an final errata reading plus errata vote at next > >> meeting (July 10-13, 2023). > >> > >> It is a bug since MPI-2.2 because a problem in C was directly mapped to Fortran. > >> This mapping was wrong. > >> In Fortran, there is no distinction between link-time and compile-time > >> constants. > >> > >> Best regards > >> Rolf Rabenseifner > > > > > > -- > > Dr. Rolf Rabenseifner . . . . . . . . . .. . . rabenseifner(a)hlrs.de . > > High Performance Computing Center (HLRS) . . . ++49(0)711/685-65530 . > > University of Stuttgart . . . . . . www.hlrs.de/people/rabenseifner . > > Nobelstr. 19, 70569 Stuttgart, Germany > > -- > Dr. Rolf Rabenseifner . . . . . . . . . .. . . rabenseifner(a)hlrs.de . > High Performance Computing Center (HLRS) . . . ++49(0)711/685-65530 . > University of Stuttgart . . . . . . www.hlrs.de/people/rabenseifner . > Nobelstr. 19, 70569 Stuttgart, Germany > _______________________________________________ > mpi-forum mailing list > mpi-forum(a)lists.mpi-forum.org > https://lists.mpi-forum.org/mailman/listinfo/mpi-forum -- Jeff Hammond jeff.science(a)gmail.com http://jeffhammond.github.io/

1 0

Results for May 3, 2023 Ballot
by Wes Bland 03 May '23

03 May '23

1 0

All MPI implementors: Implementation of MPI constants in C and Fortran / MPI meeting May 3, 2023 9am CDT discussion
by Rolf Rabenseifner 02 May '23

02 May '23

Dear implementor of an MPI library, Based on the discussion today in the MPI forum meeting, I have the following urgent question to you: Did you implement all MPI constants that are described in Annex A.1.1 as of type "const int (or unnamed enum)" as "C integer constant expression" (according to the specification of the C language)? If yes, then all is okay and the proposed change of the MPI standard in https://github.com/mpi-forum/mpi-standard/pull/821/files will not require any change of your MPI implementation. If not, then please can you tell which MPI constant(s) MPI_XXX - have you implemented in a way that - it still can be used in an initialization expression, i.e., in a application statement like int x=MPI_XXX; - but it cannot be used as a case-label in a switch statement like switch(MPI_XXX) { case MPI_XXX: printf("XXX\n"); default: ; } - and cannot be used as a fixed array length in a declaration like float x[MPI_XXX]; - and how implemented you such an MPI constant that this problem arises? We'll discuss this again tomorrow May 3, 2023 at the beginning of the MPI forum meeting. See you hopefully at the meeting, and hopefully reporting that you have no problem with the proposal, kind regards Rolf ----- Original Message ----- > From: "Rolf Rabenseifner" <rabenseifner(a)hlrs.de> > To: "Main MPI Forum mailing list" <mpi-forum(a)lists.mpi-forum.org> > Cc: "Puri Bangalore" <pvbangalore(a)ua.edu>, "Claudia Blaas-Schenner" <claudia.blaas-schenner(a)tuwien.ac.at>, "Jeff > Hammond" <jeff.science(a)gmail.com> > Sent: Tuesday, May 2, 2023 2:04:01 PM > Subject: Re: Informal meeting announcement for the May 2023 meeting of the MPI Forum > Der forum memebers, dear Wesley, > > please can we add in the agenda after > > Informal Errata Reading 705 Fortran has only compile-time constants Rolf > > an additional slot > > Errata Discussion 657 All C const int (or unnamed enum) as compile-time > constants Rolf, Jeff H. > > Bestr regards > Rolf > > > ----- Original Message ----- >> From: "Rolf Rabenseifner" <rabenseifner(a)hlrs.de> >> To: "Main MPI Forum mailing list" <mpi-forum(a)lists.mpi-forum.org> >> Cc: "Puri Bangalore" <pvbangalore(a)ua.edu>, "Claudia Blaas-Schenner" >> <claudia.blaas-schenner(a)tuwien.ac.at> >> Sent: Saturday, April 29, 2023 7:38:00 AM >> Subject: Informal meeting announcement for the May 2023 meeting of the MPI Forum > >> Dear forum members, >> >> I would like to make the following announcements for the next MPI Forum Meeting >> (May 2-5, 2023): >> >> - informal reading and discussion >> #705 Errata: Fortran has only compile-time constants Rolf >> Issue https://github.com/mpi-forum/mpi-issues/issues/705 >> PR https://github.com/mpi-forum/mpi-standard/pull/819 >> PDF >> https://github.com/mpi-forum/mpi-standard/files/11358444/mpi41-report_Issue… >> >> This errata should be completely discussed in next (May 2-5, 2023) meeting. >> It is then planned to have an final errata reading plus errata vote at next >> meeting (July 10-13, 2023). >> >> It is a bug since MPI-2.2 because a problem in C was directly mapped to Fortran. >> This mapping was wrong. >> In Fortran, there is no distinction between link-time and compile-time >> constants. >> >> Best regards >> Rolf Rabenseifner > > > -- > Dr. Rolf Rabenseifner . . . . . . . . . .. . . rabenseifner(a)hlrs.de . > High Performance Computing Center (HLRS) . . . ++49(0)711/685-65530 . > University of Stuttgart . . . . . . www.hlrs.de/people/rabenseifner . > Nobelstr. 19, 70569 Stuttgart, Germany -- Dr. Rolf Rabenseifner . . . . . . . . . .. . . rabenseifner(a)hlrs.de . High Performance Computing Center (HLRS) . . . ++49(0)711/685-65530 . University of Stuttgart . . . . . . www.hlrs.de/people/rabenseifner . Nobelstr. 19, 70569 Stuttgart, Germany

1 0

Additional informal meeting announcement for the May 2023 meeting of the MPI Forum
by Rolf Rabenseifner 02 May '23

02 May '23

Dear forum members, I would like to make the following announcements for this MPI Forum Meeting (May 2-5, 2023): - informal reading and discussion #679 Errata: Noncollective (for procedure) and nonpersistent are not defined Rolf Issue https://github.com/mpi-forum/mpi-issues/issues/679 PR https://github.com/mpi-forum/mpi-standard/pull/820 PDF https://github.com/mpi-forum/mpi-standard/files/11372960/mpi41-report_Issue… This errata should be completely discussed in this (May 2-5, 2023) meeting. It is then planned to have an final errata reading plus errata vote at next meeting (July 10-13, 2023). Best regards Rolf Rabenseifner -- Dr. Rolf Rabenseifner . . . . . . . . . .. . . rabenseifner(a)hlrs.de . High Performance Computing Center (HLRS) . . . ++49(0)711/685-65530 . University of Stuttgart . . . . . . www.hlrs.de/people/rabenseifner . Nobelstr. 19, 70569 Stuttgart, Germany

1 0

Re: [Mpi-forum] Informal meeting announcement for the May 2023 meeting of the MPI Forum
by Rolf Rabenseifner 02 May '23

02 May '23

Der forum memebers, dear Wesley, please can we add in the agenda after Informal Errata Reading 705 Fortran has only compile-time constants Rolf an additional slot Errata Discussion 657 All C const int (or unnamed enum) as compile-time constants Rolf, Jeff H. Bestr regards Rolf ----- Original Message ----- > From: "Rolf Rabenseifner" <rabenseifner(a)hlrs.de> > To: "Main MPI Forum mailing list" <mpi-forum(a)lists.mpi-forum.org> > Cc: "Puri Bangalore" <pvbangalore(a)ua.edu>, "Claudia Blaas-Schenner" <claudia.blaas-schenner(a)tuwien.ac.at> > Sent: Saturday, April 29, 2023 7:38:00 AM > Subject: Informal meeting announcement for the May 2023 meeting of the MPI Forum > Dear forum members, > > I would like to make the following announcements for the next MPI Forum Meeting > (May 2-5, 2023): > > - informal reading and discussion > #705 Errata: Fortran has only compile-time constants Rolf > Issue https://github.com/mpi-forum/mpi-issues/issues/705 > PR https://github.com/mpi-forum/mpi-standard/pull/819 > PDF > https://github.com/mpi-forum/mpi-standard/files/11358444/mpi41-report_Issue… > > This errata should be completely discussed in next (May 2-5, 2023) meeting. > It is then planned to have an final errata reading plus errata vote at next > meeting (July 10-13, 2023). > > It is a bug since MPI-2.2 because a problem in C was directly mapped to Fortran. > This mapping was wrong. > In Fortran, there is no distinction between link-time and compile-time > constants. > > Best regards > Rolf Rabenseifner -- Dr. Rolf Rabenseifner . . . . . . . . . .. . . rabenseifner(a)hlrs.de . High Performance Computing Center (HLRS) . . . ++49(0)711/685-65530 . University of Stuttgart . . . . . . www.hlrs.de/people/rabenseifner . Nobelstr. 19, 70569 Stuttgart, Germany

1 0

Informal meeting announcement for the May 2023 meeting of the MPI Forum
by Rolf Rabenseifner 29 Apr '23

29 Apr '23

Dear forum members, I would like to make the following announcements for the next MPI Forum Meeting (May 2-5, 2023): - informal reading and discussion #705 Errata: Fortran has only compile-time constants Rolf Issue https://github.com/mpi-forum/mpi-issues/issues/705 PR https://github.com/mpi-forum/mpi-standard/pull/819 PDF https://github.com/mpi-forum/mpi-standard/files/11358444/mpi41-report_Issue… This errata should be completely discussed in next (May 2-5, 2023) meeting. It is then planned to have an final errata reading plus errata vote at next meeting (July 10-13, 2023). It is a bug since MPI-2.2 because a problem in C was directly mapped to Fortran. This mapping was wrong. In Fortran, there is no distinction between link-time and compile-time constants. Best regards Rolf Rabenseifner -- Dr. Rolf Rabenseifner . . . . . . . . . .. . . rabenseifner(a)hlrs.de . High Performance Computing Center (HLRS) . . . ++49(0)711/685-65530 . University of Stuttgart . . . . . . www.hlrs.de/people/rabenseifner . Nobelstr. 19, 70569 Stuttgart, Germany

1 0

Announcements for the May 2023 MPI Forum voting meeting
by Marc-André Hermanns 18 Apr '23

18 Apr '23

Dear all, On behalf of the Tools WG, I'd like to announce a no-no vote and a 1st vote of Ticket #520 and PR #798: Issue: https://github.com/mpi-forum/mpi-issues/issues/520 PR: https://github.com/mpi-forum/mpi-standard/pull/798 No-No: https://github.com/mpi-forum/mpi-standard/pull/798/commits/b6134e5cec82e298… To clarify the no-no: -------------------- There was a discussion about the combiner on the PR discussion page, after which I added an advice to users today. (see https://github.com/mpi-forum/mpi-standard/pull/798/commits/de3912f608b7a068…) If anyone wants to review the last presentation of this in March check here: [1] https://youtu.be/KsK5LEZqk1A?t=1309 Cheers, Marc-Andre -- Dr. rer. nat. Marc-André Hermanns IT Center Group: High Performance Computing Division: Computational Science and Engineering RWTH Aachen University Seffenter Weg 23 52074 Aachen Phone: +49 241 80-24381 hermanns(a)itc.rwth-aachen.de www.itc.rwth-aachen.de Social Media Kanäle des IT Centers: https://blog.rwth-aachen.de/itc/ https://www.facebook.com/itcenterrwth https://www.linkedin.com/company/itcenterrwth https://twitter.com/ITCenterRWTH https://www.youtube.com/channel/UCKKDJJukeRwO0LP-ac8x8rQ

1 0

Announcement for May 2023 MPI Forum voting meeting
by Holmes, Daniel John 18 Apr '23

18 Apr '23

Hi all, On behalf of the HACC WG, I'd like to announce a no-no vote and a 1st vote for the memory allocation kinds proposal. Issue: https://github.com/mpi-forum/mpi-issues/issues/580 PR: https://github.com/mpi-forum/mpi-standard/pull/714 No-no: https://github.com/mpi-forum/mpi-standard/pull/714/files/34fd740def6ef0890c… (all commits since the reading during the March voting meeting - includes a merge commit, sorry about that) Best wishes, Dan.

1 0