[hwloc-devel] Create success (hwloc git 1.11.3-28-g20402ee)

[MPI Team]

Creating nightly hwloc snapshot git tarball was a success.

Snapshot:   hwloc 1.11.3-28-g20402ee
Start time: Tue Jul 12 21:03:18 EDT 2016
End time:   Tue Jul 12 21:04:57 EDT 2016

Your friendly daemon,
Cyrador

[hwloc-devel] Create success (hwloc git dev-1177-g5718fe3)

[MPI Team]

Creating nightly hwloc snapshot git tarball was a success.

Snapshot:   hwloc dev-1177-g5718fe3
Start time: Tue Jul 12 21:01:02 EDT 2016
End time:   Tue Jul 12 21:02:56 EDT 2016

Your friendly daemon,
Cyrador

Re: [OMPI devel] SHMEM, "mpp/shmem.fh", CMake and infinite loops

[Gilles Gouaillardet]

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

On Wednesday, July 13, 2016, Paul Kapinos 
wrote:

> 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 significnat content is this line:
> >  include 'shmem.fh'
> whereby OpenMPI mean to include not the same file by itself (= infinite
> loop!) but I believe these one file:
> > openmpi-1.X.Y/oshmem/include/shmem.fh
>
> (The above paths are in the source code distributions; in the installation
> the files are located here:  include/shmem.fh  include/mpp/shmem.fh)
>
>
> This works. Unless you start using CMake. Because CMake is 'intelligent'
> and try to add the search paths recursively, (I believe,) gloriously
> enabling the infinite loop by including the 'shmem.fh' file from the
> 'shmem.fh' file.
>
> Steps to repriduce:
> $ mkdir build; cd build; cmake ..
> $ make
>
> The second one command need some minute(s), sticking by the 'Scanning
> dependencies of target mpihelloworld' step.
>
> If connecting by 'strace -p ' to the 'cmake' process you will see
> lines like below, again and again. So I think CMake just include the
> 'shmem.fh' file from itself unless the stack is full / a limit is reached /
> the moon shines, and thus hangs for a while (seconds/minutes) in the
> 'Scanning dependencies...' state.
>
> *Well, maybe having a file including the same file is not that good?*
> If the file 'include/mpp/shmem.fh' would include not 'shmem.fh' but
> 'somethingelse.fh' located in 'include/...' these infinite loop would be
> impossible at all...
>
> And by the way: is here a way to limit the maximum include depths in CMake
> for header files? This would workaround this one 'infinite include loop'
> issue...
>
> Have a nice day,
>
> Paul Kapinos
>
> ..
> access("/opt/MPI/openmpi-1.10.2/linux/intel_16.0.2.181/include/mpp/shmem.fh",
> R_OK) = 0
> stat("/opt/MPI/openmpi-1.10.2/linux/intel_16.0.2.181/include/mpp/shmem.fh",
> {st_mode=S_IFREG|0644, st_size=205, ...}) = 0
> open("/opt/MPI/openmpi-1.10.2/linux/intel_16.0.2.181/include/mpp/shmem.fh",
> O_RDONLY) = 5271
> fstat(5271, {st_mode=S_IFREG|0644, st_size=205, ...}) = 0
> mmap(NULL, 32768, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0)
> = 0x7f08457d2000
> read(5271, "!\n!   Copyright (c) 2013  Me"..., 32768) = 205
> read(5271, "", 32768)   = 0
>
> access("/opt/MPI/openmpi-1.10.2/linux/intel_16.0.2.181/include/mpp/shmem.fh",
> R_OK) = 0
> stat("/opt/MPI/openmpi-1.10.2/linux/intel_16.0.2.181/include/mpp/shmem.fh",
> {st_mode=S_IFREG|0644, st_size=205, ...}) = 0
> open("/opt/MPI/openmpi-1.10.2/linux/intel_16.0.2.181/include/mpp/shmem.fh",
> O_RDONLY) = 5272
> fstat(5272, {st_mode=S_IFREG|0644, st_size=205, ...}) = 0
> mmap(NULL, 32768, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0)
> = 0x7f08457ca000
> read(5272, "!\n!   Copyright (c) 2013  Me"..., 32768) = 205
> read(5272, "", 32768)   = 0
> ..
>
> --
> Dipl.-Inform. Paul Kapinos   -   High Performance Computing,
> RWTH Aachen University, IT Center
> Seffenter Weg 23,  D 52074  Aachen (Germany)
> Tel: +49 241/80-24915
>

Re: [OMPI devel] 2.0.0rc4 Crash in MPI_File_write_all_end

[Edgar Gabriel]

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


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.

Thanks!
Edgar


On 7/8/2016 1:14 PM, Eric Chamberland wrote:

On 08/07/16 01:44 PM, Edgar Gabriel wrote:

ok, but just to be able to construct a test case, basically what you are
doing is

MPI_File_write_all_begin (fh, NULL, 0, some datatype);

MPI_File_write_all_end (fh, NULL, ),

is this correct?

Yes, but with 2 processes:

rank 0 writes something, but not rank 1...

other info: rank 0 didn't wait for rank1 after MPI_File_write_all_end so
it continued to the next MPI_File_write_all_begin with a different
datatype but on the same file...

thanks!

Eric
___
devel mailing list
de...@open-mpi.org
Subscription: https://www.open-mpi.org/mailman/listinfo.cgi/devel
Link to this post:
http://www.open-mpi.org/community/lists/devel/2016/07/19173.php

___
devel mailing list
de...@open-mpi.org
Subscription: https://www.open-mpi.org/mailman/listinfo.cgi/devel
Link to this post: 
http://www.open-mpi.org/community/lists/devel/2016/07/19192.php


--
Edgar Gabriel
Associate Professor
Parallel Software Technologies Lab  http://pstl.cs.uh.edu
Department of Computer Science  University of Houston
Philip G. Hoffman Hall, Room 524Houston, TX-77204, USA
Tel: +1 (713) 743-3857  Fax: +1 (713) 743-3335
--

Re: [OMPI devel] [OMPI users] Class information in OpenMPI

[Emani, Murali]

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 doxygen docs are probably the best you'll get, but
>they're really only the utility classes in the portability layer.  They
>don't really include the message passing stuff, nor much (anything?) in
>the ORTE or OMPI layers.  :-\
>
>
>
>> On Jul 12, 2016, at 3:07 PM, Emani, Murali  wrote:
>> 
>> 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 html to extract this info.
>> 
>> ‹ 
>> Murali
>> 
>> 
>> From: devel  on behalf of Ralph Castain
>>
>> Reply-To: Open MPI Developers 
>> Date: Thursday, July 7, 2016 at 3:18 PM
>> To: Open MPI Users 
>> Cc: Open MPI Developers 
>> Subject: Re: [OMPI devel] [OMPI users] Class information in OpenMPI
>> 
>> We used to have Doxygen support that would create what you are asking
>>for, but I don¹t think anyone has maintained it in a long time. I ran
>>³doxygen² at the top-level directory and it did indeed generate a bunch
>>of html, but I¹m not sure it is all that helpful.
>> 
>> You might take a look and see if it helps enough to be useful. Could be
>>that someone will contribute updated Doxygen support to make it betterŠ
>> 
>> 
>>> On Jul 7, 2016, at 11:57 AM, Emani, Murali  wrote:
>>> 
>>> Hi all,
>>> 
>>> I want to know if there is ³class diagram² for OpenMPI code base that
>>>shows existing classes and dependencies/associations. Are there any
>>>available tools to extract and visualize this information.
>>> 
>>> 
>>> ‹ 
>>> Murali
>>> 
>>> ___
>>> users mailing list
>>> us...@open-mpi.org
>>> Subscription: https://www.open-mpi.org/mailman/listinfo.cgi/users
>>> Link to this post:
>>>http://www.open-mpi.org/community/lists/users/2016/07/29594.php
>> 
>> ___
>> users mailing list
>> us...@open-mpi.org
>> Subscription: https://www.open-mpi.org/mailman/listinfo.cgi/users
>> Link to this post:
>>http://www.open-mpi.org/community/lists/users/2016/07/29649.php
>
>
>-- 
>Jeff Squyres
>jsquy...@cisco.com
>For corporate legal information go to:
>http://www.cisco.com/web/about/doing_business/legal/cri/
>
>___
>devel mailing list
>de...@open-mpi.org
>Subscription: https://www.open-mpi.org/mailman/listinfo.cgi/devel
>Link to this post:
>http://www.open-mpi.org/community/lists/devel/2016/07/19191.php

Re: [OMPI devel] [OMPI users] Class information in OpenMPI

[Jeff Squyres (jsquyres)]

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 really include 
the message passing stuff, nor much (anything?) in the ORTE or OMPI layers.  :-\



> On Jul 12, 2016, at 3:07 PM, Emani, Murali  wrote:
> 
> 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 html to extract this info.
> 
> — 
> Murali
> 
> 
> From: devel  on behalf of Ralph Castain 
> 
> Reply-To: Open MPI Developers 
> Date: Thursday, July 7, 2016 at 3:18 PM
> To: Open MPI Users 
> Cc: Open MPI Developers 
> Subject: Re: [OMPI devel] [OMPI users] Class information in OpenMPI
> 
> We used to have Doxygen support that would create what you are asking for, 
> but I don’t think anyone has maintained it in a long time. I ran “doxygen” at 
> the top-level directory and it did indeed generate a bunch of html, but I’m 
> not sure it is all that helpful.
> 
> You might take a look and see if it helps enough to be useful. Could be that 
> someone will contribute updated Doxygen support to make it better…
> 
> 
>> On Jul 7, 2016, at 11:57 AM, Emani, Murali  wrote:
>> 
>> Hi all,
>> 
>> I want to know if there is “class diagram” for OpenMPI code base that shows 
>> existing classes and dependencies/associations. Are there any available 
>> tools to extract and visualize this information.
>> 
>> 
>> — 
>> Murali
>> 
>> ___
>> users mailing list
>> us...@open-mpi.org
>> Subscription: https://www.open-mpi.org/mailman/listinfo.cgi/users
>> Link to this post: 
>> http://www.open-mpi.org/community/lists/users/2016/07/29594.php
> 
> ___
> users mailing list
> us...@open-mpi.org
> Subscription: https://www.open-mpi.org/mailman/listinfo.cgi/users
> Link to this post: 
> http://www.open-mpi.org/community/lists/users/2016/07/29649.php


-- 
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to: 
http://www.cisco.com/web/about/doing_business/legal/cri/

Re: [OMPI devel] Class information in OpenMPI

[Emani, Murali]

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 by my hands with the help of Autodia.
>
>  http://www.aarontrevena.co.uk/opensource/autodia/
>
>> I want to know if there is ³class diagram² for OpenMPI code base that
>>shows existing classes and dependencies/associations. Are there any
>>available tools to extract and visualize this information.
>
>Thanks,
>KAWASHIMA Takahiro
>___
>devel mailing list
>de...@open-mpi.org
>Subscription: https://www.open-mpi.org/mailman/listinfo.cgi/devel
>Link to this post:
>http://www.open-mpi.org/community/lists/devel/2016/07/19168.php

Re: [OMPI devel] [OMPI users] Class information in OpenMPI

[Emani, Murali]

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 html to extract this info.

—
Murali


From: devel > on 
behalf of Ralph Castain >
Reply-To: Open MPI Developers >
List-Post: devel@lists.open-mpi.org
Date: Thursday, July 7, 2016 at 3:18 PM
To: Open MPI Users >
Cc: Open MPI Developers >
Subject: Re: [OMPI devel] [OMPI users] Class information in OpenMPI

We used to have Doxygen support that would create what you are asking for, but 
I don’t think anyone has maintained it in a long time. I ran “doxygen” at the 
top-level directory and it did indeed generate a bunch of html, but I’m not 
sure it is all that helpful.

You might take a look and see if it helps enough to be useful. Could be that 
someone will contribute updated Doxygen support to make it better…


On Jul 7, 2016, at 11:57 AM, Emani, Murali 
> wrote:

Hi all,

I want to know if there is “class diagram” for OpenMPI code base that shows 
existing classes and dependencies/associations. Are there any available tools 
to extract and visualize this information.


—
Murali

___
users mailing list
us...@open-mpi.org
Subscription: https://www.open-mpi.org/mailman/listinfo.cgi/users
Link to this post: 
http://www.open-mpi.org/community/lists/users/2016/07/29594.php

Re: [OMPI devel] [2.0.0rc4] non-critical faulres report

[Paul Hargrove]

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) <
> jsquy...@cisco.com> wrote:
>
>> 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 Pritchard 
>> wrote:
>> > 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 here for completeness.
>> >
>> > Known, but with later target:
>> >
>> > OpenBSD fails to build ROMIO - PR1178 exists with v2.0.1 target
>> > NAG Fortran support - PR1215 exists with v2.0.1 target
>> >
>> > Known, but *not* suspected to be the fault of Open MPI or it embedded
>> components:
>> >
>> > Pathcc gets ICE - versions 5.0.5 and 6.0.527 get compiler crashes
>> building Open MPI
>> > Pgcc -m32 gets ICE - versions 12.x and 13.x (the only ones I can test
>> w/ -m32) crash compiling hwloc
>> >
>> > -Paul
>> >
>> > --
>> > Paul H. Hargrove  phhargr...@lbl.gov
>> > Computer Languages & Systems Software (CLaSS) Group
>> > Computer Science Department   Tel: +1-510-495-2352
>> > Lawrence Berkeley National Laboratory Fax: +1-510-486-6900
>> >
>> > ___
>> > devel mailing list
>> > de...@open-mpi.org
>> > Subscription: https://www.open-mpi.org/mailman/listinfo.cgi/devel
>> > Link to this post:
>> http://www.open-mpi.org/community/lists/devel/2016/07/19155.php
>> >
>> >
>> > ___
>> > devel mailing list
>> > de...@open-mpi.org
>> > Subscription: https://www.open-mpi.org/mailman/listinfo.cgi/devel
>> > Link to this post:
>> http://www.open-mpi.org/community/lists/devel/2016/07/19181.php
>> >
>> >
>> >
>> > --
>> > Paul H. Hargrove  phhargr...@lbl.gov
>> > Computer Languages & Systems Software (CLaSS) Group
>> > Computer Science Department   Tel: +1-510-495-2352
>> > Lawrence Berkeley National Laboratory Fax: +1-510-486-6900
>> > ___
>> > devel mailing list
>> > de...@open-mpi.org
>> > Subscription: https://www.open-mpi.org/mailman/listinfo.cgi/devel
>> > Link to this post:
>> http://www.open-mpi.org/community/lists/devel/2016/07/19182.php
>>
>>
>> --
>> Jeff Squyres
>> jsquy...@cisco.com
>> For corporate legal information go to:
>> http://www.cisco.com/web/about/doing_business/legal/cri/
>>
>> ___
>> devel mailing list
>> de...@open-mpi.org
>> Subscription: https://www.open-mpi.org/mailman/listinfo.cgi/devel
>> Link to this post:
>> http://www.open-mpi.org/community/lists/devel/2016/07/19183.php
>>
>
>
>
> --
> Paul H. Hargrove  phhargr...@lbl.gov
> Computer Languages & Systems Software (CLaSS) Group
> Computer Science Department   Tel: +1-510-495-2352
> Lawrence Berkeley National Laboratory Fax: +1-510-486-6900
>



-- 
Paul H. Hargrove  phhargr...@lbl.gov
Computer Languages & Systems Software (CLaSS) Group
Computer Science Department   Tel: +1-510-495-2352
Lawrence Berkeley National Laboratory Fax: +1-510-486-6900

Re: [OMPI devel] [2.0.0rc4] non-critical faulres report

[Paul Hargrove]

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 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 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 here for completeness.
> >
> > Known, but with later target:
> >
> > OpenBSD fails to build ROMIO - PR1178 exists with v2.0.1 target
> > NAG Fortran support - PR1215 exists with v2.0.1 target
> >
> > Known, but *not* suspected to be the fault of Open MPI or it embedded
> components:
> >
> > Pathcc gets ICE - versions 5.0.5 and 6.0.527 get compiler crashes
> building Open MPI
> > Pgcc -m32 gets ICE - versions 12.x and 13.x (the only ones I can test w/
> -m32) crash compiling hwloc
> >
> > -Paul
> >
> > --
> > Paul H. Hargrove  phhargr...@lbl.gov
> > Computer Languages & Systems Software (CLaSS) Group
> > Computer Science Department   Tel: +1-510-495-2352
> > Lawrence Berkeley National Laboratory Fax: +1-510-486-6900
> >
> > ___
> > devel mailing list
> > de...@open-mpi.org
> > Subscription: https://www.open-mpi.org/mailman/listinfo.cgi/devel
> > Link to this post:
> http://www.open-mpi.org/community/lists/devel/2016/07/19155.php
> >
> >
> > ___
> > devel mailing list
> > de...@open-mpi.org
> > Subscription: https://www.open-mpi.org/mailman/listinfo.cgi/devel
> > Link to this post:
> http://www.open-mpi.org/community/lists/devel/2016/07/19181.php
> >
> >
> >
> > --
> > Paul H. Hargrove  phhargr...@lbl.gov
> > Computer Languages & Systems Software (CLaSS) Group
> > Computer Science Department   Tel: +1-510-495-2352
> > Lawrence Berkeley National Laboratory Fax: +1-510-486-6900
> > ___
> > devel mailing list
> > de...@open-mpi.org
> > Subscription: https://www.open-mpi.org/mailman/listinfo.cgi/devel
> > Link to this post:
> http://www.open-mpi.org/community/lists/devel/2016/07/19182.php
>
>
> --
> Jeff Squyres
> jsquy...@cisco.com
> For corporate legal information go to:
> http://www.cisco.com/web/about/doing_business/legal/cri/
>
> ___
> devel mailing list
> de...@open-mpi.org
> Subscription: https://www.open-mpi.org/mailman/listinfo.cgi/devel
> Link to this post:
> http://www.open-mpi.org/community/lists/devel/2016/07/19183.php
>



-- 
Paul H. Hargrove  phhargr...@lbl.gov
Computer Languages & Systems Software (CLaSS) Group
Computer Science Department   Tel: +1-510-495-2352
Lawrence Berkeley National Laboratory Fax: +1-510-486-6900

[OMPI devel] Added "known issues" section to NEWS

[Jeff Squyres (jsquyres)]

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.cisco.com/web/about/doing_business/legal/cri/

[OMPI devel] SHMEM, "mpp/shmem.fh", CMake and infinite loops

[Paul Kapinos]

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 significnat content is this line:
>  include 'shmem.fh'
whereby OpenMPI mean to include not the same file by itself (= infinite loop!) 
but I believe these one file:

> openmpi-1.X.Y/oshmem/include/shmem.fh

(The above paths are in the source code distributions; in the installation the 
files are located here:  include/shmem.fh  include/mpp/shmem.fh)



This works. Unless you start using CMake. Because CMake is 'intelligent' and try 
to add the search paths recursively, (I believe,) gloriously enabling the 
infinite loop by including the 'shmem.fh' file from the 'shmem.fh' file.


Steps to repriduce:
$ mkdir build; cd build; cmake ..
$ make

The second one command need some minute(s), sticking by the 'Scanning 
dependencies of target mpihelloworld' step.


If connecting by 'strace -p ' to the 'cmake' process you will see lines 
like below, again and again. So I think CMake just include the 'shmem.fh' file 
from itself unless the stack is full / a limit is reached / the moon shines, and 
thus hangs for a while (seconds/minutes) in the 'Scanning dependencies...' state.


*Well, maybe having a file including the same file is not that good?*
If the file 'include/mpp/shmem.fh' would include not 'shmem.fh' but 
'somethingelse.fh' located in 'include/...' these infinite loop would be 
impossible at all...


And by the way: is here a way to limit the maximum include depths in CMake for 
header files? This would workaround this one 'infinite include loop' issue...


Have a nice day,

Paul Kapinos

..
access("/opt/MPI/openmpi-1.10.2/linux/intel_16.0.2.181/include/mpp/shmem.fh", 
R_OK) = 0
stat("/opt/MPI/openmpi-1.10.2/linux/intel_16.0.2.181/include/mpp/shmem.fh", 
{st_mode=S_IFREG|0644, st_size=205, ...}) = 0
open("/opt/MPI/openmpi-1.10.2/linux/intel_16.0.2.181/include/mpp/shmem.fh", 
O_RDONLY) = 5271

fstat(5271, {st_mode=S_IFREG|0644, st_size=205, ...}) = 0
mmap(NULL, 32768, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x7f08457d2000

read(5271, "!\n!   Copyright (c) 2013  Me"..., 32768) = 205
read(5271, "", 32768)   = 0

access("/opt/MPI/openmpi-1.10.2/linux/intel_16.0.2.181/include/mpp/shmem.fh", 
R_OK) = 0
stat("/opt/MPI/openmpi-1.10.2/linux/intel_16.0.2.181/include/mpp/shmem.fh", 
{st_mode=S_IFREG|0644, st_size=205, ...}) = 0
open("/opt/MPI/openmpi-1.10.2/linux/intel_16.0.2.181/include/mpp/shmem.fh", 
O_RDONLY) = 5272

fstat(5272, {st_mode=S_IFREG|0644, st_size=205, ...}) = 0
mmap(NULL, 32768, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x7f08457ca000

read(5272, "!\n!   Copyright (c) 2013  Me"..., 32768) = 205
read(5272, "", 32768)   = 0
..

--
Dipl.-Inform. Paul Kapinos   -   High Performance Computing,
RWTH Aachen University, IT Center
Seffenter Weg 23,  D 52074  Aachen (Germany)
Tel: +49 241/80-24915
cmake_minimum_required(VERSION 2.8)
project(mpihelloworld)
enable_language(Fortran)
find_package(MPI REQUIRED)

#include_directories(${MPI_INCLUDE_PATH})
include_directories(${MPI_Fortran_INCLUDE_PATH})

add_executable(mpihelloworld mpihelloworld.F90)
#link_directories(${MPI_LIBRARIES})
#target_link_libraries(mpihelloworld ${MPI_LIBRARIES})

link_directories(${MPI_Fortran_LIBRARIES})
target_link_libraries(mpihelloworld ${MPI_Fortran_LIBRARIES})
! Paul Kapinos 22.09.2009 - 
! RZ RWTH Aachen, www.rz.rwth-aachen.de
!
! MPI-Hello-World
!
PROGRAM PK_MPI_Test

! USE MPI
IMPLICIT NONE
include "mpif.h"
#if defined(SHMEM)
INCLUDE "mpp/shmem.fh"
#endif

!
INTEGER :: my_MPI_Rank, laenge, ierr
CHARACTER*(MPI_MAX_PROCESSOR_NAME) my_Host

CALL MPI_INIT (ierr)
CALL MPI_COMM_RANK( MPI_COMM_WORLD, my_MPI_Rank, ierr )
CALL MPI_GET_PROCESSOR_NAME(my_Host, laenge, ierr)
WRITE (*,*) "Prozessor ", my_MPI_Rank, "on Host: ", my_Host(1:laenge)

CALL Sleep(1)

CALL MPI_FINALIZE(ierr)

CONTAINS

SUBROUTINE foo1
#if defined(SHMEM)
INCLUDE "mpp/shmem.fh"
#endif
END SUBROUTINE foo1

SUBROUTINE foo2
#if defined(SHMEM)
INCLUDE "mpp/shmem.fh"
#endif
END SUBROUTINE foo2

SUBROUTINE foo3
#if defined(SHMEM)
INCLUDE "mpp/shmem.fh"
#endif
END SUBROUTINE foo3

SUBROUTINE foo4
#if defined(SHMEM)
INCLUDE "mpp/shmem.fh"
#endif
END SUBROUTINE foo4

SUBROUTINE foo5
#if defined(SHMEM)
INCLUDE "mpp/shmem.fh"
#endif
END SUBROUTINE foo5


END PROGRAM PK_MPI_Test


smime.p7s
Description: S/MIME Cryptographic Signature

Re: [OMPI devel] [2.0.0rc4] non-critical faulres report

[Jeff Squyres (jsquyres)]

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 Pritchard  wrote:
> 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 here for completeness.
> 
> Known, but with later target:
> 
> OpenBSD fails to build ROMIO - PR1178 exists with v2.0.1 target
> NAG Fortran support - PR1215 exists with v2.0.1 target
> 
> Known, but *not* suspected to be the fault of Open MPI or it embedded 
> components:
> 
> Pathcc gets ICE - versions 5.0.5 and 6.0.527 get compiler crashes building 
> Open MPI
> Pgcc -m32 gets ICE - versions 12.x and 13.x (the only ones I can test w/ 
> -m32) crash compiling hwloc
> 
> -Paul
> 
> -- 
> Paul H. Hargrove  phhargr...@lbl.gov
> Computer Languages & Systems Software (CLaSS) Group
> Computer Science Department   Tel: +1-510-495-2352
> Lawrence Berkeley National Laboratory Fax: +1-510-486-6900
> 
> ___
> devel mailing list
> de...@open-mpi.org
> Subscription: https://www.open-mpi.org/mailman/listinfo.cgi/devel
> Link to this post: 
> http://www.open-mpi.org/community/lists/devel/2016/07/19155.php
> 
> 
> ___
> devel mailing list
> de...@open-mpi.org
> Subscription: https://www.open-mpi.org/mailman/listinfo.cgi/devel
> Link to this post: 
> http://www.open-mpi.org/community/lists/devel/2016/07/19181.php
> 
> 
> 
> -- 
> Paul H. Hargrove  phhargr...@lbl.gov
> Computer Languages & Systems Software (CLaSS) Group
> Computer Science Department   Tel: +1-510-495-2352
> Lawrence Berkeley National Laboratory Fax: +1-510-486-6900
> ___
> devel mailing list
> de...@open-mpi.org
> Subscription: https://www.open-mpi.org/mailman/listinfo.cgi/devel
> Link to this post: 
> http://www.open-mpi.org/community/lists/devel/2016/07/19182.php


-- 
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to: 
http://www.cisco.com/web/about/doing_business/legal/cri/

Re: [OMPI devel] [2.0.0rc4] non-critical faulres report

[Paul Hargrove]

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 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 here for completeness.
>>
>> Known, but with later target:
>>
>> OpenBSD fails to build ROMIO - PR1178 exists with v2.0.1 target
>> NAG Fortran support - PR1215 exists with v2.0.1 target
>>
>> Known, but *not* suspected to be the fault of Open MPI or it embedded
>> components:
>>
>> Pathcc gets ICE - versions 5.0.5 and 6.0.527 get compiler crashes
>> building Open MPI
>> Pgcc -m32 gets ICE - versions 12.x and 13.x (the only ones I can test w/
>> -m32) crash compiling hwloc
>>
>> -Paul
>>
>> --
>> Paul H. Hargrove  phhargr...@lbl.gov
>> Computer Languages & Systems Software (CLaSS) Group
>> Computer Science Department   Tel: +1-510-495-2352
>> Lawrence Berkeley National Laboratory Fax: +1-510-486-6900
>>
>> ___
>> devel mailing list
>> de...@open-mpi.org
>> Subscription: https://www.open-mpi.org/mailman/listinfo.cgi/devel
>> Link to this post:
>> http://www.open-mpi.org/community/lists/devel/2016/07/19155.php
>>
>
>
> ___
> devel mailing list
> de...@open-mpi.org
> Subscription: https://www.open-mpi.org/mailman/listinfo.cgi/devel
> Link to this post:
> http://www.open-mpi.org/community/lists/devel/2016/07/19181.php
>



-- 
Paul H. Hargrove  phhargr...@lbl.gov
Computer Languages & Systems Software (CLaSS) Group
Computer Science Department   Tel: +1-510-495-2352
Lawrence Berkeley National Laboratory Fax: +1-510-486-6900

Re: [OMPI devel] [2.0.0rc4] non-critical faulres report

[Howard Pritchard]

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 here for completeness.
>
> Known, but with later target:
>
> OpenBSD fails to build ROMIO - PR1178 exists with v2.0.1 target
> NAG Fortran support - PR1215 exists with v2.0.1 target
>
> Known, but *not* suspected to be the fault of Open MPI or it embedded
> components:
>
> Pathcc gets ICE - versions 5.0.5 and 6.0.527 get compiler crashes building
> Open MPI
> Pgcc -m32 gets ICE - versions 12.x and 13.x (the only ones I can test w/
> -m32) crash compiling hwloc
>
> -Paul
>
> --
> Paul H. Hargrove  phhargr...@lbl.gov
> Computer Languages & Systems Software (CLaSS) Group
> Computer Science Department   Tel: +1-510-495-2352
> Lawrence Berkeley National Laboratory Fax: +1-510-486-6900
>
> ___
> devel mailing list
> de...@open-mpi.org
> Subscription: https://www.open-mpi.org/mailman/listinfo.cgi/devel
> Link to this post:
> http://www.open-mpi.org/community/lists/devel/2016/07/19155.php
>

Re: [OMPI devel] RFC: remove --disable-smp-locks

[Sreenidhi Bharathkar Ramesh]

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: [OMPI devel] RFC: remove --disable-smp-locks

[ 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
benchmarks actually degraded when "--disable-smp-locks" was used.  Hence,
asking.

Please let me know.

Thanks,
- Sreenidhi.

- - - -

Subject: Re: [OMPI devel] RFC: remove --disable-smp-locks
From: Jeff Squyres (jsquyres) (jsquyres_at_[hidden])
List-Post: devel@lists.open-mpi.org
Date: 2015-01-07 14:14:30
Added to the wiki / agenda.
On Jan 7, 2015, at 11:35 AM, Nathan Hjelm  wrote:
>
> I think this is a good discussion for the Dallas meeting. We can hold
> off on this RFC until then.
>
> -Nathan
>
> On Tue, Jan 06, 2015 at 06:16:39PM -0500, George Bosilca wrote:
>> On Tue, Jan 6, 2015 at 4:25 PM, Jeff Squyres (jsquyres)
>>  wrote:
>>
>> My enthusiasm for this was primarily because I thought we had talked
>> about exactly this issue before (at the last meeting in Chicago?),
>> and decided that the option is useless -- in part, because it always
>> *must* be enabled for shared memory correctness.
>>
>> Is that incorrect?
>>
>> This is correct. We need the memory fences and atomic operations for
>> shared memory in all cases. When thread support is enabled we also
>> need them in various other places. However, this option also turns on
>> the lock prefix for the atomic operations, forcing them to always be
>> atomic. I am not sure that this has no unexpected side-effects on the
>> code.
>> George.
>>
>>
>> On Jan 6, 2015, at 4:12 PM, George Bosilca 
>> wrote:
>>
>>> Successive alteration of the build system made this option less
>> relevant and especially less meaningful. However, while removing it
>> sounds like a desirable cleanup, we have to keep in mind that this
>> will enable all locks and all memory barriers even in cases where
>> they are not necessary (via OPAL_WANT_SMP_LOCKS).
>>>
>>> Thus, I do not share the enthusiasm of the others. I would prefer to
>> see an evaluation of the impact on performance, a patch and a little
>> bit more than 1/2 a day to react to it (the proposed deadline seems
>> to be today January 6th) before such a drastic change.
>>>
>>> George.
>>>
>>>
>>> On Tue, Jan 6, 2015 at 12:05 PM, Ralph Castain 
>> wrote:
>>> +1
>>>
 On Jan 6, 2015, at 9:04 AM, Jeff Squyres (jsquyres)
>>  wrote:

 +1

 On Jan 6, 2015, at 11:55 AM, Howard Pritchard
 
>> wrote:

> I agree. Please remove this config option.
>
> 2015-01-06 9:44 GMT-07:00 Nathan Hjelm :
>
> What: Remove the --disable-smp-locks configure option from master.
>
> Why: Use of this option produces incorrect results/undefined
>> behavior
> when any shared memory BTL is in use. Since BTL usage is enabled
>> even
> when using cm for point-to-point this option can never be safely
>> used.
>
> When: Thurs, Jan 6, 2015
>
> -Nathan

Re: [OMPI devel] RFC: remove --disable-smp-locks

[Nathan Hjelm]

> 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 option is it made the 
opal_atomic_* functions non-atomic (on x86 at least). That is fine if there is 
only a single core in use on a node but caused problems with shared memory 
communication. The shared memory transports absolutely need the atomics to be 
atomic to work correctly. This RFC came up because users were trying to use the 
option and were running into issues. Made sense to just kill it.

> 2. Under what circumstances would "--disable-smp-locks" be useful ?
> In our experiments on ARM64 platform, it was seen that OSU Micro collective
> benchmarks actually degraded when "--disable-smp-locks" was used.  Hence,
> asking.

The optimization was likely meant for MPI_THREAD_SINGLE. The problem is we 
already optimize that case with the OPAL_THREAD_* macros which use atomics only 
if threads are in use. Others may be able to explain the intent.

-Nathan

Re: [OMPI devel] RFC: remove --disable-smp-locks

[Sreenidhi Bharathkar Ramesh]

[ 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
benchmarks actually degraded when "--disable-smp-locks" was used.  Hence,
asking.

Please let me know.

Thanks,
- Sreenidhi.

- - - -

Subject: Re: [OMPI devel] RFC: remove --disable-smp-locks
From: Jeff Squyres (jsquyres) (jsquyres_at_[hidden])
List-Post: devel@lists.open-mpi.org
Date: 2015-01-07 14:14:30
Added to the wiki / agenda.
On Jan 7, 2015, at 11:35 AM, Nathan Hjelm  wrote:
>
> I think this is a good discussion for the Dallas meeting. We can hold
> off on this RFC until then.
>
> -Nathan
>
> On Tue, Jan 06, 2015 at 06:16:39PM -0500, George Bosilca wrote:
>> On Tue, Jan 6, 2015 at 4:25 PM, Jeff Squyres (jsquyres)
>>  wrote:
>>
>> My enthusiasm for this was primarily because I thought we had talked
>> about exactly this issue before (at the last meeting in Chicago?), and
>> decided that the option is useless -- in part, because it always *must*
>> be enabled for shared memory correctness.
>>
>> Is that incorrect?
>>
>> This is correct. We need the memory fences and atomic operations for
>> shared memory in all cases. When thread support is enabled we also need
>> them in various other places. However, this option also turns on the lock
>> prefix for the atomic operations, forcing them to always be atomic. I am
>> not sure that this has no unexpected side-effects on the code.
>> George.
>>
>>
>> On Jan 6, 2015, at 4:12 PM, George Bosilca  wrote:
>>
>>> Successive alteration of the build system made this option less
>> relevant and especially less meaningful. However, while removing it
>> sounds like a desirable cleanup, we have to keep in mind that this will
>> enable all locks and all memory barriers even in cases where they are
>> not necessary (via OPAL_WANT_SMP_LOCKS).
>>>
>>> Thus, I do not share the enthusiasm of the others. I would prefer to
>> see an evaluation of the impact on performance, a patch and a little bit
>> more than 1/2 a day to react to it (the proposed deadline seems to be
>> today January 6th) before such a drastic change.
>>>
>>> George.
>>>
>>>
>>> On Tue, Jan 6, 2015 at 12:05 PM, Ralph Castain 
>> wrote:
>>> +1
>>>
 On Jan 6, 2015, at 9:04 AM, Jeff Squyres (jsquyres)
>>  wrote:

 +1

 On Jan 6, 2015, at 11:55 AM, Howard Pritchard 
>> wrote:

> I agree. Please remove this config option.
>
> 2015-01-06 9:44 GMT-07:00 Nathan Hjelm :
>
> What: Remove the --disable-smp-locks configure option from master.
>
> Why: Use of this option produces incorrect results/undefined
>> behavior
> when any shared memory BTL is in use. Since BTL usage is enabled
>> even
> when using cm for point-to-point this option can never be safely
>> used.
>
> When: Thurs, Jan 6, 2015
>
> -Nathan