On Feb 11, 2021, at 11:55 AM, Max R. Dechantsreiter
wrote:
>
> Not sure about the latest, but I built v4.1.x-202102090356-380ac96
> without errors, then used that to successfully build andd test
> GROMACS parallel mdrun.
Great!
> While I do not like using non-release versions, this is promisin
On Thu, Feb 11, 2021 at 04:46:44PM +, Jeff Squyres (jsquyres) wrote:
> We did have some issues with 4.1.0 and AVX, but we have fixed everything that
> we were aware of.
>
> I'd be curious to know if you still have build failures in the latest 4.1.x
> nightly snapshot.
Not sure about the lat
We did have some issues with 4.1.0 and AVX, but we have fixed everything that
we were aware of.
I'd be curious to know if you still have build failures in the latest 4.1.x
nightly snapshot.
If you do, can you send the following:
- stdout/stderr from running configure
- config.log
- stdout/stde
...The error that prompted me to start this thread occurred
during "make all" with 4.1.0:
.
.
.
Making all in mca/op/avx
gmake[2]: Entering directory
`/home/maxd/XX/Build/openmpi-4.1.0_gcc-10.2.0/ompi/mca/op/avx'
CC op_avx_component.lo
CC liblocal_ops_avx_la-op_avx
I ran into a problem with 4.1.0 several weeks ago,
and no longer recall precisely how; I am now rebuilding
both 4.1.0 and a recent 4.1.x, then will use them to
build GROMACS, probably the application I was attemping
back then.
But I do have this from my notes (for 4.1.0):
mpicc -fopenmp hybrid_he
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 provid
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 containin
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 co
