Re: [OMPI users] OpenMPI 4.1.0 misidentifies x86 capabilities

I think Max did try the latest 4.1 nightly build (from an off-list email), and his problem still persisted. Max: can you describe exactly how Open MPI failed? All you said was: >> Consequently AVX512 intrinsic functions were erroneously >> deployed, resulting in OpenMPI failure. Can you

[OMPI users] GROMACS with openmpi

Hi, MPI developers and users, I want to run GROMACS using *gmx_mpi* rather than *gmx*, could you give me a hand on how to do that? Thanks a lot! Cheers,

Re: [OMPI users] OpenMPI 4.1.0 misidentifies x86 capabilities

Max, at configure time, Open MPI detects the *compiler* capabilities. In your case, your compiler can emit AVX512 code. (and fwiw, the tests are only compiled and never executed) Then at *runtime*, Open MPI detects the *CPU* capabilities. In your case, it should not invoke the functions

Re: [OMPI users] Issue with MPI_Get_processor_name() in Cygwin

Hello Joseph, Yes, it was just that. However, for some reason it was working on Linux… Thank you very much for your help. Regards, Martín From: Joseph Schuchart via users Sent: martes, 9 de febrero de 2021 17:45 To:

[OMPI users] OpenMPI 4.1.0 misidentifies x86 capabilities

Configuring OpenMPI 4.1.0 with GCC 10.2.0 on Intel(R) Xeon(R) CPU E5-2620 v3, a Haswell processor that supports AVX2 but not AVX512, resulted in checking for AVX512 support (no additional flags)... no checking for AVX512 support (with -march=skylake-avx512)... yes in "configure" output, and in