-os-x
>
>
>
> Greetings
>
> Michael Rachner
>
>
>
> *Von:* users [mailto:users-boun...@open-mpi.org] *Im Auftrag von *John
> Bray
> *Gesendet:* Dienstag, 18. November 2014 11:03
>
> *An:* Open MPI Users
> *Betreff:* Re: [OMPI users] Fortran and OpenMPI 1.8.3
:03
An: Open MPI Users
Betreff: Re: [OMPI users] Fortran and OpenMPI 1.8.3 compiled with Intel-15 does
nothing silently
The original problem used a separate file and not a module. Its clearly a
bizarre Intel bug, I am only continuing to persue it here as I'm curious as to
why the seg
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 Rachner
>
>
ers] Fortran and OpenMPI 1.8.3 compiled with Intel-15 does
nothing silently
A delightful bug this, you get a segfault if you code contains a random_number
call and is compiled with -fopenmp, EVEN IF YOU CANNOT CALL IT!
program fred
use mpi
integer :: ierr
call mpi_init(ierr)
print *,"hell
A delightful bug this, you get a segfault if you code contains a
random_number call and is compiled with -fopenmp, EVEN IF YOU CANNOT CALL
IT!
program fred
use mpi
integer :: ierr
call mpi_init(ierr)
print *,"hello"
call mpi_finalize(ierr)
contains
subroutine sub
real :: a(10)
call rando
Just checked the head of the 1.8 branch (soon to be released as 1.8.4), and
confirmed the same results. I know the thread-multiple option is still
broken there, but will test that once we get the final fix committed.
On Mon, Nov 17, 2014 at 7:29 PM, Ralph Castain wrote:
> FWIW: I don't have acc
FWIW: I don't have access to a Linux box right now, but I built the OMPI
devel master on my Mac using Intel 2015 compilers and was able to build/run
all of the Fortran examples in our "examples" directory.
I suspect the problem here is your use of the
--enable-mpi-thread-multiple option.
The 1.8 s
Hi John,
do you MPI_Init() or do you MPI_Init_thread(MPI_THREAD_MULTIPLE) ?
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
More investigation suggests its the use of -fopenmp (and also its new name
-qopenmp) just to compile in OpenMP code, even if it is never executed
mpiexec -n 12 ./one_f_debug.exe
fails silently
mpiexec -n 2 ./one_f_debug.exe
has a segfault
Both the segfault and the reason why changing the process
Check by ldd in case you didn't update .so path
Sent via the ASUS PadFone X mini, an AT&T 4G LTE smartphone
Original Message
From:John Bray
Sent:Mon, 17 Nov 2014 11:41:32 -0500
To:us...@open-mpi.org
Subject:[OMPI users] Fortran and OpenMPI 1.8.3 compiled with Inte
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 chan
11 matches
Mail list logo
