Open MPI logo

Open MPI Development Mailing List Archives

  |   Home   |   Support   |   FAQ   |   all Development mailing list

Subject: Re: [OMPI devel] [EXTERNAL] oshmem implementation still lacking
From: Barrett, Brian W (bwbarre_at_[hidden])
Date: 2013-09-15 06:14:29


Yes, they should be oshcc, oshCC (there are no C++ bindings, but there is a wrapper compiler), and oshfort, according to the specification. Brian -- Brian W. Barrett Scalable System Software Group Sandia National Laboratories ________________________________________ From: devel [devel-bounces_at_[hidden]] on behalf of Jeff Squyres (jsquyres) [jsquyres_at_[hidden]] Sent: Sunday, September 15, 2013 4:13 AM To: Open MPI Developers Subject: Re: [OMPI devel] [EXTERNAL] oshmem implementation still lacking On Sep 15, 2013, at 12:10 PM, "Barrett, Brian W" <bwbarre_at_[hidden]> wrote: > Are the wrapper compilers named shmem<lang>? Given that the OpenSHMEM specification specifically calls out the name of the wrapper compilers as osh<lang>, we should probably follow that convention. Yes, they're named shmemcc and shmemfort. So they should be named oshcc and oshfort? I.e., is there a convention for <lang>? -- Jeff Squyres jsquyres_at_[hidden] For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/ _______________________________________________ devel mailing list devel_at_[hidden] http://www.open-mpi.org/mailman/listinfo.cgi/devel