[OMPI devel] 1.7.4rc1 test failure : cygwin 64 bit

2014-01-07 Thread marco atzeri
Failures on cygwin 64bit with gcc-4.8.2. Notes: - cygwin 32bit gives no failure - These failures are not new, they were also present in openmpi-1.7.3-1 and previous - --> Testing atomic_spinlock_noinline.exe /pub/devel/openmpi/ope

Re: [OMPI devel] 1.7.4rc1 test failure : cygwin 64 bit

2014-01-07 Thread George Bosilca
Can you try with the latest trunk please? Also if things are not going well with the trunk please provide the opal_config.h file. Thanks, George. On Jan 7, 2014, at 14:19 , marco atzeri wrote: > Failures on cygwin 64bit with gcc-4.8.2. > Notes: > - cygwin 32bit gives no failure > - Thes

Re: [OMPI devel] return value of opal_compress_base_register() in opal/mca/compress/base/compress_base_open.c

2014-01-07 Thread Josh Hursey
Either would be fine with me. If you left in the verbose message then it might be a bit confusing to any user that might see it. On Fri, Jan 3, 2014 at 9:13 AM, Ralph Castain wrote: > That would work. Alternatively, you could try just returning OPAL_SUCCESS > in place of OPAL_ERR_NOT_AVAILABLE.

Re: [OMPI devel] return value of opal_compress_base_register() in opal/mca/compress/base/compress_base_open.c

2014-01-07 Thread Adrian Reber
I have commited fixes for opal/mca/compress/base/compress_base_open.c and opal/mca/crs/base/crs_base_open.c which return OPAL_SUCCESS but do not open the components if CR is disabled. Adrian On Tue, Jan 07, 2014 at 01:43:00PM -0600, Josh Hursey wrote: > Either would be fine with

[OMPI devel] [Patch] For Fortran, support GCC/gfortran 4.9's TYPE(*) with NO_ARG_CHECK

2014-01-07 Thread Tobias Burnus
Hello, I'd like to see the following patch to be included in Open MPI, which enabled interface checking also with GCC's gfortran. While TYPE(*), DIMENSION(*) is already tested for, it cannot be used for scalars (and "TYPE(*)" cannot be used with arrays). [Those were added in GCC 4.8, which d

[OMPI devel] RFC: Drop all mpirun single-dash multi-letter CLI options (except -np)

2014-01-07 Thread Jeff Squyres (jsquyres)
WHAT: Drop mpirun single-dash CLI options such as -bynode (but keep the double-dash equivalents, like --bynode) WHY: It's a well-established de facto CLI option standard: "-" is used for single-letter options "--" is used for tokenized options WHERE: probably mostly in orte/tools/orterun WH

Re: [OMPI devel] RFC: Drop all mpirun single-dash multi-letter CLI options (except -np)

2014-01-07 Thread Ralph Castain
+1 On Jan 7, 2014, at 1:49 PM, Jeff Squyres (jsquyres) wrote: > WHAT: Drop mpirun single-dash CLI options such as -bynode (but keep the > double-dash equivalents, like --bynode) > > WHY: It's a well-established de facto CLI option standard: > "-" is used for single-letter options > "--" is u

[OMPI devel] RFC: OB1 optimizations

2014-01-07 Thread Nathan Hjelm
What: Push some ob1 optimizations to the trunk and 1.7.5. What: This patch contains two optimizations: - Introduce a fast send path for blocking send calls. This path uses the btl sendi function to put the data on the wire without the need for setting up a send request. In the case of b

Re: [OMPI devel] RFC: Drop all mpirun single-dash multi-letter CLI options (except -np)

2014-01-07 Thread Nathan Hjelm
+1. Single dashed long names drive me nuts. -Nathan On Tue, Jan 07, 2014 at 03:17:11PM -0800, Ralph Castain wrote: > +1 > > On Jan 7, 2014, at 1:49 PM, Jeff Squyres (jsquyres) > wrote: > > > WHAT: Drop mpirun single-dash CLI options such as -bynode (but keep the > > double-dash equivalents,

Re: [OMPI devel] RFC: OB1 optimizations

2014-01-07 Thread Shamis, Pavel
Overall it looks good. It would be helpful to validate performance numbers for other interconnects as well. -Pasha > -Original Message- > From: devel [mailto:devel-boun...@open-mpi.org] On Behalf Of Nathan > Hjelm > Sent: Tuesday, January 07, 2014 6:45 PM > To: Open MPI Developers List >

Re: [OMPI devel] RFC: OB1 optimizations

2014-01-07 Thread George Bosilca
The local request is not correctly released, leading to assert in debug mode. This is because you avoid calling MCA_PML_BASE_RECV_REQUEST_FINI, fact that leaves the request in an ACTIVE state, condition carefully checked during the call to destructor. I attached a second patch that fixes the is

Re: [OMPI devel] [Patch] For Fortran, support GCC/gfortran 4.9's TYPE(*) with NO_ARG_CHECK

2014-01-07 Thread Jeff Squyres (jsquyres)
Many thanks for the reminder; this had totally slipped off my radar. :-( Oy, yes, I added this in my bitbucket forever ago and forgot to bring it to the trunk! :-( It looks like that bitbucket is in bad shape -- I just svn up'ed it, and it no longer compiles. I suspect some conflicts crept i