Paul,
The two header files in include/mpp simply include the file with the same
name in the upper directory.
A simple workaround is to replace these two files in include/mpp with
symbolic links to files with the same name in the upper directory.
Would you mind giving this a try ?
Cheers,
Gilles
I think the decision was made to postpone the patch to 2.0.1, since the
release of 2.0.0 is eminent.
Thanks
Edgar
On 7/12/2016 2:51 PM, Eric Chamberland wrote:
Hi Edgard,
I just saw that your patch got into ompi/master... any chances it goes
into ompi-release/v2.x before rc5?
thanks,
Eric
Thanks Jeff for your inputs.
‹
Murali
On 7/12/16, 12:12 PM, "devel on behalf of Jeff Squyres (jsquyres)"
wrote:
>Unfortunately, the Open MPI code base is quite large, and changes over
>time.
>
>There really is no overall diagram describing the entire code base,
>sorry. The OPAL-level dox
Hi Edgard,
I just saw that your patch got into ompi/master... any chances it goes
into ompi-release/v2.x before rc5?
thanks,
Eric
On 08/07/16 03:14 PM, Edgar Gabriel wrote:
I think I found the problem, I filed a pr towards master, and if that
passes I will file a pr for the 2.x branch.
Th
Unfortunately, the Open MPI code base is quite large, and changes over time.
There really is no overall diagram describing the entire code base, sorry. The
OPAL-level doxygen docs are probably the best you'll get, but they're really
only the utility classes in the portability layer. They don't
Thanks Kawashima. This note is really helpful.
‹
Murali
On 7/7/16, 4:17 PM, "devel on behalf of KAWASHIMA Takahiro"
wrote:
>FWIW, I have my private notes on process and datatype -related structs.
>
> https://rivis.github.io/doc/openmpi/openmpi-source-reading.en.xhtml
>
>They are created
Thanks Ralph.
The ‘doxygen’ command generated a bunch of html files along with few class
diagrams in “gif”. I think these figures cover only few classes/structs and
are not exhaustive. I am looking to generate a complete hierarchical diagram. I
will try to see if I can utilize the generated ht
I have updated the README; thanks Paul.
> On Jul 12, 2016, at 2:31 PM, Paul Hargrove wrote:
>
> Ok, PGI 15.10 w/ -m32 failed in the same way as the earlier versions.
>
> -Paul
>
> On Tue, Jul 12, 2016 at 11:10 AM, Paul Hargrove wrote:
> I have a lead on a 15.10 installation with -m32 support.
Ok, PGI 15.10 w/ -m32 failed in the same way as the earlier versions.
-Paul
On Tue, Jul 12, 2016 at 11:10 AM, Paul Hargrove wrote:
> I have a lead on a 15.10 installation with -m32 support.
> I will report results later.
>
> -Paul
>
>
> On Tue, Jul 12, 2016 at 10:29 AM, Jeff Squyres (jsquyres)
I have a lead on a 15.10 installation with -m32 support.
I will report results later.
-Paul
On Tue, Jul 12, 2016 at 10:29 AM, Jeff Squyres (jsquyres) <
jsquy...@cisco.com> wrote:
> Got it; thanks.
>
> > On Jul 12, 2016, at 1:00 PM, Paul Hargrove wrote:
> >
> > I have only access to two instanc
Per the call today, I added a "known issues" section to NEWS. Please have a
look and make comments -- I'd like to merge within the next hour or two:
https://github.com/open-mpi/ompi-release/pull/1266
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisc
Dear OpenMPI developer,
we have some troubles when using OpenMPI and CMake on codes using 'SHMEM'.
Cf. 'man shmem_swap',
> Fortran:
> INCLUDE "mpp/shmem.fh"
Yes here is one such header file:
> openmpi-1.X.Y/oshmem/include/mpp/shmem.fh
... since version 1.7. at least.
The significn
Got it; thanks.
> On Jul 12, 2016, at 1:00 PM, Paul Hargrove wrote:
>
> I have only access to two instances of PGI which were installed with -m32
> support.
> They are both old: 12.10-0 and 13.9-0.
> Sorry, I know that's not much.
>
> -Paul
>
> On Tue, Jul 12, 2016 at 8:06 AM, Howard Pritcha
I have only access to two instances of PGI which were installed with -m32
support.
They are both old: 12.10-0 and 13.9-0.
Sorry, I know that's not much.
-Paul
On Tue, Jul 12, 2016 at 8:06 AM, Howard Pritchard
wrote:
> Paul,
>
> Could you narrow down the versions of the PGCC where you get the I
Paul,
Could you narrow down the versions of the PGCC where you get the ICE when
using the -m32 option?
Thanks,
Howard
2016-07-06 15:29 GMT-06:00 Paul Hargrove :
> The following are previously reported issues that I am *not* expecting to
> be resolved in 2.0.0.
> However, I am listing them her
My mistake.
Looks like "--disable-smp-locks" is no longer available in 2.0.x versions.
Thanks,
- Sreenidhi.
-Original Message-
From: Sreenidhi Bharathkar Ramesh
[mailto:sreenidhi-bharathkar.ram...@broadcom.com]
Sent: Tuesday, 12 July, 2016 11:32 AM
To: 'Open MPI Developers'
Subject: Re:
> On Jul 12, 2016, at 12:01 AM, Sreenidhi Bharathkar Ramesh
> wrote:
>
> [ query regarding an old thread ]
>
> Hi,
>
> It looks like "--disable-smp-locks" is still available as an option.
>
> 1. Will this be continued or deprecated ?
It was completely discontinued. The problem with the opti
[ query regarding an old thread ]
Hi,
It looks like "--disable-smp-locks" is still available as an option.
1. Will this be continued or deprecated ?
2. Under what circumstances would "--disable-smp-locks" be useful ?
In our experiments on ARM64 platform, it was seen that OSU Micro collective
be
Hi,
Looks like there's a #include missing from
oshmem/shmem/fortran/shmem_put_nb_f.c. It's causing MCA_SPML_CALL to show up
as an undefined symbol, even though it's a macro (among other things). The
#include is in shmem_get_nb_f.c but not ..._put_...
Patch against master (0e433ea):
$ git diff
di
19 matches
Mail list logo
