[OMPI users] Fortran and OpenMPI 1.8.3 compiled with Intel-15 does nothing silently

I have succesfully been using OpenMPI 1.8.3 compiled with Intel-14, using ./configure --prefix=/usr/local/mpi/$(basename $PWD) --with-threads=posix --enable-mpi-thread-multiple --disable-vt --with-scif=no I have now switched to Intel 15.0.1, and configuring with the same options, I get minor

Re: [OMPI users] Fortran and OpenMPI 1.8.3 compiled with Intel-15 does nothing silently

the process count suppresses it are still a mystery John On 17 November 2014 16:41, John Bray <jb...@allinea.com> wrote: > I have succesfully been using OpenMPI 1.8.3 compiled with Intel-14, using > > ./configure --prefix=/usr/local/mpi/$(basename $PWD) --with-threads=posix > --enable-m

Re: [OMPI users] Fortran and OpenMPI 1.8.3 compiled with Intel-15 does nothing silently

> does your program calls MPI anywhere from an OpenMP region ? >>> does your program calls MPI only within an !$OMP MASTER section ? >>> does your program does not invoke MPI at all from any OpenMP region ? >>> >>> can you reproduce this issue with a simple for

Re: [OMPI users] Fortran and OpenMPI 1.8.3 compiled with Intel-15 does nothing silently

utine sub > > end module MYMODULE > > ! > > program fred > > use MYMODULE > use mpi > integer :: ierr > call mpi_init(ierr) > print *,"hello" > call mpi_finalize(ierr) > end program fred > > > > > > Greetings > > Michael Rach

[OMPI users] Converting --cpus-per-proc to --map-by for a hybrid code

To run a hybrid MPI/OpenMP code on a hyperthreaded machine with 24 virtual cores, I've been using -n 12 --cpus-per-proc 2 so I can use OMP_NUM_THREADS=2 I now see that --cpus-per-proc is deprecated in favour of --map-by, but I've been struggling to find a conversion as the --map-by documentation

Re: [OMPI users] Converting --cpus-per-proc to --map-by for a hybrid code

Hi Ralph I have a motherboard with 2 X6580 chips, each with 6 cores 2 way hyperthreading, so /proc/cpuinfo reports 24 cores Doing a pure compute OpenMP loop where I'd expect the number of iterations in 10s to rise with number of threads with gnu and mpich OMP_NUM_THREADS=1 -n 1 : 112 iterations

Re: [OMPI users] Converting --cpus-per-proc to --map-by for a hybrid code

lstopo is pretty! John

Re: [OMPI users] Converting --cpus-per-proc to --map-by for a hybrid code

ur earlier note. > > Try using —map-by node:PE=N to your cmd line. I think the problem is that > we default to —map-by numa if you just give cpus-per-proc and no mapping > directive as we know that having threads that span multiple numa regions is > bad for performance > > > >

[OMPI users] Sample code using the more obscure MPI_Neighbor routines

I want to validate Allinea's profiler on the complete set of p2p and collective routines available in MPI and went looking for examples of the MPI_Neighbor routines in action. I can find a range of PDF tutorials and papers, but no actual sample codes to try. The OpenMPI examples for 1.8.4 don't

[MTT users] Simple sample code to test MPI wrappers

Hi All I'm the QA Manager at Allinea, a small company that produces the DDT Parallel Debugger and MAP Parallel Profiler, and we spend a lot of time manipulating MPI environments to get our debugging and profiling to work. In particular for the MAP profiler, which is a sampling one, we want to

Re: [MTT users] Simple sample code to test MPI wrappers

> > George. > > > On Aug 13, 2013, at 11:00 , John Bray <jb...@allinea.com> wrote: > >> Hi All >> >> I'm the QA Manager at Allinea, a small company that produces the DDT >> Parallel Debugger and MAP Parallel Profiler, and we spend a lot of