On Aug 25, 2015, at 11:03 AM, George Bosilca <bosi...@icl.utk.edu> wrote: > > This seems to be the case only with the TKR interface. All the others are > either calling the OMPI version directly (mpif-h), or are calling some other > internal (or weak symbol function).
Yes, those might need to be updated. Not it! (let's let the TKR interface die...) You're right about the mpif-h interface, though -- they call the PMPI versions of the functions (through weak symbols). However, our use of weak symbols might be confusing to the tool -- is it somehow intercepting our call from ompi_send_f() to PMPI_Send(), for example? You might want to step through with a debugger to see what's happening, because the debugger should show the name of the symbol that is invoked in the call stack, even though the pointer in the source code may show you in "MPI_Send()" (remember: we compile the C code for our functions potential with #defines that turn MPI_Send into PMPI_Send, etc.). -- Jeff Squyres jsquy...@cisco.com For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
