Re: [OMPI devel] oshmem Fortran

2013-10-18 Thread Jeff Squyres (jsquyres)
+1. On Oct 18, 2013, at 10:17 AM, Ralph Castain wrote: > Then I would suggest you stick with "oshmem" to be clear you mean OpenSHMEM > > On Oct 18, 2013, at 6:20 AM, Igor Ivanov wrote: > >> As I know OpenSHMEM is an effort to create a standardized SHMEM library for >> C and Fortran. SGI’s S

Re: [OMPI devel] oshmem Fortran

2013-10-18 Thread Ralph Castain
Then I would suggest you stick with "oshmem" to be clear you mean OpenSHMEM On Oct 18, 2013, at 6:20 AM, Igor Ivanov wrote: > As I know OpenSHMEM is an effort to create a standardized SHMEM library for C > and Fortran. SGI’s SHMEM API is the baseline for OpenSHMEM Specification 1.0. > Most of O

Re: [OMPI devel] oshmem Fortran

2013-10-18 Thread Igor Ivanov
As I know OpenSHMEM is an effort to create a standardized SHMEM library for C and Fortran. SGI’s SHMEM API is the baseline for OpenSHMEM Specification 1.0. Most of OpenSHMEM API functions can be found in different SHMEM API implementations but there are functions that are specific for SGI`s, Cr

Re: [OMPI devel] oshmem Fortran

2013-10-18 Thread Jeff Squyres (jsquyres)
On Oct 18, 2013, at 1:18 AM, Igor Ivanov wrote: > Is there naming convention related configure options in OMPI? > Do you see any objections about --enable-oshmem-xxx or they must be replaced > with --enable-shmem-xxx? Hmm. Good question. I don't know enough about shmem vs. open shmem to say.

Re: [OMPI devel] oshmem Fortran

2013-10-18 Thread Igor Ivanov
Hi Jeff, Is there naming convention related configure options in OMPI? Do you see any objections about --enable-oshmem-xxx or they must be replaced with --enable-shmem-xxx? Regards, Igor On 17.10.2013 14:20, Jeff Squyres (jsquyres) wrote: Mellanox -- In r29448, you deleted the comment witho

[OMPI devel] oshmem Fortran

2013-10-17 Thread Jeff Squyres (jsquyres)
Mellanox -- In r29448, you deleted the comment without doing what it explicitly said to do. For example, you can --disable-mpi-fortran --enable-oshmem-fortran and get a broken build. Additionally, the shmem example in examples/ has several problems: 1. Why all the #defines? This is supposed

[OMPI devel] oshmem fortran interface

2013-09-13 Thread Jeff Squyres (jsquyres)
The open shmem Fortran iterface is quite definitely not a Fortran 77 interface (there have not been Fortran 77 compilers in over 30 years). Can we rename the oshmem/shmem/f77 directory to be oshmem/shmem/fortran? Also, there should be no shmemf77 and shmemf90 wrappers -- there should only be sh