Re: [OMPI devel] [EXTERNAL] Which compiler versions to test?

[Baker, Lawrence M via devel]

Jeff,

The PGI/nVidia compiler suite is free now and could become more significant in 
the ARM world, now that nVidia has acquired ARM.  We use PGI on our cluster, 
along with the others you support.

Larry Baker
US Geological Survey
650-329-5608
ba...@usgs.gov



On Oct 7 2020, at 1:42:16 PM, Jeff Squyres (jsquyres) via devel 
mailto:devel@lists.open-mpi.org>> wrote:



This email has been received from outside of DOI - Use caution before clicking 
on links, opening attachments, or responding.



Open question to the Open MPI dev community...

Over time, the size of my MTT cluster has been growing smaller (due to hardware 
failure, power budget restrictions, etc.).  This means that I have far fewer 
CPU cycles available for testing various compilers and configure CLI options 
than I used to.

What compilers does the community think are worthwhile to test these days?  I 
generally have access to gcc/gfortran, clang, and some versions of the Intel 
compiler suite.

master, 4.0.x, and 4.1.x branches
- gcc 4.8.5 (i.e., the default gcc on RHEL 7.x)
- gcc 9.latest
- gcc 10.latest
- clang 9.0.latest
- clang 10.0.latest
- Intel 2017
- Intel 2019

(I don't have Intel 2018 or Intel 2020)

Is this sufficient?  Or is it worthwhile to test other versions of these 
compilers?

--
Jeff Squyres
jsquy...@cisco.com




Larry Baker
US Geological Survey
650-329-5608
ba...@usgs.gov

Re: [OMPI devel] Which compiler versions to test?

[Gilles Gouaillardet via devel]

Hi Jeff,

On RHEL 8.x, the default gcc compiler is 8.3.1, so I think it is worth testing.

Containers could be used to setup a RHEL 8.x environment (so not only
gcc but also third party libs such as libevent and hwloc can be used)
if the MTT cluster will not shrink bigger.

Cheers,

Gilles

On Fri, Oct 9, 2020 at 1:28 AM Jeff Squyres (jsquyres) via devel
 wrote:
>
> Open question to the Open MPI dev community...
>
> Over time, the size of my MTT cluster has been growing smaller (due to 
> hardware failure, power budget restrictions, etc.).  This means that I have 
> far fewer CPU cycles available for testing various compilers and configure 
> CLI options than I used to.
>
> What compilers does the community think are worthwhile to test these days?  I 
> generally have access to gcc/gfortran, clang, and some versions of the Intel 
> compiler suite.
>
> master, 4.0.x, and 4.1.x branches
> - gcc 4.8.5 (i.e., the default gcc on RHEL 7.x)
> - gcc 9.latest
> - gcc 10.latest
> - clang 9.0.latest
> - clang 10.0.latest
> - Intel 2017
> - Intel 2019
>
> (I don't have Intel 2018 or Intel 2020)
>
> Is this sufficient?  Or is it worthwhile to test other versions of these 
> compilers?
>
> --
> Jeff Squyres
> jsquy...@cisco.com
>

Re: [OMPI devel] Open MPI 3rd party packaging changes

[Orion Poplawski via devel]

On 10/1/20 1:43 PM, Barrett, Brian via devel wrote:

All -

Only 6 months after I promised the code would be done, the changes we discussed in February around 3rd party 
packages (Libevent, HWLOC, PMIx, and PRRTE) are merged to master.  With these changes, Open MPI will prefer 
an external version of any of those packages if a "new enough" version is found already installed 
on the system.  New enough is no longer defined as "newer than the built-in package", but is 
defined as "as new as the oldest version we know works".  This may cause unexpected changes from 
using the built-in versions to the system versions for some packages, particularly libevent.

If you have Libevent and hwloc pre-installed, your total build times will go 
down a couple percent, so there's that :).

Brian



Thank you.

Orion

--
Orion Poplawski
Manager of NWRA Technical Systems  720-772-5637
NWRA, Boulder/CoRA Office FAX: 303-415-9702
3380 Mitchell Lane   or...@nwra.com
Boulder, CO 80301 https://www.nwra.com/



smime.p7s
Description: S/MIME Cryptographic Signature

[OMPI devel] Which compiler versions to test?

[Jeff Squyres (jsquyres) via devel]

Open question to the Open MPI dev community...

Over time, the size of my MTT cluster has been growing smaller (due to hardware 
failure, power budget restrictions, etc.).  This means that I have far fewer 
CPU cycles available for testing various compilers and configure CLI options 
than I used to.

What compilers does the community think are worthwhile to test these days?  I 
generally have access to gcc/gfortran, clang, and some versions of the Intel 
compiler suite.

master, 4.0.x, and 4.1.x branches
- gcc 4.8.5 (i.e., the default gcc on RHEL 7.x)
- gcc 9.latest
- gcc 10.latest
- clang 9.0.latest
- clang 10.0.latest
- Intel 2017
- Intel 2019

(I don't have Intel 2018 or Intel 2020)

Is this sufficient?  Or is it worthwhile to test other versions of these 
compilers?

-- 
Jeff Squyres
jsquy...@cisco.com