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

Re: [MPIWG Fortran] Deprecated functions in F08
by Rolf Rabenseifner 27 Feb '14

27 Feb '14

Dear Junchao Zhang, MPI-3.0 page 598 lines 1-5 state: Compliant MPI-3 implementations providing a Fortran interface must provide one or both of the following: - The USE mpi_f08 Fortran support method. - The USE mpi and INCLUDE 'mpif.h' Fortran support methods. This is the main rule. 17.1.2 "Fortran Support Through the mpi_f08 Module", > Line 12, Page 599 of MPI 3.0 reads: Only one Fortran > interface is defined for functions that are deprecated as > of MPI-3.0. This interface must be provided as an explicit > interface according to the rules defined for the mpi module, > see Section 17.1.3 on page 601. If an MPI library provider decides that he/she provides only the mpi_f08 module, then the words "according to the rules for the mpi module" mean that these deprecated routines are not provided. There was never the intent that the mpi module must come together with mpi_f08 through a back-door with the wording on p599:12-14. Best regards Rolf ----- Original Message ----- > From: "Junchao Zhang" <jczhang(a)mcs.anl.gov> > To: "MPI-WG Fortran working group" <mpiwg-fortran(a)lists.mpi-forum.org> > Sent: Wednesday, February 26, 2014 4:58:28 PM > Subject: [MPIWG Fortran] Deprecated functions in F08 > > Line 12, Page 599 of MPI 3.0 reads: Only one Fortran interface is > defined for functions that are deprecated as of > MPI-3.0. This interface must be provided as an explicit interface > according to > the rules defined for the mpi module, see Section 17.1.3 on page 601. > > Can I put it as: In a mpi_f08 module, if one uses the deprecated > functions, he should get compilation errors, since the Standard does > not define interfaces for them. He can either upgrade them to new > functions, or uses mpi module instead. > Does it also mean the mpi module is mandatory partner for F08 > binding, since it says, "This interface must be provided ..." > > Thanks. > > --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

Deprecated functions in F08
by Junchao Zhang 26 Feb '14

26 Feb '14

Line 12, Page 599 of MPI 3.0 reads: Only one Fortran interface is defined for functions that are deprecated as of MPI-3.0. This interface must be provided as an explicit interface according to the rules defined for the mpi module, see Section 17.1.3 on page 601. Can I put it as: In a mpi_f08 module, if one uses the deprecated functions, he should get compilation errors, since the Standard does not define interfaces for them. He can either upgrade them to new functions, or uses mpi module instead. Does it also mean the mpi module is mandatory partner for F08 binding, since it says, "This interface must be provided ..." Thanks. --Junchao Zhang

1 0

Re: [MPIWG Fortran] Question on Fortran binding errata
by Rolf Rabenseifner 13 Feb '14

13 Feb '14

Jeff, Yes, you are right. We use the method that the specific procedure name differs from the MPI routine name in - the errata, new Sect. 17.1.5, see Table 1.1, (no real overloading within a given module), - and in the definition of all memory allocating routines MPI_ALLOC_MEM, MPI_WIN_ALLOCATE, MPI_WIN_ALLOCATE_SHARED... and the memory-pointer providing routine MPI_WIN_SHARED_QUERY (real overloading within each module). 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: Wednesday, February 12, 2014 11:28:24 PM > Subject: Re: [MPIWG Fortran] Question on Fortran binding errata > > There's deep Fortran voodoo here. :-) > > The short version is that Fortran overloads functions sorta similar > to C++, but with a different mechanism. So you can: > > call foo(integer_value) > and > call foo(floating_value) > > and have it call 2 different back-end subroutines, just like C++. > The way this is done in fortran is with interfaces. Something like > this: > > interface foo > subroutine foo_integer(a) > integer :: a > end subroutine foo_integer > > subroutine foo_real(a) > real :: a > end subroutine foo_real > end interface foo > > So you've declared one interface -- foo -- but with 2 different > subroutine implementations -- foo_integer and foo_real (note that > the above is a *declaration*, it is not an *implementation*). You > can then go implement foo_integer and foo_real, and the compiler > will take care of figuring out which actual subroutine to invoke > when an application invokes "call foo(x)". > > The "specific procedure name" refers to the "inner" names (e.g., > foo_integer and foo_real, in this example). As Craig said, because > of the MPI profiling layer, we mandated specific forms of specific > procedure names. Otherwise, 3rd party tools wouldn't be able to > intercept calls via the MPI profiling mechanism (because the > actual/back-end symbol for any given procedure would be unknown / > implementation-specific). > > Make sense? > > > On Feb 12, 2014, at 5:02 PM, Craig Rasmussen <rasmus(a)cas.uoregon.edu> > wrote: > > > We realized after working on MPI-3 for awhile that we would need > > Fortran wrappers and couldn't really call C routines directly. > > One of the reasons is that the MPI C routines return a function > > value and most of the Fortran bindings are subroutines without a > > return value. The language you refer to is a requirement on the > > implementer as to what the name of the wrapper routine is. > > > > For example, if the user calls MPI_Isend and uses the MPI_F08 > > module, then the wrapper routine shall (must) be called > > MPI_Isend_f08. Another requirement we have placed on implementors > > is that the wrapper name can't be hidden within a module so that > > Fortran module name mangling won't be done for the MPI_Isend_f08 > > routine. > > > > Craig Rasmussen > > CAS Scientific Programmer > > rasmus(a)cas.uoregon.edu > > > > > > > > > > On Feb 12, 2014, at 1:28 PM, Junchao Zhang wrote: > > > >> Hello, > >> On page 10, line 38 of the errata, > >> http://www.mpi-forum.org/docs/mpi-3.0/errata-30.pdf, it reads > >> > >> A Fortran call to an MPI routine shall result in a call to a > >> procedure with one of the > >> specific procedure names and calling conventions, as described in > >> Table 1.1 on page 11. > >> Case is not significant in the names. > >> > >> Can someone explain it a little more, especially, what is the > >> meaning of "specific procedure names"? > >> 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 > > > > _______________________________________________ > > 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)

1 0

Re: [MPIWG Fortran] Question on Fortran binding errata
by Junchao Zhang 12 Feb '14

12 Feb '14

Got it. It is very helpful. I now understand that we do overloading in MPI since Fortran standards have different supports for choice buffers. Application programmers only care interface names; tool developers need to know inner names to intercept. So MPI spec defines both. --Junchao Zhang On Wed, Feb 12, 2014 at 4:28 PM, Jeff Squyres (jsquyres) <jsquyres(a)cisco.com > wrote: > There's deep Fortran voodoo here. :-) > > The short version is that Fortran overloads functions sorta similar to > C++, but with a different mechanism. So you can: > > call foo(integer_value) > and > call foo(floating_value) > > and have it call 2 different back-end subroutines, just like C++. The way > this is done in fortran is with interfaces. Something like this: > > interface foo > subroutine foo_integer(a) > integer :: a > end subroutine foo_integer > > subroutine foo_real(a) > real :: a > end subroutine foo_real > end interface foo > > So you've declared one interface -- foo -- but with 2 different subroutine > implementations -- foo_integer and foo_real (note that the above is a > *declaration*, it is not an *implementation*). You can then go implement > foo_integer and foo_real, and the compiler will take care of figuring out > which actual subroutine to invoke when an application invokes "call foo(x)". > > The "specific procedure name" refers to the "inner" names (e.g., > foo_integer and foo_real, in this example). As Craig said, because of the > MPI profiling layer, we mandated specific forms of specific procedure > names. Otherwise, 3rd party tools wouldn't be able to intercept calls via > the MPI profiling mechanism (because the actual/back-end symbol for any > given procedure would be unknown / implementation-specific). > > Make sense? > > > On Feb 12, 2014, at 5:02 PM, Craig Rasmussen <rasmus(a)cas.uoregon.edu> > wrote: > > > We realized after working on MPI-3 for awhile that we would need Fortran > wrappers and couldn't really call C routines directly. One of the reasons > is that the MPI C routines return a function value and most of the Fortran > bindings are subroutines without a return value. The language you refer to > is a requirement on the implementer as to what the name of the wrapper > routine is. > > > > For example, if the user calls MPI_Isend and uses the MPI_F08 module, > then the wrapper routine shall (must) be called MPI_Isend_f08. Another > requirement we have placed on implementors is that the wrapper name can't > be hidden within a module so that Fortran module name mangling won't be > done for the MPI_Isend_f08 routine. > > > > Craig Rasmussen > > CAS Scientific Programmer > > rasmus(a)cas.uoregon.edu > > > > > > > > > > On Feb 12, 2014, at 1:28 PM, Junchao Zhang wrote: > > > >> Hello, > >> On page 10, line 38 of the errata, > http://www.mpi-forum.org/docs/mpi-3.0/errata-30.pdf, it reads > >> > >> A Fortran call to an MPI routine shall result in a call to a procedure > with one of the > >> specific procedure names and calling conventions, as described in Table > 1.1 on page 11. > >> Case is not significant in the names. > >> > >> Can someone explain it a little more, especially, what is the > meaning of "specific procedure names"? > >> 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 > > > > _______________________________________________ > > 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 >

1 0

Re: [MPIWG Fortran] Question on Fortran binding errata
by Jeff Squyres (jsquyres) 12 Feb '14

12 Feb '14

There's deep Fortran voodoo here. :-) The short version is that Fortran overloads functions sorta similar to C++, but with a different mechanism. So you can: call foo(integer_value) and call foo(floating_value) and have it call 2 different back-end subroutines, just like C++. The way this is done in fortran is with interfaces. Something like this: interface foo subroutine foo_integer(a) integer :: a end subroutine foo_integer subroutine foo_real(a) real :: a end subroutine foo_real end interface foo So you've declared one interface -- foo -- but with 2 different subroutine implementations -- foo_integer and foo_real (note that the above is a *declaration*, it is not an *implementation*). You can then go implement foo_integer and foo_real, and the compiler will take care of figuring out which actual subroutine to invoke when an application invokes "call foo(x)". The "specific procedure name" refers to the "inner" names (e.g., foo_integer and foo_real, in this example). As Craig said, because of the MPI profiling layer, we mandated specific forms of specific procedure names. Otherwise, 3rd party tools wouldn't be able to intercept calls via the MPI profiling mechanism (because the actual/back-end symbol for any given procedure would be unknown / implementation-specific). Make sense? On Feb 12, 2014, at 5:02 PM, Craig Rasmussen <rasmus(a)cas.uoregon.edu> wrote: > We realized after working on MPI-3 for awhile that we would need Fortran wrappers and couldn't really call C routines directly. One of the reasons is that the MPI C routines return a function value and most of the Fortran bindings are subroutines without a return value. The language you refer to is a requirement on the implementer as to what the name of the wrapper routine is. > > For example, if the user calls MPI_Isend and uses the MPI_F08 module, then the wrapper routine shall (must) be called MPI_Isend_f08. Another requirement we have placed on implementors is that the wrapper name can't be hidden within a module so that Fortran module name mangling won't be done for the MPI_Isend_f08 routine. > > Craig Rasmussen > CAS Scientific Programmer > rasmus(a)cas.uoregon.edu > > > > > On Feb 12, 2014, at 1:28 PM, Junchao Zhang wrote: > >> Hello, >> On page 10, line 38 of the errata, http://www.mpi-forum.org/docs/mpi-3.0/errata-30.pdf, it reads >> >> A Fortran call to an MPI routine shall result in a call to a procedure with one of the >> specific procedure names and calling conventions, as described in Table 1.1 on page 11. >> Case is not significant in the names. >> >> Can someone explain it a little more, especially, what is the meaning of "specific procedure names"? >> 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 > > _______________________________________________ > 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] Question on Fortran binding errata
by Craig Rasmussen 12 Feb '14

12 Feb '14

We realized after working on MPI-3 for awhile that we would need Fortran wrappers and couldn't really call C routines directly. One of the reasons is that the MPI C routines return a function value and most of the Fortran bindings are subroutines without a return value. The language you refer to is a requirement on the implementer as to what the name of the wrapper routine is. For example, if the user calls MPI_Isend and uses the MPI_F08 module, then the wrapper routine shall (must) be called MPI_Isend_f08. Another requirement we have placed on implementors is that the wrapper name can't be hidden within a module so that Fortran module name mangling won't be done for the MPI_Isend_f08 routine. Craig Rasmussen CAS Scientific Programmer rasmus(a)cas.uoregon.edu On Feb 12, 2014, at 1:28 PM, Junchao Zhang wrote: > Hello, > On page 10, line 38 of the errata, http://www.mpi-forum.org/docs/mpi-3.0/errata-30.pdf, it reads > > A Fortran call to an MPI routine shall result in a call to a procedure with one of the > specific procedure names and calling conventions, as described in Table 1.1 on page 11. > Case is not significant in the names. > > Can someone explain it a little more, especially, what is the meaning of "specific procedure names"? > 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

1 0

Question on Fortran binding errata
by Junchao Zhang 12 Feb '14

12 Feb '14

Hello, On page 10, line 38 of the errata, http://www.mpi-forum.org/docs/mpi-3.0/errata-30.pdf, it reads A Fortran call to an MPI routine shall result in a call to a procedure with one of the specific procedure names and calling conventions, as described in Table 1.1 on page 11. Case is not significant in the names. Can someone explain it a little more, especially, what is the meaning of "specific procedure names"? Thank you. --Junchao Zhang

1 0

Re: [MPIWG Fortran] What is BIND(C)?
by Tobias Burnus 08 Feb '14

08 Feb '14

1 0

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

07 Feb '14

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 <jczhang(a)mcs.anl.gov> 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) <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). > > > > 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 > > _______________________________________________ > 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 Junchao Zhang 06 Feb '14

06 Feb '14

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) <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). > > > > 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 >

1 0