Hi Jeff,
I would like to add few notes inline
Igor
On 25.10.2013 20:33, Jeff Squyres (jsquyres) wrote:
We had a few emails a little while ago, and decided that the branding should be
"oshmem" because Open SHMEM is different than (original) SHMEM.
I notice that there's still:
- shmemcc / shmemfort / shmem_info / shmemrun
--> should these all be "oshmem*" ?
- the examples are hello_shmem* and ring_shmem*
--> should these all be "*_oshmem*" ?
These examples are not OpenSHMEM specific.
- there are header files named shmem*
--> I'm guessing the names "shmem.h" and "shmem.fh" are mandated
OpenSHMEM specification says
>>>
10.1 Incorporating OpenSHMEM into Programs
C and C++ programs that use the OpenSHMEM library must
#include <shmem.h>
All Fortran OpenSHMEM programs should
include ’shmem.fh’
and Fortran OpenSHMEM programs that use constants defined by OpenSHMEM must
include ’shmem.fh’
10.1.1 Compatibility Note
Implementations must also provide these header files so that they can be
referenced in C
and C++ as
#include <mpp/shmem.h>
and in Fortran as
include ’mpp/shmem.fh’
for backward compatbility with OpensHMEM 1.0 and SGI SHMEM.
<<<
--> shmem_portable_platform.h.in should probably be
oshmem_portable_platform.h.in, right?
--> same for the internal headers shmem_api_logger.h and shmem_lock.h
