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

Re: [MPIWG Fortran] What is BIND(C)?
by Jeff Squyres (jsquyres) 05 Feb '14

05 Feb '14

Not AFAIK. But we use the pragmas for ignore TKR. I guess I could have been more clear: OMPI will build the mpi_f08 module if it finds "enough" F08 characteristics supported in the Fortran compiler, but it may strip away some features if the compiler doesn't support them. For example, with current ifort, you'll basically get everything except the "new" meaning of asynchronous and descriptors (we'll use ignore TKR pragmas instead) -- so the SUBARRAYS value will be .false. The new gfortran functionality will be in the upcoming gcc/gfortran v4.9 (which isn't released yet). On Feb 5, 2014, at 1:26 PM, Craig Rasmussen <rasmus(a)cas.uoregon.edu> wrote: > I don't think Intel does yet (but actually I will check). Intel supports the IGNORE_TKR and so Jeff is using the Intel compiler with compiler directives to support MPI-3. > > Surprisingly, the latest gfortran supports type(*) and dimension(..) partially, as in it will act like IGNORE_TKR (I think) but actually doesn't pass the new C descriptors yet. > > Craig Rasmussen > CAS Scientific Programmer > rasmus(a)cas.uoregon.edu > > > > > On Feb 5, 2014, at 10:11 AM, Bill Long wrote: > >> >> On Feb 5, 2014, at 12:02 PM, Jeff Squyres (jsquyres) <jsquyres(a)cisco.com> wrote: >> >>> ...but be careful. We didn't get rid of *all* the BIND(C)'s. >>> >>> If you care, the most recent OMPI 1.7 and SVN trunk nightly tarballs have the most correct/most-bug-fixed implementation of the mpi_f08 module available (soon to be released as OMPI 1.7.4). You'll need to build with a non-gfortran compiler to get the mpi_f08 module built (e.g., the Intel fortran compiler). >> >> Really? Intel supports type(*) and dimension(..) now? >> >> Cheers, >> Bill >> >>> >>> >>> >>> On Feb 5, 2014, at 12:46 PM, Rolf Rabenseifner <rabenseifner(a)hlrs.de> wrote: >>> >>>> Hello, >>>> >>>> The BIND(C) was removed in the latest errata, >>>> see >>>> http://www.mpi-forum.org/docs/docs.html >>>> and >>>> http://www.mpi-forum.org/docs/mpi-3.0/errata-30.pdf >>>> page 1 lines 21-27 >>>> >>>> Best regards >>>> Rolf Rabenseifner >>>> >>>> ----- Original Message ----- >>>>> From: "Junchao Zhang" <jczhang(a)mcs.anl.gov> >>>>> To: mpiwg-fortran(a)lists.mpi-forum.org >>>>> Sent: Wednesday, February 5, 2014 6:42:28 PM >>>>> Subject: [MPIWG Fortran] What is BIND(C)? >>>>> >>>>> >>>>> >>>>> Hello, >>>>> I have a naive question. MPI3 has Fortran binding in forms like >>>>> this: >>>>> >>>>> >>>>> MPI_Send(buf, count, datatype, dest, tag, comm, ierror) BIND(C) >>>>> TYPE(*), DIMENSION(..), INTENT(IN) :: buf >>>>> INTEGER, INTENT(IN) :: count, dest, tag >>>>> ... >>>>> >>>>> >>>>> So how to interpret BIND(C) here? Is it to say this interface is >>>>> interoperable with C? But I find the interface arguments are not >>>>> interoperable, e.g., INTEGER, instead of C_INT. >>>>> 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 >>>> >>>> -- >>>> 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 >>> >>> >>> -- >>> 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 >> >> >> _______________________________________________ >> 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 -- 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] What is BIND(C)?
by Craig Rasmussen 05 Feb '14

05 Feb '14

I don't think Intel does yet (but actually I will check). Intel supports the IGNORE_TKR and so Jeff is using the Intel compiler with compiler directives to support MPI-3. Surprisingly, the latest gfortran supports type(*) and dimension(..) partially, as in it will act like IGNORE_TKR (I think) but actually doesn't pass the new C descriptors yet. Craig Rasmussen CAS Scientific Programmer rasmus(a)cas.uoregon.edu On Feb 5, 2014, at 10:11 AM, Bill Long wrote: > > On Feb 5, 2014, at 12:02 PM, Jeff Squyres (jsquyres) <jsquyres(a)cisco.com> wrote: > >> ...but be careful. We didn't get rid of *all* the BIND(C)'s. >> >> If you care, the most recent OMPI 1.7 and SVN trunk nightly tarballs have the most correct/most-bug-fixed implementation of the mpi_f08 module available (soon to be released as OMPI 1.7.4). You'll need to build with a non-gfortran compiler to get the mpi_f08 module built (e.g., the Intel fortran compiler). > > Really? Intel supports type(*) and dimension(..) now? > > Cheers, > Bill > >> >> >> >> On Feb 5, 2014, at 12:46 PM, Rolf Rabenseifner <rabenseifner(a)hlrs.de> wrote: >> >>> Hello, >>> >>> The BIND(C) was removed in the latest errata, >>> see >>> http://www.mpi-forum.org/docs/docs.html >>> and >>> http://www.mpi-forum.org/docs/mpi-3.0/errata-30.pdf >>> page 1 lines 21-27 >>> >>> Best regards >>> Rolf Rabenseifner >>> >>> ----- Original Message ----- >>>> From: "Junchao Zhang" <jczhang(a)mcs.anl.gov> >>>> To: mpiwg-fortran(a)lists.mpi-forum.org >>>> Sent: Wednesday, February 5, 2014 6:42:28 PM >>>> Subject: [MPIWG Fortran] What is BIND(C)? >>>> >>>> >>>> >>>> Hello, >>>> I have a naive question. MPI3 has Fortran binding in forms like >>>> this: >>>> >>>> >>>> MPI_Send(buf, count, datatype, dest, tag, comm, ierror) BIND(C) >>>> TYPE(*), DIMENSION(..), INTENT(IN) :: buf >>>> INTEGER, INTENT(IN) :: count, dest, tag >>>> ... >>>> >>>> >>>> So how to interpret BIND(C) here? Is it to say this interface is >>>> interoperable with C? But I find the interface arguments are not >>>> interoperable, e.g., INTEGER, instead of C_INT. >>>> 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 >>> >>> -- >>> 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 >> >> >> -- >> 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 > > > _______________________________________________ > 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] What is BIND(C)?
by Bill Long 05 Feb '14

05 Feb '14

On Feb 5, 2014, at 12:02 PM, Jeff Squyres (jsquyres) <jsquyres(a)cisco.com> wrote: > ...but be careful. We didn't get rid of *all* the BIND(C)'s. > > If you care, the most recent OMPI 1.7 and SVN trunk nightly tarballs have the most correct/most-bug-fixed implementation of the mpi_f08 module available (soon to be released as OMPI 1.7.4). You'll need to build with a non-gfortran compiler to get the mpi_f08 module built (e.g., the Intel fortran compiler). Really? Intel supports type(*) and dimension(..) now? Cheers, Bill > > > > On Feb 5, 2014, at 12:46 PM, Rolf Rabenseifner <rabenseifner(a)hlrs.de> wrote: > >> Hello, >> >> The BIND(C) was removed in the latest errata, >> see >> http://www.mpi-forum.org/docs/docs.html >> and >> http://www.mpi-forum.org/docs/mpi-3.0/errata-30.pdf >> page 1 lines 21-27 >> >> Best regards >> Rolf Rabenseifner >> >> ----- Original Message ----- >>> From: "Junchao Zhang" <jczhang(a)mcs.anl.gov> >>> To: mpiwg-fortran(a)lists.mpi-forum.org >>> Sent: Wednesday, February 5, 2014 6:42:28 PM >>> Subject: [MPIWG Fortran] What is BIND(C)? >>> >>> >>> >>> Hello, >>> I have a naive question. MPI3 has Fortran binding in forms like >>> this: >>> >>> >>> MPI_Send(buf, count, datatype, dest, tag, comm, ierror) BIND(C) >>> TYPE(*), DIMENSION(..), INTENT(IN) :: buf >>> INTEGER, INTENT(IN) :: count, dest, tag >>> ... >>> >>> >>> So how to interpret BIND(C) here? Is it to say this interface is >>> interoperable with C? But I find the interface arguments are not >>> interoperable, e.g., INTEGER, instead of C_INT. >>> 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 >> >> -- >> 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 > > > -- > 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] What is BIND(C)?
by Bill Long 05 Feb '14

05 Feb '14

On Feb 5, 2014, at 11:46 AM, Rolf Rabenseifner <rabenseifner(a)hlrs.de> wrote: > Hello, > > The BIND(C) was removed in the latest errata, Correct. The place for BIND(C) is in the interface for the underlying C routine. At that level, the arguments are interoperable. Cheers, Bill > see > http://www.mpi-forum.org/docs/docs.html > and > http://www.mpi-forum.org/docs/mpi-3.0/errata-30.pdf > page 1 lines 21-27 > > Best regards > Rolf Rabenseifner > > ----- Original Message ----- >> From: "Junchao Zhang" <jczhang(a)mcs.anl.gov> >> To: mpiwg-fortran(a)lists.mpi-forum.org >> Sent: Wednesday, February 5, 2014 6:42:28 PM >> Subject: [MPIWG Fortran] What is BIND(C)? >> >> >> >> Hello, >> I have a naive question. MPI3 has Fortran binding in forms like >> this: >> >> >> MPI_Send(buf, count, datatype, dest, tag, comm, ierror) BIND(C) >> TYPE(*), DIMENSION(..), INTENT(IN) :: buf >> INTEGER, INTENT(IN) :: count, dest, tag >> ... >> >> >> So how to interpret BIND(C) here? Is it to say this interface is >> interoperable with C? But I find the interface arguments are not >> interoperable, e.g., INTEGER, instead of C_INT. >> 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 > > -- > 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

1 0

Re: [MPIWG Fortran] What is BIND(C)?
by Jeff Squyres (jsquyres) 05 Feb '14

05 Feb '14

...but be careful. We didn't get rid of *all* the BIND(C)'s. If you care, the most recent OMPI 1.7 and SVN trunk nightly tarballs have the most correct/most-bug-fixed implementation of the mpi_f08 module available (soon to be released as OMPI 1.7.4). You'll need to build with a non-gfortran compiler to get the mpi_f08 module built (e.g., the Intel fortran compiler). On Feb 5, 2014, at 12:46 PM, Rolf Rabenseifner <rabenseifner(a)hlrs.de> wrote: > Hello, > > The BIND(C) was removed in the latest errata, > see > http://www.mpi-forum.org/docs/docs.html > and > http://www.mpi-forum.org/docs/mpi-3.0/errata-30.pdf > page 1 lines 21-27 > > Best regards > Rolf Rabenseifner > > ----- Original Message ----- >> From: "Junchao Zhang" <jczhang(a)mcs.anl.gov> >> To: mpiwg-fortran(a)lists.mpi-forum.org >> Sent: Wednesday, February 5, 2014 6:42:28 PM >> Subject: [MPIWG Fortran] What is BIND(C)? >> >> >> >> Hello, >> I have a naive question. MPI3 has Fortran binding in forms like >> this: >> >> >> MPI_Send(buf, count, datatype, dest, tag, comm, ierror) BIND(C) >> TYPE(*), DIMENSION(..), INTENT(IN) :: buf >> INTEGER, INTENT(IN) :: count, dest, tag >> ... >> >> >> So how to interpret BIND(C) here? Is it to say this interface is >> interoperable with C? But I find the interface arguments are not >> interoperable, e.g., INTEGER, instead of C_INT. >> 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 > > -- > 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 -- 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] What is BIND(C)?
by Rolf Rabenseifner 05 Feb '14

05 Feb '14

Hello, The BIND(C) was removed in the latest errata, see http://www.mpi-forum.org/docs/docs.html and http://www.mpi-forum.org/docs/mpi-3.0/errata-30.pdf page 1 lines 21-27 Best regards Rolf Rabenseifner ----- Original Message ----- > From: "Junchao Zhang" <jczhang(a)mcs.anl.gov> > To: mpiwg-fortran(a)lists.mpi-forum.org > Sent: Wednesday, February 5, 2014 6:42:28 PM > Subject: [MPIWG Fortran] What is BIND(C)? > > > > Hello, > I have a naive question. MPI3 has Fortran binding in forms like > this: > > > MPI_Send(buf, count, datatype, dest, tag, comm, ierror) BIND(C) > TYPE(*), DIMENSION(..), INTENT(IN) :: buf > INTEGER, INTENT(IN) :: count, dest, tag > ... > > > So how to interpret BIND(C) here? Is it to say this interface is > interoperable with C? But I find the interface arguments are not > interoperable, e.g., INTEGER, instead of C_INT. > 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 -- 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

What is BIND(C)?
by Junchao Zhang 05 Feb '14

05 Feb '14

Hello, I have a naive question. MPI3 has Fortran binding in forms like this: MPI_Send(buf, count, datatype, dest, tag, comm, ierror) BIND(C) TYPE(*), DIMENSION(..), INTENT(IN) :: buf INTEGER, INTENT(IN) :: count, dest, tag ... So how to interpret BIND(C) here? Is it to say this interface is interoperable with C? But I find the interface arguments are not interoperable, e.g., INTEGER, instead of C_INT. Thank you. --Junchao Zhang

1 0

Re: [MPIWG Fortran] MPI-3 ticket 349: Fortran question
by Jim Dinan 04 Feb '14

04 Feb '14

Sorry it has taken me so long to respond to this -- Dave, thanks so much for the detailed example! I added this to the ticket to make sure we don't lose it. ~Jim. On Thu, Jan 2, 2014 at 11:36 AM, Dave Goodell (dgoodell) <dgoodell(a)cisco.com > wrote: > On Dec 24, 2013, at 11:36 AM, Jim Dinan <james.dinan(a)gmail.com> wrote: > > > Given that MPI_Aint will be at least the same size as ptrdiff_t, do we > > actually have a problem with subtracting MPI_Aints to find pointer diffs? > > It seems like this may actually be ok. > > There's still a problem. I don't think that ptrdiff_t has anything to do > with it since that normally only comes into play when you subtract two > _pointers_, not two integers acting sort of like pointers. > > As an example, take a look at this little test program. It subtracts two > plausible addresses from the middle of the address space but underflows the > signed arithmetic anyway. When I compile this with '-ftrapv' under clang > then I get a core dump when executing this program. > > ----8<---- > #include <stdio.h> > #include <limits.h> > > typedef long long MPI_Aint; > > int main(int argc, char **argv) > { > MPI_Aint a = LLONG_MIN; /* 0x8000000000000000LL */ > MPI_Aint b = 0x7ffffffffffffffcLL; > MPI_Aint c = a - b; /* expect 0x4LL if signed overflow were defined */ > printf("a=%#llx b=%#llx c=%#llx\n", a, b, c); > return 0; > } > ----8<---- > > The overflow occurs because "(a - b)" is really "(-9223372036854775808 - > 9223372036854775804)" in signed integer arithmetic. Note that most > implementations will give you the expected value if you don't set > '-ftrapv', but that's *undefined behavior* according to the C standard and > should not be relied upon (see http://www.airs.com/blog/archives/120) > > This is all just the C side of things. I have no idea whether Fortran > integer overflow is defined. > > -Dave > >

1 0

Re: [MPIWG Fortran] Draft chapter for discussion today
by Jeff Squyres (jsquyres) 04 Feb '14

04 Feb '14

Ticket #408 has been created. I replaced all "ticketWG" instances in the final PDF with "ticket408" and uploaded it. We're good to go. As a sidenote: I'm also going to introduce a ticket to move some chapters around. I notice that 3.0-and-soon-to-be-3.1 has the following chapters: 14. Tool Support 15. Deprecated Interfaces 16. Removed Interfaces 17. Language Bindings It seems to me that Deprecated/Removed should be the last 2 chapters before the appendix; i.e., we should move 17 up before 15 (for MPI-4 -- no need to do this for 3.1). Like this: 14. Tool Support 15. Language Bindings 16. Deprecated Interfaces 17. Removed Interfaces A minor change, but it appeals to my aesthetic. :-) On Feb 4, 2014, at 8:32 AM, "Jeff Squyres (jsquyres)" <jsquyres(a)cisco.com> wrote: > I thought the wording in those 2 locations was already fine, but I don't have a strong opinion, so I'll change it. > > > On Feb 4, 2014, at 7:49 AM, Rolf Rabenseifner <rabenseifner(a)hlrs.de> wrote: > >> Jeff, >> >> Only a minor detail in your attached pdf on p19:24 and p683:20: >> Please, can you interchange the sequence: first mpi then deprecated mpif.h >> All other locations are already done. >> >> Best regards >> Rolf >> >> ----- Original Message ----- >>> From: "Jeff Squyres (jsquyres)" <jsquyres(a)cisco.com> >>> To: "MPI-WG Fortran working group" <mpiwg-fortran(a)lists.mpi-forum.org> >>> Sent: Tuesday, February 4, 2014 12:39:17 PM >>> Subject: Re: [MPIWG Fortran] Draft chapter for discussion today >>> >>> >>> >>> >>> Ok, here's a final copy -- see the new section in the Deprecated >>> Interfaces chapter. >>> >>> I'll make a ticket for this, and send it to the mpi-forum list so >>> that we're well-ahead of the T-2 week notice. >>> >>> >>> >>> >>> >>> >>> On Feb 4, 2014, at 3:31 AM, Rolf Rabenseifner <rabenseifner(a)hlrs.de> >>> wrote: >>> >>>> Perfect. >>>> >>>> ----- Original Message ----- >>>>> From: "Jeff Squyres (jsquyres)" <jsquyres(a)cisco.com> >>>>> To: "MPI-WG Fortran working group" >>>>> <mpiwg-fortran(a)lists.mpi-forum.org> >>>>> Sent: Tuesday, February 4, 2014 12:10:03 AM >>>>> Subject: Re: [MPIWG Fortran] Draft chapter for discussion today >>>>> >>>>> On Feb 3, 2014, at 4:02 AM, Rolf Rabenseifner >>>>> <rabenseifner(a)hlrs.de> >>>>> wrote: >>>>> >>>>>>> If Chapter 15 is to be renamed, I would agree that 17.1.4 should >>>>>>> move. But I'm not sure this is a good idea. >>>>>> >>>>>> We used already in MPI-2.2 the "Chapter 15. Deprecated Functions" >>>>>> in the general way "Deprecated Interfaces" when we added >>>>>> the total C++ bindings to this chapter, i.e. all C++ constants, >>>>>> functions, ,... . >>>>> >>>>> This is a good point. >>>>> >>>>>> To make the life easy, we should rename Chapter 15 into >>>>>> "Chapter 15. Deprecated Interfaces". This would be consistent to >>>>>> "Chapter 16. Removed Interfaces". >>>>>> The normal text (i.e., text outside of Chap. 15+16) should >>>>>> include as few deprecated features as possible. >>>>> >>>>> I see in MPI-2.2 chapter 15 a very brief blurb about how the C++ >>>>> bindings are deprecated. We then also put "deprecated" next to >>>>> every binding throughout the text (and a few other select places, >>>>> IIRC). >>>>> >>>>> So for mpif.h/MPI-4, I propose a compromise: >>>>> >>>>> 1. Rename chapter 15 as you suggest. >>>>> >>>>> 2. Put a brief blurb in 15 saying that mpif.h is deprecated, >>>>> similar >>>>> to what we did for C++ in MPI-2.2. I.e., do not move 17.1.4 or >>>>> other giant blocks of text to chapter 15. >>>>> >>>>> -- >>>>> 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 >>>>> >>>> >>>> -- >>>> 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 >>> >>> >>> -- >>> 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 >> >> -- >> 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 > > > -- > 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 -- 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] Draft chapter for discussion today
by Jeff Squyres (jsquyres) 04 Feb '14

04 Feb '14

I thought the wording in those 2 locations was already fine, but I don't have a strong opinion, so I'll change it. On Feb 4, 2014, at 7:49 AM, Rolf Rabenseifner <rabenseifner(a)hlrs.de> wrote: > Jeff, > > Only a minor detail in your attached pdf on p19:24 and p683:20: > Please, can you interchange the sequence: first mpi then deprecated mpif.h > All other locations are already done. > > Best regards > Rolf > > ----- Original Message ----- >> From: "Jeff Squyres (jsquyres)" <jsquyres(a)cisco.com> >> To: "MPI-WG Fortran working group" <mpiwg-fortran(a)lists.mpi-forum.org> >> Sent: Tuesday, February 4, 2014 12:39:17 PM >> Subject: Re: [MPIWG Fortran] Draft chapter for discussion today >> >> >> >> >> Ok, here's a final copy -- see the new section in the Deprecated >> Interfaces chapter. >> >> I'll make a ticket for this, and send it to the mpi-forum list so >> that we're well-ahead of the T-2 week notice. >> >> >> >> >> >> >> On Feb 4, 2014, at 3:31 AM, Rolf Rabenseifner <rabenseifner(a)hlrs.de> >> wrote: >> >>> Perfect. >>> >>> ----- Original Message ----- >>>> From: "Jeff Squyres (jsquyres)" <jsquyres(a)cisco.com> >>>> To: "MPI-WG Fortran working group" >>>> <mpiwg-fortran(a)lists.mpi-forum.org> >>>> Sent: Tuesday, February 4, 2014 12:10:03 AM >>>> Subject: Re: [MPIWG Fortran] Draft chapter for discussion today >>>> >>>> On Feb 3, 2014, at 4:02 AM, Rolf Rabenseifner >>>> <rabenseifner(a)hlrs.de> >>>> wrote: >>>> >>>>>> If Chapter 15 is to be renamed, I would agree that 17.1.4 should >>>>>> move. But I'm not sure this is a good idea. >>>>> >>>>> We used already in MPI-2.2 the "Chapter 15. Deprecated Functions" >>>>> in the general way "Deprecated Interfaces" when we added >>>>> the total C++ bindings to this chapter, i.e. all C++ constants, >>>>> functions, ,... . >>>> >>>> This is a good point. >>>> >>>>> To make the life easy, we should rename Chapter 15 into >>>>> "Chapter 15. Deprecated Interfaces". This would be consistent to >>>>> "Chapter 16. Removed Interfaces". >>>>> The normal text (i.e., text outside of Chap. 15+16) should >>>>> include as few deprecated features as possible. >>>> >>>> I see in MPI-2.2 chapter 15 a very brief blurb about how the C++ >>>> bindings are deprecated. We then also put "deprecated" next to >>>> every binding throughout the text (and a few other select places, >>>> IIRC). >>>> >>>> So for mpif.h/MPI-4, I propose a compromise: >>>> >>>> 1. Rename chapter 15 as you suggest. >>>> >>>> 2. Put a brief blurb in 15 saying that mpif.h is deprecated, >>>> similar >>>> to what we did for C++ in MPI-2.2. I.e., do not move 17.1.4 or >>>> other giant blocks of text to chapter 15. >>>> >>>> -- >>>> 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 >>>> >>> >>> -- >>> 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 >> >> >> -- >> 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 > > -- > 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 -- Jeff Squyres jsquyres(a)cisco.com For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/

1 0