Hi George,
Thank you for attending the meeting at Kyoto. As we talked
at the meeting, my colleague suffers from a datatype problem.
See attached create_resized.c. It creates a datatype with an
LB marker using MPI_Type_create_struct and MPI_Type_create_resized.
Expected contents of the output fil
I see behavioral difference between 1.8.x and trunk for OPAL_C_HAVE_VISIBILITY
definition on same build environment. is this expected?
-Devendar
-Original Message-
From: devel [mailto:devel-boun...@open-mpi.org] On Behalf Of Jeff Squyres
(jsquyres)
Sent: Monday, September 29, 2014 4:25
I can't quite parse what you are saying -- do you have a specific question?
On Sep 29, 2014, at 7:18 PM, Devendar Bureddy wrote:
> This is supposed to be enable by default. In trunk, I see that
> OPAL_C_HAVE_VISIBILITY is defined to 0 by default. 1.8.x looks fine
>
> Configure : ./config
This is supposed to be enable by default. In trunk, I see that
OPAL_C_HAVE_VISIBILITY is defined to 0 by default. 1.8.x looks fine
Configure : ./configure -prefix=$PWD/install --enable-mpirun-prefix-by-default
--disable-mpi-fortran --disable-vt --enable-debug --enable-oshmem --with-pmi
GCC :
Hi Jeff,
Sure if that's the preferred check inside ompi itself.
Howard
-Original Message-
From: devel [mailto:devel-boun...@open-mpi.org] On Behalf Of Jeff Squyres
(jsquyres)
Sent: Monday, September 29, 2014 3:59 PM
To: Open MPI Developers List
Subject: Re: [OMPI devel] [OMPI svn-full]
Howard --
Do you want to just check ompi_mpi_thread_provided (== MPI_THREAD_MULTIPLE),
instead?
On Sep 29, 2014, at 5:02 PM,
wrote:
> Author: hppritcha (Howard Pritchard)
> Date: 2014-09-29 17:02:15 EDT (Mon, 29 Sep 2014)
> New Revision: 32814
> URL: https://svn.open-mpi.org/trac/ompi/chang
I looks like OMPI_MCA_mpi_abort_print_stack=1 is broken. I'm seeing
following warning with it.
--
$mpirun -np 2 -x OMPI_MCA_mpi_abort_print_stack=1 ./hello_c
--
WARNING: A user-supplied value attempte
Hi Folks,
The release managers for the 1.9/2.0 stream have been putting together
notes on features for this series, what sort of code pruning to do, etc.
See
https://github.com/open-mpi/ompi/wiki/Releasev19
We will be discussing the contents of the table(s) at the bottom of the wiki
at tomorrow
Good catch - the problem is that ompi_info_get_bool returns "success" if the
value isn't found, setting "flag" to false, but doesn't set the value of the
param itself. So if you don't specify "blocking_fence" in MPI_Info, then the
"blocking_fence" flag wasn't being set.
Fixed in r32812 and sche
An equivalent change would need to be made for graph and dist graph as
well. That will take a little more work. Also, I was avoiding changing
anything in topo for 1.8.
-Nathan
On Mon, Sep 29, 2014 at 08:02:41PM +0900, Gilles Gouaillardet wrote:
>Nathan,
>
>why not just make the topology
Nathan,
why not just make the topology information available at that point as
you described it ?
the attached patch does this, could you please review it ?
Cheers,
Gilles
On 2014/09/26 2:50, Nathan Hjelm wrote:
> On Tue, Aug 26, 2014 at 07:03:24PM +0300, Lisandro Dalcin wrote:
>> I finally man
11 matches
Mail list logo
