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

Re: [MPIWG Fortran] "small count" variants of RMA functions
by Jeff Hammond 29 Nov '21

29 Nov '21

I created https://github.com/mpi-forum/mpi-issues/issues/528. Normally, we would have a Fortran WG meeting during the quarterly meeting. Is there going to be a Fortran WG session at the December meeting? Jeff On Sat, Nov 27, 2021 at 9:14 PM William Gropp <wgropp(a)illinois.edu> wrote: > I agree with Jeff here. This is a good enhancement; I believe the only > reason that we hadn’t done this before is that we’ve stuck closely to the > original Fortran look-and-feel - which was pre-Fortran 90. We could have > done this earlier, and now that there are explicit interfaces that are only > available in Fortran08, there is no reason not to do this. > > Bill > > William Gropp > Director, NCSA > Thomas M. Siebel Chair in Computer Science > University of Illinois Urbana-Champaign > IEEE-CS President-Elect > > > > > On Nov 25, 2021, at 4:42 AM, Jeff Hammond via mpiwg-fortran < > mpiwg-fortran(a)lists.mpi-forum.org> wrote: > > RMA absolutely did the right thing with MPI_Aint size and displacement > arguments. > > In C, it is no problem to pass 32b integers to these arguments when AINT > is 64b, because C type promotion rules just work. > > In Fortran, I cannot do this, because an integer literal is not compatible > with an AINT argument. I find it tedious to have to declare a variable > just for this, or to explicitly cast with integer(100,MPI_ADDRESS_KIND). > > Since Fortran does polymorphism right and can have subroutine declarations > for both default integer and AINT integer scalar arguments, is there a good > reason not to add the former? > > This proposal applies not to just MPI_Win_allocate but any RMA function > that uses AINT scalar arguments. > > Thanks, > > Jeff > > % mpifort y.F90 > y.F90:20:60: > > 20 | call MPI_Win_allocate(100, 1, MPI_INFO_NULL, comm, XA, WA) > | 1 > Error: There is no specific subroutine for the generic 'mpi_win_allocate' > at (1) > > % cat y.F90 > ! USE mpi_f08 > ! MPI_Win_allocate(size, disp_unit, info, comm, baseptr, win, ierror) > ! USE, INTRINSIC :: ISO_C_BINDING, ONLY : C_PTR > ! INTEGER(KIND=MPI_ADDRESS_KIND), INTENT(IN) :: size > ! INTEGER, INTENT(IN) :: disp_unit > ! TYPE(MPI_Info), INTENT(IN) :: info > ! TYPE(MPI_Comm), INTENT(IN) :: comm > ! TYPE(C_PTR), INTENT(OUT) :: baseptr > ! TYPE(MPI_Win), INTENT(OUT) :: win > ! INTEGER, OPTIONAL, INTENT(OUT) :: ierror > program main > use iso_fortran_env > use mpi_f08 > implicit none > integer(kind=MPI_ADDRESS_KIND) :: as = 100 > type(c_ptr) :: XA > type(MPI_Win) :: WA > TYPE(MPI_Comm) :: comm = MPI_COMM_WORLD > call MPI_Win_allocate(as, 1, MPI_INFO_NULL, comm, XA, WA) > call MPI_Win_allocate(100, 1, MPI_INFO_NULL, comm, XA, WA) > end program main > > % mpicc y.c && echo SUCCESS > SUCCESS > > % cat y.c > #include <mpi.h> > int main(void) > { > MPI_Aint as = 100; > int * XA; > MPI_Win WA; > MPI_Win_allocate(as, 1, MPI_INFO_NULL, MPI_COMM_WORLD, XA, &WA); > MPI_Win_allocate(100, 1, MPI_INFO_NULL, MPI_COMM_WORLD, XA, &WA); > } > > > -- > Jeff Hammond > jeff.science(a)gmail.com > http://jeffhammond.github.io/ > <https://urldefense.com/v3/__http://jeffhammond.github.io/__;!!DZ3fjg!rCl1MJ…> > _______________________________________________ > mpiwg-fortran mailing list > mpiwg-fortran(a)lists.mpi-forum.org > > https://urldefense.com/v3/__https://lists.mpi-forum.org/mailman/listinfo/mp… > > > -- Jeff Hammond jeff.science(a)gmail.com http://jeffhammond.github.io/

1 0

Re: [MPIWG Fortran] "small count" variants of RMA functions
by William Gropp 27 Nov '21

27 Nov '21

I agree with Jeff here. This is a good enhancement; I believe the only reason that we hadn’t done this before is that we’ve stuck closely to the original Fortran look-and-feel - which was pre-Fortran 90. We could have done this earlier, and now that there are explicit interfaces that are only available in Fortran08, there is no reason not to do this. Bill William Gropp Director, NCSA Thomas M. Siebel Chair in Computer Science University of Illinois Urbana-Champaign IEEE-CS President-Elect > On Nov 25, 2021, at 4:42 AM, Jeff Hammond via mpiwg-fortran <mpiwg-fortran(a)lists.mpi-forum.org> wrote: > > RMA absolutely did the right thing with MPI_Aint size and displacement arguments. > > In C, it is no problem to pass 32b integers to these arguments when AINT is 64b, because C type promotion rules just work. > > In Fortran, I cannot do this, because an integer literal is not compatible with an AINT argument. I find it tedious to have to declare a variable just for this, or to explicitly cast with integer(100,MPI_ADDRESS_KIND). > > Since Fortran does polymorphism right and can have subroutine declarations for both default integer and AINT integer scalar arguments, is there a good reason not to add the former? > > This proposal applies not to just MPI_Win_allocate but any RMA function that uses AINT scalar arguments. > > Thanks, > > Jeff > > % mpifort y.F90 > y.F90:20:60: > > 20 | call MPI_Win_allocate(100, 1, MPI_INFO_NULL, comm, XA, WA) > | 1 > Error: There is no specific subroutine for the generic 'mpi_win_allocate' at (1) > > % cat y.F90 > ! USE mpi_f08 > ! MPI_Win_allocate(size, disp_unit, info, comm, baseptr, win, ierror) > ! USE, INTRINSIC :: ISO_C_BINDING, ONLY : C_PTR > ! INTEGER(KIND=MPI_ADDRESS_KIND), INTENT(IN) :: size > ! INTEGER, INTENT(IN) :: disp_unit > ! TYPE(MPI_Info), INTENT(IN) :: info > ! TYPE(MPI_Comm), INTENT(IN) :: comm > ! TYPE(C_PTR), INTENT(OUT) :: baseptr > ! TYPE(MPI_Win), INTENT(OUT) :: win > ! INTEGER, OPTIONAL, INTENT(OUT) :: ierror > program main > use iso_fortran_env > use mpi_f08 > implicit none > integer(kind=MPI_ADDRESS_KIND) :: as = 100 > type(c_ptr) :: XA > type(MPI_Win) :: WA > TYPE(MPI_Comm) :: comm = MPI_COMM_WORLD > call MPI_Win_allocate(as, 1, MPI_INFO_NULL, comm, XA, WA) > call MPI_Win_allocate(100, 1, MPI_INFO_NULL, comm, XA, WA) > end program main > > % mpicc y.c && echo SUCCESS > SUCCESS > > % cat y.c > #include <mpi.h> > int main(void) > { > MPI_Aint as = 100; > int * XA; > MPI_Win WA; > MPI_Win_allocate(as, 1, MPI_INFO_NULL, MPI_COMM_WORLD, XA, &WA); > MPI_Win_allocate(100, 1, MPI_INFO_NULL, MPI_COMM_WORLD, XA, &WA); > } > > > -- > Jeff Hammond > jeff.science(a)gmail.com <mailto:[email protected]> > http://jeffhammond.github.io/ <https://urldefense.com/v3/__http://jeffhammond.github.io/__;!!DZ3fjg!rCl1MJ…>_______________________________________________ > mpiwg-fortran mailing list > mpiwg-fortran(a)lists.mpi-forum.org > https://urldefense.com/v3/__https://lists.mpi-forum.org/mailman/listinfo/mp…

1 0

"small count" variants of RMA functions
by Jeff Hammond 25 Nov '21

25 Nov '21

RMA absolutely did the right thing with MPI_Aint size and displacement arguments. In C, it is no problem to pass 32b integers to these arguments when AINT is 64b, because C type promotion rules just work. In Fortran, I cannot do this, because an integer literal is not compatible with an AINT argument. I find it tedious to have to declare a variable just for this, or to explicitly cast with integer(100,MPI_ADDRESS_KIND). Since Fortran does polymorphism right and can have subroutine declarations for both default integer and AINT integer scalar arguments, is there a good reason not to add the former? This proposal applies not to just MPI_Win_allocate but any RMA function that uses AINT scalar arguments. Thanks, Jeff % mpifort y.F90 y.F90:20:60: 20 | call MPI_Win_allocate(100, 1, MPI_INFO_NULL, comm, XA, WA) | 1 Error: There is no specific subroutine for the generic 'mpi_win_allocate' at (1) % cat y.F90 ! USE mpi_f08 ! MPI_Win_allocate(size, disp_unit, info, comm, baseptr, win, ierror) ! USE, INTRINSIC :: ISO_C_BINDING, ONLY : C_PTR ! INTEGER(KIND=MPI_ADDRESS_KIND), INTENT(IN) :: size ! INTEGER, INTENT(IN) :: disp_unit ! TYPE(MPI_Info), INTENT(IN) :: info ! TYPE(MPI_Comm), INTENT(IN) :: comm ! TYPE(C_PTR), INTENT(OUT) :: baseptr ! TYPE(MPI_Win), INTENT(OUT) :: win ! INTEGER, OPTIONAL, INTENT(OUT) :: ierror program main use iso_fortran_env use mpi_f08 implicit none integer(kind=MPI_ADDRESS_KIND) :: as = 100 type(c_ptr) :: XA type(MPI_Win) :: WA TYPE(MPI_Comm) :: comm = MPI_COMM_WORLD call MPI_Win_allocate(as, 1, MPI_INFO_NULL, comm, XA, WA) call MPI_Win_allocate(100, 1, MPI_INFO_NULL, comm, XA, WA) end program main % mpicc y.c && echo SUCCESS SUCCESS % cat y.c #include <mpi.h> int main(void) { MPI_Aint as = 100; int * XA; MPI_Win WA; MPI_Win_allocate(as, 1, MPI_INFO_NULL, MPI_COMM_WORLD, XA, &WA); MPI_Win_allocate(100, 1, MPI_INFO_NULL, MPI_COMM_WORLD, XA, &WA); } -- Jeff Hammond jeff.science(a)gmail.com http://jeffhammond.github.io/

1 0

Bindings chapter committee review: missed Pythonization functions
by Jeff Squyres (jsquyres) 10 Sep '20

10 Sep '20

Chapter committee -- Can you please review the "BEFORE" and "AFTER" PDFs on PR 276? They're in this comment: https://github.com/mpi-forum/mpi-standard/pull/276#issuecomment-690115458 It turns out that the f2c/c2f functions were missed when Pythonizing. This PR simply Pythonizes them. - The "BEFORE" PR is a build of the mpi-4.x branch at the current HEAD (git ref e6917ee1). - The "AFTER" PR is a build of the mpi-4.x branch with the Pythonization fixes applied (git ref 813afdbd). Bill Gropp says (and I agree) that this is a chapter-committee-level fix. I.e., we review it and just merge it (because we're not changing any semantics). -- Jeff Squyres jsquyres(a)cisco.com

1 0

Re: [MPIWG Fortran] MPI_STATUS_SIZE: Why only in Fortran?
by Rolf Rabenseifner 09 Sep '20

09 Sep '20

> Any thoughts on https://github.com/mpi-forum/mpi-issues/issues/307 (missing > "const" on 2 Status conversion functions)? Yes, any thoughts: To add "const" seems to be correct. Best regards Rolf ----- Original Message ----- > From: "Jeff Squyres" <jsquyres(a)cisco.com> > To: "Rolf Rabenseifner" <rabenseifner(a)hlrs.de> > Cc: "MPI-WG Fortran working group" <mpiwg-fortran(a)lists.mpi-forum.org> > Sent: Wednesday, September 9, 2020 4:14:40 PM > Subject: Re: [MPIWG Fortran] MPI_STATUS_SIZE: Why only in Fortran? > Thanks Rolf! > > Any thoughts on https://github.com/mpi-forum/mpi-issues/issues/307 (missing > "const" on 2 Status conversion functions)? > > > > On Sep 9, 2020, at 2:54 AM, Rolf Rabenseifner > <rabenseifner(a)hlrs.de<mailto:[email protected]>> wrote: > > Dear Jeff, > > Perfect. Thank you for detecting and fixing this bug. > > Best regards > Rolf > > ----- Original Message ----- > From: "Jeff Squyres" <jsquyres(a)cisco.com<mailto:[email protected]>> > To: "Rolf Rabenseifner" <rabenseifner(a)hlrs.de<mailto:[email protected]>> > Cc: "MPI-WG Fortran working group" > <mpiwg-fortran(a)lists.mpi-forum.org<mailto:[email protected]>> > Sent: Wednesday, September 9, 2020 12:13:00 AM > Subject: Re: [MPIWG Fortran] MPI_STATUS_SIZE: Why only in Fortran? > > On Sep 8, 2020, at 4:57 PM, Rolf Rabenseifner > <rabenseifner(a)hlrs.de<mailto:[email protected]>> wrote: > > ... > but you should have > > Status array size and reserved index values (Fortran only) > ... > Fortran status array size and reserved index values (C only) > ... > > Perfect; done -- thanks! > > PRs updated; new PDFs posted to the issue: > > https://github.com/mpi-forum/mpi-issues/issues/306 > > -- > Jeff Squyres > jsquyres(a)cisco.com > > -- > Dr. Rolf Rabenseifner . . . . . . . . . .. email > rabenseifner(a)hlrs.de<mailto:[email protected]> . > 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<http://www.hlrs.de/people/rabenseifner> . > Nobelstr. 19, D-70550 Stuttgart, Germany . . . . (Office: Room 1.307) . > > > -- > Jeff Squyres > jsquyres(a)cisco.com<mailto:[email protected]> -- 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] MPI_STATUS_SIZE: Why only in Fortran?
by Jeff Squyres (jsquyres) 09 Sep '20

09 Sep '20

Thanks Rolf! Any thoughts on https://github.com/mpi-forum/mpi-issues/issues/307 (missing "const" on 2 Status conversion functions)? On Sep 9, 2020, at 2:54 AM, Rolf Rabenseifner <rabenseifner(a)hlrs.de<mailto:[email protected]>> wrote: Dear Jeff, Perfect. Thank you for detecting and fixing this bug. Best regards Rolf ----- Original Message ----- From: "Jeff Squyres" <jsquyres(a)cisco.com<mailto:[email protected]>> To: "Rolf Rabenseifner" <rabenseifner(a)hlrs.de<mailto:[email protected]>> Cc: "MPI-WG Fortran working group" <mpiwg-fortran(a)lists.mpi-forum.org<mailto:[email protected]>> Sent: Wednesday, September 9, 2020 12:13:00 AM Subject: Re: [MPIWG Fortran] MPI_STATUS_SIZE: Why only in Fortran? On Sep 8, 2020, at 4:57 PM, Rolf Rabenseifner <rabenseifner(a)hlrs.de<mailto:[email protected]>> wrote: ... but you should have Status array size and reserved index values (Fortran only) ... Fortran status array size and reserved index values (C only) ... Perfect; done -- thanks! PRs updated; new PDFs posted to the issue: https://github.com/mpi-forum/mpi-issues/issues/306 -- Jeff Squyres jsquyres(a)cisco.com -- Dr. Rolf Rabenseifner . . . . . . . . . .. email rabenseifner(a)hlrs.de<mailto:[email protected]> . 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<http://www.hlrs.de/people/rabenseifner> . Nobelstr. 19, D-70550 Stuttgart, Germany . . . . (Office: Room 1.307) . -- Jeff Squyres jsquyres(a)cisco.com<mailto:[email protected]>

1 0

Re: [MPIWG Fortran] MPI_STATUS_SIZE: Why only in Fortran?
by Rolf Rabenseifner 09 Sep '20

09 Sep '20

Dear Jeff, Perfect. Thank you for detecting and fixing this bug. Best regards Rolf ----- Original Message ----- > From: "Jeff Squyres" <jsquyres(a)cisco.com> > To: "Rolf Rabenseifner" <rabenseifner(a)hlrs.de> > Cc: "MPI-WG Fortran working group" <mpiwg-fortran(a)lists.mpi-forum.org> > Sent: Wednesday, September 9, 2020 12:13:00 AM > Subject: Re: [MPIWG Fortran] MPI_STATUS_SIZE: Why only in Fortran? > On Sep 8, 2020, at 4:57 PM, Rolf Rabenseifner <rabenseifner(a)hlrs.de> wrote: >> >> ... >> but you should have >> >> Status array size and reserved index values (Fortran only) >> ... >> Fortran status array size and reserved index values (C only) >> ... > > Perfect; done -- thanks! > > PRs updated; new PDFs posted to the issue: > > https://github.com/mpi-forum/mpi-issues/issues/306 > > -- > Jeff Squyres > jsquyres(a)cisco.com -- 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] MPI_STATUS_SIZE: Why only in Fortran?
by Jeff Squyres (jsquyres) 08 Sep '20

08 Sep '20

On Sep 8, 2020, at 4:57 PM, Rolf Rabenseifner <rabenseifner(a)hlrs.de> wrote: > > ... > but you should have > > Status array size and reserved index values (Fortran only) > ... > Fortran status array size and reserved index values (C only) > ... Perfect; done -- thanks! PRs updated; new PDFs posted to the issue: https://github.com/mpi-forum/mpi-issues/issues/306 -- Jeff Squyres jsquyres(a)cisco.com

1 0

Re: [MPIWG Fortran] MPI_STATUS_SIZE: Why only in Fortran?
by Rolf Rabenseifner 08 Sep '20

08 Sep '20

Dear Jeff, I commenting your latest pdf together with email below: ----- Original Message ----- > From: "Jeff Squyres" <jsquyres(a)cisco.com> > To: "Rolf Rabenseifner" <rabenseifner(a)hlrs.de> > Cc: "MPI-WG Fortran working group" <mpiwg-fortran(a)lists.mpi-forum.org> > Sent: Tuesday, September 8, 2020 8:46:09 PM > Subject: Re: [MPIWG Fortran] MPI_STATUS_SIZE: Why only in Fortran? > On Sep 8, 2020, at 2:15 PM, Rolf Rabenseifner > <rabenseifner(a)hlrs.de<mailto:[email protected]>> wrote: > > I just updated the header-text in > https://github.com/mpi-forum/mpi-issues/issues/306 > > MPI 3.x: p704:13-xx (still to be done: list with the new C constants after the > list for Fortran) > MPI 4.x: p774:13-xx (still to be done: list with the new C constants after the > list for Fortran) > > Thanks Rolf. I see you also fixed a copy-n-paste error I had for the MPI-3.x > pages; thanks. > > Text in the new C table header may be something like (see also my previous > email, > but I removed the hint to mpif.h and mpi module, because the Fortran constants > must be provided also in the mpi_f08 module) > > Fortran status array size and reserved index values (C only) > (in C only to specify a Fortran status array and indexes into such an array. > The values of Fortran MPI_STATUS_SIZE and C MPI_F_STATUS_SIZE are identical, > whereas the indexes in C are 1 less than in Fortran to reflect that > arrays in Fortran start by default with index 1 whereas in C with index 0) > > I don't think we need this text -- these values are explained in the chapter > text. Plus, we don't have such explanation text in other annex A tables. > > Right? Yes, right. > ---------------------- > C type: int > ---------------------- > MPI_F_STATUS_SIZE > MPI_F_SOURCE > MPI_F_TAG > MPI_F_ERROR > ---------------------- > > Additionally, I would change the Fortran header in the original table > from > Status array size and reserved index values (Fortran only) > to > Status array size and reserved index values (Fortran only) > > These two lines are identical... did you mean to make a change on the 2nd line? sorry for that typo, but not identical to your titles: You have: Status size and reserved index values (Fortran only) ... Status size and reserved index values (C only) ... but you should have Status array size and reserved index values (Fortran only) ... Fortran status array size and reserved index values (C only) ... Reasons: 1) In Fortran, we have two different interfaces (since MPI-3.0): The status array and the TYPE(MPI_Status). Both are statuses, but our constants relate only to the "Status array" 2) For "(Fortran only)", it is clear, that these constants are for the Fortran status, and with 1) above, for the Fortran status array. But for C, I would clearly say that it is nothing for the C MPI_Status or a status array like in MPI_Waitall. Therefore "Fortran status array size". (It is also okay to use "Fortran status array size" for both titles) > Please, do not forget to add also Annex A.1.1 in the list in the changelog. > > Changelog: please keep in mind, that for errata (see older erratas), > we also cite the previous standard, to which the change applies, > i.e., additionally > > ---- > Sections 2.5.4, 18.2.5 and A.1.1 on pages 15, 758 and 771, and > MPI-3.1 Sections 2.5.4, 17.2.5 and A.1.1 on pages 15, 656 and 669. > Defi ne the C constants MPI_F_STATUS_SIZE, MPI_F_SOURCE, MPI_F_TAG, and > MPI_F_ERROR. > ---- I do not understand, why you are doing it other than the rest: 14. Sections 14.3.6, 14.3.7, and 14.3.9 on pages 654, 661, and 689, and MPI-3.0 Sections 14.3.6, 14.3.7, and 14.3.8 on pages 567, 573, and 584. In functions MPI_T_CVAR_GET_INFO, MPI_T_PVAR_GET_INFO, and or 20. Annexes A.2, A.3, and A.4 on pages 795, 821, and 878, and MPI-3.0 Annexes A.2, A.3, and A.4 on pages 685, 707, and 756. The predened callback MPI_CONVERSION_FN_NULL was added or 2. Sections 3.2.2, 5.9.2, 13.5.2 Table 13.2, and Annex A.1.1 on pages 27, 186, 618, and 771, and MPI-2.2 Sections 3.2.2, 5.9.2, 13.5.2 Table 13.2, 16.1.16 Table 16.1, and Annex A.1.1 on pages 27, 164, 433, 472 and 513 This is an MPI-2.2 erratum: New named prede... (Yes, I know, B.3.1 Item 1 is an exception, but hopefully the only one, and for the reason, that Chapters 3-18 are without page number) Therefore please without repeating several times "on page", i.e., please > ---- > Sections 2.5.4, 18.2.5 and A.1.1 on pages 15, 758 and 771, and > MPI-3.1 Sections 2.5.4, 17.2.5 and A.1.1 on pages 15, 656 and 669. > Define the C constants MPI_F_STATUS_SIZE, MPI_F_SOURCE, MPI_F_TAG, and > MPI_F_ERROR. > ---- or a bit longer ---- Sections 2.5.4, 18.2.5 and Annex A.1.1 on pages 15, 758 and 771, and MPI-3.1 Sections 2.5.4, 17.2.5 and Annex A.1.1 on pages 15, 656 and 669. Define the C constants MPI_F_STATUS_SIZE, MPI_F_SOURCE, MPI_F_TAG, and MPI_F_ERROR. ---- Please do not forget the plural s in MPI-3.1 Section**s** > Done everything except the title line of both tables in Annex A. Best regards Rolf > The 4.0 PDF is attached; I'll hold off on the 3.x PDF and updating both PRs > until you let me know what you wanted done with those table headings. > > -- > Jeff Squyres > jsquyres(a)cisco.com<mailto:[email protected]> -- 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] MPI_STATUS_SIZE: Why only in Fortran?
by Jeff Squyres (jsquyres) 08 Sep '20

08 Sep '20

On Sep 8, 2020, at 2:46 PM, Jeff Squyres (jsquyres) via mpiwg-fortran <mpiwg-fortran(a)lists.mpi-forum.org> wrote: > > The 4.0 PDF is attached; I'll hold off on the 3.x PDF and updating both PRs until you let me know what you wanted done with those table headings. The PDF I attached was garbage; sorry about that. Here's one showing all the changes except changes to the table names in Annex A. -- Jeff Squyres jsquyres(a)cisco.com

1 0