Re: [OMPI users] Passive target sync. support

Thanks! Sebastian On 03 Apr 2017, at 23:23, Nathan Hjelm wrote: > No, support is enabled by default. You can check whether it is working by > running with --mca osc ^pt2pt . This will disable the two-sided > implementation. > > -Nathan > > On Apr 03, 2017, at 03:02 PM,

Re: [OMPI users] Compiler error with PGI: pgcc-Error-Unknown switch: -pthread

Coming in near the end here. I've had "fun" with PGI + Open MPI + macOS (and still haven't quite solved it, see: https://www.mail-archive.com/users@lists.open-mpi.org//msg30865.html, still unanswered!) The solution that PGI gave me, and which seems the magic sauce on macOS is to use a siterc file

Re: [OMPI users] MPI_WAIT hangs after a call to MPI_CANCEL

On Mon, Apr 3, 2017 at 4:47 PM, McGrattan, Kevin B. Dr. (Fed) < kevin.mcgrat...@nist.gov> wrote: > Thanks, George. > > > > Are persistent send/receives matched from the start of the calculation? If > so, then I guess MPI_CANCEL won’t work. > A persistent request is only matched when it is

Re: [OMPI users] Passive target sync. support

No, support is enabled by default. You can check whether it is working by running with --mca osc ^pt2pt . This will disable the two-sided implementation. -Nathan On Apr 03, 2017, at 03:02 PM, Sebastian Rinke wrote: Thank you very much for the quick response! Do I

Re: [OMPI users] Compiler error with PGI: pgcc-Error-Unknown switch: -pthread

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 03.04.2017 um 23:07 schrieb Prentice Bisbal: > FYI - the proposed 'here-doc' solution below didn't work for me, it produced > an error. Neither did printf. When I used printf, only the first arg was > passed along: > > #!/bin/bash > >

Re: [OMPI users] Compiler error with PGI: pgcc-Error-Unknown switch: -pthread

FYI - the proposed 'here-doc' solution below didn't work for me, it produced an error. Neither did printf. When I used printf, only the first arg was passed along: #!/bin/bash realcmd=/usr/pppl/pgi/17.3/linux86-64/17.3/bin/pgcc.real echo "original args: $@" newargs=$(printf -- "$@" | sed

Re: [OMPI users] Passive target sync. support

Thank you very much for the quick response! Do I need to configure with certain flags to enable the hardware put/get support? Sebastian On 03 Apr 2017, at 18:02, Nathan Hjelm wrote: > > > On Apr 03, 2017, at 08:36 AM, Sebastian Rinke > wrote: >

Re: [OMPI users] Compiler error with PGI: pgcc-Error-Unknown switch: -pthread

A coworker came up with another idea that works, too: newargs=sed s/-pthread//g < Try $ printf -- "-E" ... On 04/03/2017 04:03 PM, Prentice Bisbal wrote: Okay. the additional -E doesn't work,either. :( Prentice Bisbal Lead Software Engineer Princeton Plasma Physics Laboratory

Re: [OMPI users] Compiler error with PGI: pgcc-Error-Unknown switch: -pthread

Try $ printf -- "-E" ... On 04/03/2017 04:03 PM, Prentice Bisbal wrote: Okay. the additional -E doesn't work,either. :( Prentice Bisbal Lead Software Engineer Princeton Plasma Physics Laboratory http://www.pppl.gov On 04/03/2017 04:01 PM, Prentice Bisbal wrote: Nevermind. A coworker helped

Re: [OMPI users] Compiler error with PGI: pgcc-Error-Unknown switch: -pthread

Okay. the additional -E doesn't work,either. :( Prentice Bisbal Lead Software Engineer Princeton Plasma Physics Laboratory http://www.pppl.gov On 04/03/2017 04:01 PM, Prentice Bisbal wrote: Nevermind. A coworker helped me figure this one out. Echo is treating the '-E' as an argument to echo

Re: [OMPI users] Compiler error with PGI: pgcc-Error-Unknown switch: -pthread

Nevermind. A coworker helped me figure this one out. Echo is treating the '-E' as an argument to echo and interpreting it instead of passing it to sed. Since that's used by the configure tests, that's a bit of a problem, Just adding another -E before $@, should fix the problem. Prentice On

Re: [OMPI users] Compiler error with PGI: pgcc-Error-Unknown switch: -pthread

I've decided to work around this problem by creating a wrapper script for pgcc that strips away the -pthread argument, but my sed expression works on the command-line, but not in the script. I'm essentially reproducing the workaround from

Re: [OMPI users] MPI_WAIT hangs after a call to MPI_CANCEL

Kevin, In Open MPI we only support cancelling non-yet matched receives. So, you cannot cancel sends nor receive requests that have already been matched. While the latter are supposed to complete (otherwise they would not have been matched), the former are trickier to complete if the corresponding

Re: [OMPI users] Compiler error with PGI: pgcc-Error-Unknown switch: -pthread

To be thorough couldn't one replace -pthread in the slurm .la files with -lpthread? I ran into this last week and this was the solution I was thinking about implementing. Having said that, I can't think of a situation in which the -pthread/-lpthread argument would be required other than

Re: [OMPI users] Compiler error with PGI: pgcc-Error-Unknown switch: -pthread

We build slurm with GCC, drop the -pthread arg in the .la files, and have never seen any problems related to that. And we do build quite a lot of code. And lots of versions of OpenMPI with multiple different compilers (and versions). On 04/03/2017 04:51 PM, Prentice Bisbal wrote: > This is the

Re: [OMPI users] Passive target sync. support

On Apr 03, 2017, at 08:36 AM, Sebastian Rinke wrote: Dear all, I’m using passive target sync. in my code and would like to know how well it is supported in Open MPI. In particular, the code is some sort of particle tree code that uses a distributed tree and every

Re: [OMPI users] Compiler error with PGI: pgcc-Error-Unknown switch: -pthread

This is the second suggestion to rebuild Slurm The other from Åke Sandgren, who recommended this: This usually comes from slurm, so we always do perl -pi -e 's/-pthread//'/lap/slurm/${version}/lib/libpmi.la /lap/slurm/${version}/lib/libslurm.la when installing a new slurm version. Thus no

[OMPI users] Passive target sync. support

Dear all, I’m using passive target sync. in my code and would like to know how well it is supported in Open MPI. In particular, the code is some sort of particle tree code that uses a distributed tree and every rank gets non-local tree nodes that are needed for its own computation from other

Re: [OMPI users] Compiler error with PGI: pgcc-Error-Unknown switch: -pthread

Hi, The -pthread flag is likely pulled by libtool from the slurm libmpi.la and/or libslurm.la Workarounds are - rebuild slurm with PGI - remove the .la files (*.so and/or *.a are enough) - wrap the PGI compiler to ignore the -pthread option Hope this helps Gilles On Monday, April 3, 2017,

Re: [OMPI users] Compiler error with PGI: pgcc-Error-Unknown switch: -pthread

This usually comes from slurm, so we always do perl -pi -e 's/-pthread//' /lap/slurm/${version}/lib/libpmi.la /lap/slurm/${version}/lib/libslurm.la when installing a new slurm version. Thus no need for a fakepg wrapper. On 04/03/2017 04:20 PM, Prentice Bisbal wrote: > Greeting Open MPI users!

[OMPI users] Compiler error with PGI: pgcc-Error-Unknown switch: -pthread

Greeting Open MPI users! After being off this list for several years, I'm back! And I need help: I'm trying to compile OpenMPI 1.10.3 with the PGI compilers, version 17.3. I'm using the following configure options: ./configure \ --prefix=/usr/pppl/pgi/17.3-pkgs/openmpi-1.10.3 \