Ok. Mellanox: please rename shmemcc and shmemfort, and please create shmemCC (shmemcxx for non-case-sensitive filesystems -- see ompi/tools/wrappers for how this is done).
Thanks. On Sep 15, 2013, at 12:14 PM, "Barrett, Brian W" <bwba...@sandia.gov> wrote: > 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-boun...@open-mpi.org] on behalf of Jeff Squyres (jsquyres) > [jsquy...@cisco.com] > 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" <bwba...@sandia.gov> 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 > jsquy...@cisco.com > For corporate legal information go to: > http://www.cisco.com/web/about/doing_business/legal/cri/ > > _______________________________________________ > devel mailing list > de...@open-mpi.org > http://www.open-mpi.org/mailman/listinfo.cgi/devel > _______________________________________________ > devel mailing list > de...@open-mpi.org > http://www.open-mpi.org/mailman/listinfo.cgi/devel -- Jeff Squyres jsquy...@cisco.com For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
