On May 10, 2016, at 12:26 , Gilles Gouaillardet wrote:
except if you #include the libc header in your app, *and* your send
function has a different prototype, I do not see how clang can issue
a warning
(except of course if clang "knows" all the libc subroutines ...)
not sure if that helps t
except if you #include the libc header in your app, *and* your send
function has a different prototype, I do not see how clang can issue a
warning
(except of course if clang "knows" all the libc subroutines ...)
Cheers,
Gilles
On Tuesday, May 10, 2016, Devon Hollowood wrote:
> That worked perf
That worked perfectly. Thank you. I'm surprised that clang didn't emit a
warning about this!
-Devon
On Mon, May 9, 2016 at 3:42 PM, Gilles Gouaillardet <
gilles.gouaillar...@gmail.com> wrote:
> Devon,
>
> send() is a libc function that is used internally by Open MPI, and it uses
> your user func
Devon,
send() is a libc function that is used internally by Open MPI, and it uses
your user function instead of the libc ne.
simply rename your function mysend() or something else that is not used by
libc, and your issue will likely be fixed
Cheers,
Gilles
On Tuesday, May 10, 2016, Devon Hollow
Hello,
I am having trouble understanding why I am getting an error when running
the program produced by the attached C file. In this file, there are three
short functions: send(), bounce() and main(). send() and bounce() both use
MPI_Send() and MPI_Recv(), but critically, neither one is called fro
