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

Re: [MPIWG Fortran] Dec mtg: MPI 4: deprecate SIZEOF and mpif.h
by Balaji, Pavan 11 Nov '14

11 Nov '14

> On Nov 11, 2014, at 10:36 AM, Bill Long <longb(a)cray.com> wrote: > > On Nov 11, 2014, at 8:49 AM, Balaji, Pavan <balaji(a)anl.gov> wrote: > >> >> With one minor addition — new functionality will not have deprecated equivalents (at least that’s the model we used with C++). So everything that gets added in MPI-4 will be “use mpi” or “use mpi_f08” only, if this passes. > > OK. That’s what I was hoping. Did you mean “use mpi” *and* “use mpi_f08” only? I would not expect those to be diverging, at least yet. Right. I meant the user will need to use “use mpi” or “use mpi_f08” for MPI-4 functionality. -- Pavan Balaji ✉️ http://www.mcs.anl.gov/~balaji

1 0

Re: [MPIWG Fortran] Dec mtg: MPI 4: deprecate SIZEOF and mpif.h
by Bill Long 11 Nov '14

11 Nov '14

On Nov 11, 2014, at 8:49 AM, Balaji, Pavan <balaji(a)anl.gov> wrote: > > With one minor addition — new functionality will not have deprecated equivalents (at least that’s the model we used with C++). So everything that gets added in MPI-4 will be “use mpi” or “use mpi_f08” only, if this passes. OK. That’s what I was hoping. Did you mean “use mpi” *and* “use mpi_f08” only? I would not expect those to be diverging, at least yet. Cheers, Bill > > — Pavan > >> On Nov 11, 2014, at 8:09 AM, William Gropp <wgropp(a)illinois.edu> wrote: >> >> Deprecate in MPI uses the same definition that the Fortran standards have used - discouraged from use and a candidate for deletion in a future standard. Thus, until formally deleted, it must be implemented and appear in mpif.h (as mpif.h is now defined). >> >> Bill >> >> On Nov 11, 2014, at 8:01 AM, Bill Long <longb(a)cray.com> wrote: >> >>> Seems reasonable to me. >>> >>> Are there plans for a Webex meeting for the Fortran working group before the December MPI meeting in San Jose? This is a “vacation challenged” time of the year - I’m scheduled to be in the office only 3 days between December 5 and 31. >>> >>> How does MPI define “deprecate”? For example, would any new feature/function be excluded from mpif.h? Personally, I think that would be a good idea - it simplifies maintenance of the distribution and emphasizes that mpif.h is for legacy use only. But I can imagine other opinions. >>> >>> Cheers, >>> Bill >>> >>> >>> >>> On Nov 11, 2014, at 6:22 AM, Jeff Squyres (jsquyres) <jsquyres(a)cisco.com> wrote: >>> >>>> I won't have time to do any prep in detail until after SC and the subsequent US thanksgiving holiday, but are these 2 topics that we want to discuss in December? >>>> >>>> Sent from my phone. No type good. >>>> _______________________________________________ >>>> 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 >> >> _______________________________________________ >> mpiwg-fortran mailing list >> mpiwg-fortran(a)lists.mpi-forum.org >> http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran > > -- > Pavan Balaji ✉️ > http://www.mcs.anl.gov/~balaji > > _______________________________________________ > 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] Dec mtg: MPI 4: deprecate SIZEOF and mpif.h
by Jeff Squyres (jsquyres) 11 Nov '14

11 Nov '14

Yes, we should probably have a webex to discuss first (this is not the firs time discussing these issues, but a cache-refresh would be a good idea). We span Europe-to-California, so I'm thinking we really only have one or two possible time slots a day. Here's a doodle for a few days in the week of Dec 1: http://doodle.com/965sgk95nrza8r8q On Nov 11, 2014, at 9:01 AM, Bill Long <longb(a)cray.com> wrote: > Seems reasonable to me. > > Are there plans for a Webex meeting for the Fortran working group before the December MPI meeting in San Jose? This is a “vacation challenged” time of the year - I’m scheduled to be in the office only 3 days between December 5 and 31. > > How does MPI define “deprecate”? For example, would any new feature/function be excluded from mpif.h? Personally, I think that would be a good idea - it simplifies maintenance of the distribution and emphasizes that mpif.h is for legacy use only. But I can imagine other opinions. > > Cheers, > Bill > > > > On Nov 11, 2014, at 6:22 AM, Jeff Squyres (jsquyres) <jsquyres(a)cisco.com> wrote: > >> I won't have time to do any prep in detail until after SC and the subsequent US thanksgiving holiday, but are these 2 topics that we want to discuss in December? >> >> Sent from my phone. No type good. >> _______________________________________________ >> 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

Re: [MPIWG Fortran] Dec mtg: MPI 4: deprecate SIZEOF and mpif.h
by Balaji, Pavan 11 Nov '14

11 Nov '14

With one minor addition — new functionality will not have deprecated equivalents (at least that’s the model we used with C++). So everything that gets added in MPI-4 will be “use mpi” or “use mpi_f08” only, if this passes. — Pavan > On Nov 11, 2014, at 8:09 AM, William Gropp <wgropp(a)illinois.edu> wrote: > > Deprecate in MPI uses the same definition that the Fortran standards have used - discouraged from use and a candidate for deletion in a future standard. Thus, until formally deleted, it must be implemented and appear in mpif.h (as mpif.h is now defined). > > Bill > > On Nov 11, 2014, at 8:01 AM, Bill Long <longb(a)cray.com> wrote: > >> Seems reasonable to me. >> >> Are there plans for a Webex meeting for the Fortran working group before the December MPI meeting in San Jose? This is a “vacation challenged” time of the year - I’m scheduled to be in the office only 3 days between December 5 and 31. >> >> How does MPI define “deprecate”? For example, would any new feature/function be excluded from mpif.h? Personally, I think that would be a good idea - it simplifies maintenance of the distribution and emphasizes that mpif.h is for legacy use only. But I can imagine other opinions. >> >> Cheers, >> Bill >> >> >> >> On Nov 11, 2014, at 6:22 AM, Jeff Squyres (jsquyres) <jsquyres(a)cisco.com> wrote: >> >>> I won't have time to do any prep in detail until after SC and the subsequent US thanksgiving holiday, but are these 2 topics that we want to discuss in December? >>> >>> Sent from my phone. No type good. >>> _______________________________________________ >>> 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 > > _______________________________________________ > mpiwg-fortran mailing list > mpiwg-fortran(a)lists.mpi-forum.org > http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran -- Pavan Balaji ✉️ http://www.mcs.anl.gov/~balaji

1 0

Re: [MPIWG Fortran] Dec mtg: MPI 4: deprecate SIZEOF and mpif.h
by William Gropp 11 Nov '14

11 Nov '14

Deprecate in MPI uses the same definition that the Fortran standards have used - discouraged from use and a candidate for deletion in a future standard. Thus, until formally deleted, it must be implemented and appear in mpif.h (as mpif.h is now defined). Bill On Nov 11, 2014, at 8:01 AM, Bill Long <longb(a)cray.com> wrote: > Seems reasonable to me. > > Are there plans for a Webex meeting for the Fortran working group before the December MPI meeting in San Jose? This is a “vacation challenged” time of the year - I’m scheduled to be in the office only 3 days between December 5 and 31. > > How does MPI define “deprecate”? For example, would any new feature/function be excluded from mpif.h? Personally, I think that would be a good idea - it simplifies maintenance of the distribution and emphasizes that mpif.h is for legacy use only. But I can imagine other opinions. > > Cheers, > Bill > > > > On Nov 11, 2014, at 6:22 AM, Jeff Squyres (jsquyres) <jsquyres(a)cisco.com> wrote: > >> I won't have time to do any prep in detail until after SC and the subsequent US thanksgiving holiday, but are these 2 topics that we want to discuss in December? >> >> Sent from my phone. No type good. >> _______________________________________________ >> 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

1 0

Re: [MPIWG Fortran] Dec mtg: MPI 4: deprecate SIZEOF and mpif.h
by Bill Long 11 Nov '14

11 Nov '14

Seems reasonable to me. Are there plans for a Webex meeting for the Fortran working group before the December MPI meeting in San Jose? This is a “vacation challenged” time of the year - I’m scheduled to be in the office only 3 days between December 5 and 31. How does MPI define “deprecate”? For example, would any new feature/function be excluded from mpif.h? Personally, I think that would be a good idea - it simplifies maintenance of the distribution and emphasizes that mpif.h is for legacy use only. But I can imagine other opinions. Cheers, Bill On Nov 11, 2014, at 6:22 AM, Jeff Squyres (jsquyres) <jsquyres(a)cisco.com> wrote: > I won't have time to do any prep in detail until after SC and the subsequent US thanksgiving holiday, but are these 2 topics that we want to discuss in December? > > Sent from my phone. No type good. > _______________________________________________ > 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] Dec mtg: MPI 4: deprecate SIZEOF and mpif.h
by Jeff Hammond 11 Nov '14

11 Nov '14

Yes. Sent from my iPhone > On Nov 11, 2014, at 1:22 PM, "Jeff Squyres (jsquyres)" <jsquyres(a)cisco.com> wrote: > > I won't have time to do any prep in detail until after SC and the subsequent US thanksgiving holiday, but are these 2 topics that we want to discuss in December? > > Sent from my phone. No type good. > _______________________________________________ > mpiwg-fortran mailing list > mpiwg-fortran(a)lists.mpi-forum.org > http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran

1 0

Dec mtg: MPI 4: deprecate SIZEOF and mpif.h
by Jeff Squyres (jsquyres) 11 Nov '14

11 Nov '14

I won't have time to do any prep in detail until after SC and the subsequent US thanksgiving holiday, but are these 2 topics that we want to discuss in December? Sent from my phone. No type good.

1 0

Fortran Tickets #440 - #446
by Rolf Rabenseifner 13 Aug '14

13 Aug '14

Dear Fortran WG members, as proposed in the previous Forum Meeting, I split #427 into ist independent parts. The following tickets ##41, #422, #444, #445 are pure Fortran errata tickets and mainly level 0 Quality therefore I would propose that - we should check whether the proposed text is okay - and then we may pass them with a chapter committee vote if they are treated by the chapter committee as ticket 0. http://meetings.mpi-forum.org/MPI_3.1_main_page.php currently lists as chapter committee: Jeff Squyres, Jeff Hammond, Rolf Rabenseifner Craig and all, who also wants to help in this chapter committee? Okay? In the other tickets #440,, #443, #446, other chapters are involved and therefore, the forum should vote. List of all these tickets: #440 Fortran cross-reference correction (ticket 0 / errata) https://svn.mpi-forum.org/trac/mpi-forum-web/ticket/440 #441 Missing text for Fortran MPI_SUBARRAYS_SUPPORTED equals .FALSE. (errata) https://svn.mpi-forum.org/trac/mpi-forum-web/ticket/441 #442 Fortran "vector subscipts" and MPI_BOTTOM (ticket 0 / errata) https://svn.mpi-forum.org/trac/mpi-forum-web/ticket/442 #443 Fortran MPI_BOTTOM not for initialization or assignment (ticket 0 / errata) https://svn.mpi-forum.org/trac/mpi-forum-web/ticket/443 #444 Fortran and Persistent Requests (ticket 0 / errata) https://svn.mpi-forum.org/trac/mpi-forum-web/ticket/444 #445 Fortran and Permament Data Movement: "All" nonblocking (ticket 0 / errata) https://svn.mpi-forum.org/trac/mpi-forum-web/ticket/445 #446 Fortran cross-reference update (ticket-0/errata) https://svn.mpi-forum.org/trac/mpi-forum-web/ticket/446 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] BIND(C) attribute of MPI callback functions
by Junchao Zhang 02 Jul '14

02 Jul '14

On Wed, Jul 2, 2014 at 7:05 AM, Bill Long <longb(a)cray.com> wrote: > > On Jul 2, 2014, at 2:11 AM, Rolf Rabenseifner <rabenseifner(a)hlrs.de> > wrote: > > > Bill, > > > > The reason for removal of BIND(C) was simple: > > Four callbacks contain LOGICAL arguments > > and we learnt that LOGICAL and BIND(C) does not work together. > > Therefore the errata is correct. > > Agreed. > > > > > I hope you find a solution for storing the callback pointer > > in a C structure and to bring it back to Fortran. > > I expect that calling the Fortran callbacks > > in a portable way may require Fortran code > > that calls the callback. > > For compilers that support the TS, there should be no problem. As noted by > Junchao, Cray and Gfortran did not have a problem. The IBM compiler > appears to have overlooked the TS change. A bug report to IBM should > resolve the issue. The fix is trivial - just disabling an error message > Have sent two bug reports regarding F08 to IBM. One is the BIND(C). The other is that XLF-15.1 does not support storage_size(). > Cheers, > Bill > > > > > > Best regards > > Rolf > > > > > > ----- Original Message ----- > >> From: "Bill Long" <longb(a)cray.com> > >> To: "MPI-WG Fortran working group" <mpiwg-fortran(a)lists.mpi-forum.org> > >> Sent: Tuesday, July 1, 2014 9:06:05 PM > >> Subject: Re: [MPIWG Fortran] BIND(C) attribute of MPI callback functions > >> > >> > >> On Jul 1, 2014, at 2:00 PM, Junchao Zhang <jczhang(a)mcs.anl.gov> > >> wrote: > >> > >>> Hello, > >>> Errata for MPI-3.0 removed the BIND(C) attribute of MPI callback > >>> functions. But in an implementation, to pass the Fortran > >>> procedure to the backend C, I need to get its C function pointer > >>> with c_funloc, as the following code shows. When I compile it > >>> with IBM XLF 15.1, it complains with such an error "1516-203 (S) > >>> The argument to the intrinsic procedure C_FUNLOC must be a > >>> procedure with the BIND(C) attribute." In my experiments, gcc > >>> and Cray ftn are fine with it. Looking at > >>> https://gcc.gnu.org/onlinedocs/gfortran/C_005fFUNLOC.html, I > >>> find c_funloc indeed requires an interoperable function > >>> argument. Any comments? > >> > >> This requirement on the argument of C_FUNLOC was removed by TS 29113, > >> subclause 8.1 “Removed restrictions on ISO_C_BINDING module > >> procedures”. > >> > >> Cheers, > >> Bill > >> > >> > >> > >>> > >>> subroutine MPI_Comm_create_errhandler_f08(comm_errhandler_fn, > >>> errhandler, ierror) > >>> use, intrinsic :: iso_c_binding, only : c_funloc, c_int, > >>> c_funptr > >>> use :: mpi_f08, only : MPI_Errhandler, > >>> MPI_Comm_errhandler_function > >>> use :: mpi_c_interface, only : c_Errhandler, > >>> MPIR_Comm_create_errhandler_c > >>> > >>> implicit none > >>> > >>> procedure(MPI_Comm_errhandler_function) :: comm_errhandler_fn > >>> type(MPI_Errhandler), intent(out) :: errhandler > >>> integer, optional, intent(out) :: ierror > >>> > >>> type(c_funptr) :: comm_errhandler_fn_c > >>> > >>> comm_errhandler_fn_c = c_funloc(comm_errhandler_fn) !! xlf > >>> issues an error > >>> ierror_c = MPIR_Comm_create_errhandler_c(comm_errhandler_fn_c, > >>> errhandler%MPI_VAL) > >>> ... > >>> end subroutine MPI_Comm_create_errhandler_f08 > >>> > >>> --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 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 > >> > > > > -- > > 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 > > 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 >

1 0