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
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" <[email protected]> To: [email protected] 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 [email protected] http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran
-- Dr. Rolf Rabenseifner . . . . . . . . . .. email [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 Nobelstr. 19, D-70550 Stuttgart, Germany . . . . (Office: Room 1.307)
...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 <[email protected]> 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" <[email protected]> To: [email protected] 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 [email protected] http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran
-- Dr. Rolf Rabenseifner . . . . . . . . . .. email [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 Nobelstr. 19, D-70550 Stuttgart, Germany . . . . (Office: Room 1.307) _______________________________________________ mpiwg-fortran mailing list [email protected] http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran
-- Jeff Squyres [email protected] For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
On Feb 5, 2014, at 12:02 PM, Jeff Squyres (jsquyres) <[email protected]> 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 <[email protected]> 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" <[email protected]> To: [email protected] 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 [email protected] http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran
-- Dr. Rolf Rabenseifner . . . . . . . . . .. email [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 Nobelstr. 19, D-70550 Stuttgart, Germany . . . . (Office: Room 1.307) _______________________________________________ mpiwg-fortran mailing list [email protected] http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran
-- Jeff Squyres [email protected] For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
_______________________________________________ mpiwg-fortran mailing list [email protected] http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran
Bill Long [email protected] 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
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 [email protected] On Feb 5, 2014, at 10:11 AM, Bill Long wrote:
On Feb 5, 2014, at 12:02 PM, Jeff Squyres (jsquyres) <[email protected]> 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 <[email protected]> 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" <[email protected]> To: [email protected] 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 [email protected] http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran
-- Dr. Rolf Rabenseifner . . . . . . . . . .. email [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 Nobelstr. 19, D-70550 Stuttgart, Germany . . . . (Office: Room 1.307) _______________________________________________ mpiwg-fortran mailing list [email protected] http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran
-- Jeff Squyres [email protected] For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
_______________________________________________ mpiwg-fortran mailing list [email protected] http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran
Bill Long [email protected] 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 [email protected] http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran
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 <[email protected]> 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 [email protected]
On Feb 5, 2014, at 10:11 AM, Bill Long wrote:
On Feb 5, 2014, at 12:02 PM, Jeff Squyres (jsquyres) <[email protected]> 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 <[email protected]> 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" <[email protected]> To: [email protected] 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 [email protected] http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran
-- Dr. Rolf Rabenseifner . . . . . . . . . .. email [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 Nobelstr. 19, D-70550 Stuttgart, Germany . . . . (Office: Room 1.307) _______________________________________________ mpiwg-fortran mailing list [email protected] http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran
-- Jeff Squyres [email protected] For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
_______________________________________________ mpiwg-fortran mailing list [email protected] http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran
Bill Long [email protected] 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 [email protected] http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran
_______________________________________________ mpiwg-fortran mailing list [email protected] http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran
-- Jeff Squyres [email protected] For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
Could you give some background/details on the "new" meaning ASYNCHRONOUS? I thought Intel ifort had support? Thanks, -Dan On Wed, Feb 05, 2014 at 07:19:16PM +0000, Jeff Squyres (jsquyres) wrote:
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 <[email protected]> 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 [email protected]
On Feb 5, 2014, at 10:11 AM, Bill Long wrote:
On Feb 5, 2014, at 12:02 PM, Jeff Squyres (jsquyres) <[email protected]> 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 <[email protected]> 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" <[email protected]> To: [email protected] 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 [email protected] http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran
-- Dr. Rolf Rabenseifner . . . . . . . . . .. email [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 Nobelstr. 19, D-70550 Stuttgart, Germany . . . . (Office: Room 1.307) _______________________________________________ mpiwg-fortran mailing list [email protected] http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran
-- Jeff Squyres [email protected] For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
_______________________________________________ mpiwg-fortran mailing list [email protected] http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran
Bill Long [email protected] 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 [email protected] http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran
_______________________________________________ mpiwg-fortran mailing list [email protected] http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran
-- Jeff Squyres [email protected] For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
_______________________________________________ mpiwg-fortran mailing list [email protected] http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran
Before the TS, the concept of ASYNCHRONOUS applied only to I/O. Asynchronous use of a variable started with a READ or WRITE statement and completed with a WAIT statement. The TS extended that idea to “asynchronous communication” that could also include the effects of non-Fortran procedures (specifically like MPI_Ixxx routines). Cheers, Bill On Feb 5, 2014, at 2:57 PM, Dan Pou <[email protected]> wrote:
Could you give some background/details on the "new" meaning ASYNCHRONOUS? I thought Intel ifort had support?
Thanks, -Dan
On Wed, Feb 05, 2014 at 07:19:16PM +0000, Jeff Squyres (jsquyres) wrote:
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 <[email protected]> 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 [email protected]
On Feb 5, 2014, at 10:11 AM, Bill Long wrote:
On Feb 5, 2014, at 12:02 PM, Jeff Squyres (jsquyres) <[email protected]> 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 <[email protected]> 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" <[email protected]> To: [email protected] 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 [email protected] http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran
-- Dr. Rolf Rabenseifner . . . . . . . . . .. email [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 Nobelstr. 19, D-70550 Stuttgart, Germany . . . . (Office: Room 1.307) _______________________________________________ mpiwg-fortran mailing list [email protected] http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran
-- Jeff Squyres [email protected] For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
_______________________________________________ mpiwg-fortran mailing list [email protected] http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran
Bill Long [email protected] 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 [email protected] http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran
_______________________________________________ mpiwg-fortran mailing list [email protected] http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran
-- Jeff Squyres [email protected] For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
_______________________________________________ mpiwg-fortran mailing list [email protected] http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran
mpiwg-fortran mailing list [email protected] http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran
Bill Long [email protected] 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
On Feb 5, 2014, at 12:26 PM, Craig Rasmussen <[email protected]> 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.
Using IGNORE_TKR misses a big part of the mpi_f08 module.
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.
Right. I’ve been using gfortran 4.9 for some time to compile mpi_f08 and associated modules. But not execute. The Cray compiler does support the C descriptors, but gfortran is not quite there yet. I think the gfortran plan is to switch all of their dope vectors to the C descriptor format, which is a much bigger change. Cheers, Bill
Craig Rasmussen CAS Scientific Programmer [email protected]
On Feb 5, 2014, at 10:11 AM, Bill Long wrote:
On Feb 5, 2014, at 12:02 PM, Jeff Squyres (jsquyres) <[email protected]> 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 <[email protected]> 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" <[email protected]> To: [email protected] 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 [email protected] http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran
-- Dr. Rolf Rabenseifner . . . . . . . . . .. email [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 Nobelstr. 19, D-70550 Stuttgart, Germany . . . . (Office: Room 1.307) _______________________________________________ mpiwg-fortran mailing list [email protected] http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran
-- Jeff Squyres [email protected] For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
_______________________________________________ mpiwg-fortran mailing list [email protected] http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran
Bill Long [email protected] 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 [email protected] http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran
_______________________________________________ mpiwg-fortran mailing list [email protected] http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran
Bill Long [email protected] 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
On Feb 5, 2014, at 2:20 PM, Bill Long <[email protected]> wrote:
Using IGNORE_TKR misses a big part of the mpi_f08 module.
It missed descriptors, but that's only one feature. I think the unique handle types and all the other features are still fairly enormous and useful additions for the average MPI Fortran developer. -- Jeff Squyres [email protected] For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
Thanks, Jeff. Definitely, I will have a look at OMPI mpi_f08. --Junchao Zhang On Wed, Feb 5, 2014 at 12:02 PM, Jeff Squyres (jsquyres) <[email protected]
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).
On Feb 5, 2014, at 12:46 PM, Rolf Rabenseifner <[email protected]> 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" <[email protected]> To: [email protected] 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 [email protected] http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran
-- Dr. Rolf Rabenseifner . . . . . . . . . .. email [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 Nobelstr. 19, D-70550 Stuttgart, Germany . . . . (Office: Room 1.307) _______________________________________________ mpiwg-fortran mailing list [email protected] http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran
-- Jeff Squyres [email protected] For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
_______________________________________________ mpiwg-fortran mailing list [email protected] http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran
If you care, OMPI v1.7.4 was (literally) just released; you can look at the official 1.7.4 tarball. On Feb 5, 2014, at 5:47 PM, Junchao Zhang <[email protected]> wrote:
Thanks, Jeff. Definitely, I will have a look at OMPI mpi_f08.
--Junchao Zhang
On Wed, Feb 5, 2014 at 12:02 PM, Jeff Squyres (jsquyres) <[email protected]> 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).
On Feb 5, 2014, at 12:46 PM, Rolf Rabenseifner <[email protected]> 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" <[email protected]> To: [email protected] 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 [email protected] http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran
-- Dr. Rolf Rabenseifner . . . . . . . . . .. email [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 Nobelstr. 19, D-70550 Stuttgart, Germany . . . . (Office: Room 1.307) _______________________________________________ mpiwg-fortran mailing list [email protected] http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran
-- Jeff Squyres [email protected] For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
_______________________________________________ mpiwg-fortran mailing list [email protected] http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran
_______________________________________________ mpiwg-fortran mailing list [email protected] http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran
-- Jeff Squyres [email protected] For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
When I clicked v1.7.4, I got http://www.open-mpi.org/404.php -- OMG, 404 not found :) But never mind, I use SVN to check out OMPI. --Junchao Zhang On Wed, Feb 5, 2014 at 4:50 PM, Jeff Squyres (jsquyres) <[email protected]>wrote:
If you care, OMPI v1.7.4 was (literally) just released; you can look at the official 1.7.4 tarball.
On Feb 5, 2014, at 5:47 PM, Junchao Zhang <[email protected]> wrote:
Thanks, Jeff. Definitely, I will have a look at OMPI mpi_f08.
--Junchao Zhang
On Wed, Feb 5, 2014 at 12:02 PM, Jeff Squyres (jsquyres) < [email protected]> 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).
On Feb 5, 2014, at 12:46 PM, Rolf Rabenseifner <[email protected]> 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" <[email protected]> To: [email protected] 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 [email protected] http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran
-- Dr. Rolf Rabenseifner . . . . . . . . . .. email [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 Nobelstr. 19, D-70550 Stuttgart, Germany . . . . (Office: Room 1.307) _______________________________________________ mpiwg-fortran mailing list [email protected] http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran
-- Jeff Squyres [email protected] For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
_______________________________________________ mpiwg-fortran mailing list [email protected] http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran
_______________________________________________ mpiwg-fortran mailing list [email protected] http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran
-- Jeff Squyres [email protected] For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
_______________________________________________ mpiwg-fortran mailing list [email protected] http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran
Works for me...? http://www.open-mpi.org/software/ompi/v1.7/ On Feb 5, 2014, at 6:04 PM, Junchao Zhang <[email protected]> wrote:
When I clicked v1.7.4, I got http://www.open-mpi.org/404.php -- OMG, 404 not found :) But never mind, I use SVN to check out OMPI.
--Junchao Zhang
On Wed, Feb 5, 2014 at 4:50 PM, Jeff Squyres (jsquyres) <[email protected]> wrote: If you care, OMPI v1.7.4 was (literally) just released; you can look at the official 1.7.4 tarball.
On Feb 5, 2014, at 5:47 PM, Junchao Zhang <[email protected]> wrote:
Thanks, Jeff. Definitely, I will have a look at OMPI mpi_f08.
--Junchao Zhang
On Wed, Feb 5, 2014 at 12:02 PM, Jeff Squyres (jsquyres) <[email protected]> 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).
On Feb 5, 2014, at 12:46 PM, Rolf Rabenseifner <[email protected]> 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" <[email protected]> To: [email protected] 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 [email protected] http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran
-- Dr. Rolf Rabenseifner . . . . . . . . . .. email [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 Nobelstr. 19, D-70550 Stuttgart, Germany . . . . (Office: Room 1.307) _______________________________________________ mpiwg-fortran mailing list [email protected] http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran
-- Jeff Squyres [email protected] For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
_______________________________________________ mpiwg-fortran mailing list [email protected] http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran
_______________________________________________ mpiwg-fortran mailing list [email protected] http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran
-- Jeff Squyres [email protected] For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
_______________________________________________ mpiwg-fortran mailing list [email protected] http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran
_______________________________________________ mpiwg-fortran mailing list [email protected] http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran
-- Jeff Squyres [email protected] For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
Click <Read more> under <Open MPI v1.7.4 released>, which is on the right of page http://www.open-mpi.org/ --Junchao Zhang On Wed, Feb 5, 2014 at 5:56 PM, Jeff Squyres (jsquyres) <[email protected]>wrote:
Works for me...?
http://www.open-mpi.org/software/ompi/v1.7/
On Feb 5, 2014, at 6:04 PM, Junchao Zhang <[email protected]> wrote:
When I clicked v1.7.4, I got http://www.open-mpi.org/404.php -- OMG, 404 not found :) But never mind, I use SVN to check out OMPI.
--Junchao Zhang
On Wed, Feb 5, 2014 at 4:50 PM, Jeff Squyres (jsquyres) < [email protected]> wrote: If you care, OMPI v1.7.4 was (literally) just released; you can look at the official 1.7.4 tarball.
On Feb 5, 2014, at 5:47 PM, Junchao Zhang <[email protected]> wrote:
Thanks, Jeff. Definitely, I will have a look at OMPI mpi_f08.
--Junchao Zhang
On Wed, Feb 5, 2014 at 12:02 PM, Jeff Squyres (jsquyres) < [email protected]> 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).
On Feb 5, 2014, at 12:46 PM, Rolf Rabenseifner <[email protected]> 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" <[email protected]> To: [email protected] 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 [email protected] http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran
-- Dr. Rolf Rabenseifner . . . . . . . . . .. email [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 Nobelstr. 19, D-70550 Stuttgart, Germany . . . . (Office: Room 1.307) _______________________________________________ mpiwg-fortran mailing list [email protected] http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran
-- Jeff Squyres [email protected] For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
_______________________________________________ mpiwg-fortran mailing list [email protected] http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran
_______________________________________________ mpiwg-fortran mailing list [email protected] http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran
-- Jeff Squyres [email protected] For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
_______________________________________________ mpiwg-fortran mailing list [email protected] http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran
_______________________________________________ mpiwg-fortran mailing list [email protected] http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran
-- Jeff Squyres [email protected] For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
_______________________________________________ mpiwg-fortran mailing list [email protected] http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran
Hi, Jeff, How can I get a MPI-3 spec with the errata merged? So that I can easily found which BIND(C)'s are left. Thanks. --Junchao Zhang On Wed, Feb 5, 2014 at 12:02 PM, Jeff Squyres (jsquyres) <[email protected]
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).
On Feb 5, 2014, at 12:46 PM, Rolf Rabenseifner <[email protected]> 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" <[email protected]> To: [email protected] 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 [email protected] http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran
-- Dr. Rolf Rabenseifner . . . . . . . . . .. email [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 Nobelstr. 19, D-70550 Stuttgart, Germany . . . . (Office: Room 1.307) _______________________________________________ mpiwg-fortran mailing list [email protected] http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran
-- Jeff Squyres [email protected] For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
_______________________________________________ mpiwg-fortran mailing list [email protected] http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran
You can't yet, unfortunately. The overall MPI-3.1 tree was not ready in SVN until the last Forum meeting. I hope to have at least a draft ready in the MPI-3.1 tree by the SJC Forum meeting. On Feb 6, 2014, at 11:55 PM, Junchao Zhang <[email protected]> wrote:
Hi, Jeff, How can I get a MPI-3 spec with the errata merged? So that I can easily found which BIND(C)'s are left. Thanks.
--Junchao Zhang
On Wed, Feb 5, 2014 at 12:02 PM, Jeff Squyres (jsquyres) <[email protected]> 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).
On Feb 5, 2014, at 12:46 PM, Rolf Rabenseifner <[email protected]> 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" <[email protected]> To: [email protected] 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 [email protected] http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran
-- Dr. Rolf Rabenseifner . . . . . . . . . .. email [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 Nobelstr. 19, D-70550 Stuttgart, Germany . . . . (Office: Room 1.307) _______________________________________________ mpiwg-fortran mailing list [email protected] http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran
-- Jeff Squyres [email protected] For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
_______________________________________________ mpiwg-fortran mailing list [email protected] http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran
_______________________________________________ mpiwg-fortran mailing list [email protected] http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran
-- Jeff Squyres [email protected] For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
On Feb 5, 2014, at 11:46 AM, Rolf Rabenseifner <[email protected]> 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" <[email protected]> To: [email protected] 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 [email protected] http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran
-- Dr. Rolf Rabenseifner . . . . . . . . . .. email [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 Nobelstr. 19, D-70550 Stuttgart, Germany . . . . (Office: Room 1.307) _______________________________________________ mpiwg-fortran mailing list [email protected] http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran
Bill Long [email protected] 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
Fixed; thanks. On Feb 5, 2014, at 12:42 PM, Junchao Zhang <[email protected]> wrote:
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 [email protected] http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran
-- Jeff Squyres [email protected] For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
participants (7)
-
Bill Long -
Craig Rasmussen -
Dan Pou -
Jeff Squyres (jsquyres) -
Junchao Zhang -
Rolf Rabenseifner -
Tobias Burnus