Re: [OMPI users] ERR_TRUNCATE with MPI_Pack

On 02/14/2018 11:19 AM, Florian Lindner wrote: Hello, I have this example code: #include #include int main(int argc, char *argv[]) { MPI_Init(, ); { MPI_Request req1, req2; std::vector vec = {1, 2, 3}; int packSize = sizeof(int) * vec.size(); Why don't you use

Re: [OMPI users] mpifort cannot find libgfortran.so at the correct path

Hello Davide, On 11/28/17 15:58, Vanzo, Davide wrote: I am having a very weird problem with mpifort that I cannot understand. I am building OpenMPI 1.10.3 with GCC 5.4.0 with EasyBuild and everything goes fine until I try to use mpifort to build any MPI Fortran code, which fails with the

Re: [OMPI users] Question concerning compatibility of languages used with building OpenMPI and languages OpenMPI uses to build MPI binaries.

On 09/20/17 23:39, Jeff Hammond wrote: I assume that anyone who is using Fortran 2003 or later has the good sense to never use compiler flags to change the size of the INTEGER type, because this is evil. Actually, only changing INTEGER size without adjusting REAL size is evil (i.e. breaks

Re: [OMPI users] Hang in MPI_Abort

.6? Regards, Thomas -- Thomas Jahns HD(CP)^2 Abteilung Anwendungssoftware Deutsches Klimarechenzentrum GmbH Bundesstraße 45a • D-20146 Hamburg • Germany Phone: +49 40 460094-151 Fax:+49 40 460094-270 Email: Thomas Jahns <ja...@dkrz.de> URL:www.dkrz.de Geschäftsführer: Prof. Dr.

Re: [OMPI users] Incorrect function call in simple C program

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

Re: [OMPI users] Problems in compiling a code with dynamic linking

get binaries that also work when they haven't setup the environment for some specific intel compiler. An alternative is static linking but that has other downsides. Regards, Thomas Jahns smime.p7s Description: S/MIME Cryptographic Signature

Re: [OMPI users] Strange problem with mpirun and LIGGGHTS after reboot of machine

her an effect of the way your Linux scheduler works. Already tried to look for differences in the Ubuntu boot logs, but there is nothing different. Did you look into /proc/cpuinfo? Regards, Thomas -- Thomas Jahns HD(CP)^2 Abteilung Anwendungssoftware Deutsches Klimarechenzentrum GmbH Bundesstr

Re: [OMPI users] MPI, Fortran, and GET_ENVIRONMENT_VARIABLE

n environment variable to be set up. The process is still not entirely robust because you might end up on a non-RFC-compliant system where name lookup doesn't work. Regards, Thomas -- Thomas Jahns HD(CP)^2 Abteilung Anwendungssoftware Deutsches Klimarechenzentrum GmbH Bundesstraße 45a • D-20146

Re: [OMPI users] openmpi-1.10.2rc1: wrong ELF class on Solaris

Hello, On Dec 21, 2015, at 12:46 , Siegmar Gross wrote: LDFLAGS="-m64" CC="gcc" CXX="g++" FC="gfortran" \ CFLAGS="-m64" CXXFLAGS="-m64" FCFLAGS="-m64" \ CPP="cpp" CXXCPP="cpp" \ I might be wrong but

Re: [OMPI users] Using OpenMPI (1.8, 1.10) with Mellanox MXM, ulimits ?

Hello, On 09/28/15 18:36, Grigory Shamov wrote: The question is if we should do as MXM wants, or ignore it? Has anyone an experience running recent OpenMPI with MXM enabled, and what kind of ulimits do you have? Any suggestions/comments appreciated, thanks! It should be sufficient to set the

Re: [OMPI users] open mpi gcc

The usual way to override the C compiler is to invoke configure like this: ./configure CC=nameofcc Regards, Thomas smime.p7s Description: S/MIME Cryptographic Signature

Re: [OMPI users] difference between OPENMPI e Intel MPI (DATATYPE)

Hello, On 09/03/15 16:52, Nick Papior wrote: When you change environment, that is change between OpenMPI and Intel MPI, or compiler, it is recommended that you recompile everything. use mpi is a module, you cannot mix these between compilers/environments, sadly the Fortran specification does

Re: [OMPI users] OpenMPI Fortran with Intel 15 and OpenMP

://software.intel.com/en-us/forums/topic/549547 -- Thomas Jahns DKRZ GmbH, Department: Application software Deutsches Klimarechenzentrum Bundesstraße 45a D-20146 Hamburg Phone: +49-40-460094-151 Fax: +49-40-460094-270 Email: Thomas Jahns <ja...@dkrz.de> smime.p7s Description: S/MIME cryptographic signature

Re: [OMPI users] Invalid read of size 4 (Valgrind error) with OpenMPI 1.8.7

w.open-mpi.org/mailman/listinfo.cgi/users Link to this post: http://www.open-mpi.org/community/lists/users/2015/07/27348.php -- Thomas Jahns HD(CP)^2 Abteilung Anwendungssoftware Deutsches Klimarechenzentrum GmbH Bundesstraße 45a • D-20146 Hamburg • Germany Phone: +49 40 460094-151 Fax:+49 40

Re: [OMPI users] Progress on target of MPI_Win_lock on Infiniband

On 06/29/15 17:25, Nathan Hjelm wrote: This is not a configuration issue. On 1.8.x and master we use two-sided communication to emulation one-sided. Since we do not currently have async progress this requires the target to call into MPI to progress RMA communication. This will change in 2.x. I

Re: [OMPI users] Openmpi compilation errors

for the Fortran parts of OpenMPI, i.e. try something like ./configure CC=gcc CXX=g++ FC=pgf90 F77=pgf77 F90=pgf90 --prefix=/opt/openmpi-1.8.5_pgf90 Regards, Thomas Jahns smime.p7s Description: S/MIME Cryptographic Signature

Re: [OMPI users] Problems using Open MPI 1.8.4 OSHMEM on Intel Xeon Phi/MIC

ntel?? to that file. Regards, Thomas -- Thomas Jahns DKRZ GmbH, Department: Application software Deutsches Klimarechenzentrum Bundesstraße 45a D-20146 Hamburg Phone: +49-40-460094-151 Fax: +49-40-460094-270 Email: Thomas Jahns <ja...@dkrz.de> smime.p7s Description: S/MIME cryptographic signature

[OMPI users] http://www.open-mpi.org/doc/current/man3/MPI_Win_lock_all.3.php

Hello, I think above web site lists the Fortran syntax section incorrectly as INCLUDE ’mpif.h’ MPI_WIN_LOCK(ASSERT, WIN, IERROR) INTEGER ASSERT, WIN, IERROR when there should be MPI_WIN_LOCK_ALL(ASSERT, WIN, IERROR) instead. Regards, Thomas smime.p7s Description: S/MIME Cryptographic