Re: [OMPI users] Issue with Profiling Fortran code

2008-12-05 Thread Nick Wright
y incorrect. (BTW, LAM/MPI handles profiling the same way as Open MPI). Brian On Fri, 5 Dec 2008, Nick Wright wrote: Hi Antony That will work yes, but its not portable to other MPI's that do implement the profiling layer correctly unfortunately. I guess we will just need to detect that

Re: [OMPI users] Issue with Profiling Fortran code

2008-12-05 Thread Nick Wright
pen MPI has done, I don't think you can claim Open MPI is doing it "incorrectly". Different from MPICH is not necessarily incorrect. (BTW, LAM/MPI handles profiling the same way as Open MPI). Brian On Fri, 5 Dec 2008, Nick Wright wrote: Hi Antony That will work yes, but its n

Re: [OMPI users] Issue with Profiling Fortran code

2008-12-05 Thread Nick Wright
Nick. George Bosilca wrote: Nick, Thanks for noticing this. It's unbelievable that nobody noticed that over the last 5 years. Anyway, I think we have a one line fix for this problem. I'll test it asap, and then push it in the 1.3. Thanks, george. On Dec 5, 2008, at 10:14 , Nick

Re: [OMPI users] Issue with Profiling Fortran code

2008-12-05 Thread Nick Wright
I think we can just look at OPEN_MPI as you say and then OMPI_MAJOR_VERSION, OMPI_MINOR_VERSION & OMPI_RELEASE_VERSION from mpi.h and if version is less than 1.2.9 implement a work around as Antony suggested. Its not the most elegant solution but it will work I think? Nick. Jeff Squyres wro

Re: [OMPI users] Issue with Profiling Fortran code

2008-12-05 Thread Nick Wright
you can just call C version of PMPI_xxx directly from your fortran layer, e.g. void mpi_comm_rank_(MPI_Comm *comm, int *rank, int *info) { printf("mpi_comm_rank call successfully intercepted\n"); *info = PMPI_Comm_rank(comm,rank); } A.Chan - "Nick Wright" wrote: H

[OMPI users] Issue with Profiling Fortran code

2008-12-04 Thread Nick Wright
Hi I am trying to use the PMPI interface with OPENMPI to profile a fortran program. I have tried with 1.28 and 1.3rc1 with --enable-mpi-profile switched on. The problem seems to be that if one eg. intercepts to call to mpi_comm_rank_ (the fortran hook) then calls pmpi_comm_rank_ this then c