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