The proposed fix is #if defined(PETSC_USE_AVX512_KERNELS) && && && && && in
https://gitlab.com/petsc/petsc/merge_requests/2213/diffs
but note that PETSC_USE_AVX512_KERNELS does not even do a configure check to
make sure it is valid. The user has to guess that passing that flag will work.
"Smith, Barry F. via petsc-dev" writes:
>This needs to be fixed properly with a configure test(s) and not with huge
> and inconsistent checks like this
>
> #if defined(PETSC_HAVE_IMMINTRIN_H) && defined(__AVX512F__) &&
> defined(PETSC_USE_REAL_DOUBLE) && !defined(PETSC_USE_COMPLEX) &&
>
https://gitlab.com/petsc/petsc/issues/434
> On Oct 25, 2019, at 9:16 AM, Smith, Barry F. wrote:
>
>
> This needs to be fixed properly with a configure test(s) and not with huge
> and inconsistent checks like this
>
> #if defined(PETSC_HAVE_IMMINTRIN_H) && defined(__AVX512F__) &&
>
This needs to be fixed properly with a configure test(s) and not with huge
and inconsistent checks like this
#if defined(PETSC_HAVE_IMMINTRIN_H) && defined(__AVX512F__) &&
defined(PETSC_USE_REAL_DOUBLE) && !defined(PETSC_USE_COMPLEX) &&
!defined(PETSC_USE_64BIT_INDICES) or this
#elif
I can live with PetscInt instead of PetscMPIInt, this was more of a curiosity I
noticed.
But if no one fixes these, I’ll give it a go in the near future.
Thanks,
Pierre
> On 24 Oct 2019, at 4:47 PM, Smith, Barry F. wrote:
>
>
> These routines should be fixed.
>
>
>> On Oct 16, 2019, at
On Fri, 25 Oct 2019 at 01:40, Balay, Satish wrote:
> I'm curious why this issue comes up for you. The code was unrelated to
> --with-avx512-kernels=0 option.
>
> Its relying on __AVX512F__and PETSC_HAVE_IMMINTRIN_H flags. And
> assumes immintrin.h has a definition for _mm512_reduce_add_pd()
>
>
