[petsc-users] Problems with DMDAVecGetArrayF90 + Intel

[Fabian.Jakub]

Hi,

Not sure if this is related to your current issues but
I once had issues with this particular function with IBM XLF compilers
but never got to a solution because...

a) VecGetArrayF90 also worked for me
b) and the IBM Machine got switched off

Anyway, I did not have any issues since then... not with intel nor with
gfortran compilers.

The helpdesk back then created a petsc bug report but I think the issue
was never resolved...

For the sake of completeness, I am attaching the messages we had then,
maybe the debugging efforts are related to your problems?

Good Luck,

Fabian


On 04/05/2018 05:03 PM, Randall Mackie wrote:
> Dear PETSc users,
>
> I’m curious if anyone else experiences problems using
DMDAVecGetArrayF90 in conjunction with Intel compilers?
> We have had many problems (typically 11 SEGV segmentation violations)
when PETSc is compiled in optimize mode (with various combinations of
options).
> These same codes run valgrind clean with gfortran, so I assume this is
an Intel bug, but before we submit a bug report I wanted to see if
anyone else had similar experiences?
> We have basically gone back and replaced our calls to
DMDAVecGetArrayF90 with calls to VecGetArrayF90 and pass those pointers
into a “local” subroutine that works fine.
>
> In case anyone is curious, the attached test code shows this behavior
when PETSc is compiled with the following options:
>
> ./configure \
>   --with-clean=1 \
>   --with-debugging=0 \
>   --with-fortran=1 \
>   --with-64-bit-indices \
>   --download-mpich=../mpich-3.3a2.tar.gz \
>   --with-blas-lapack-dir=/opt/intel/mkl \
>   --with-cc=icc \
>   --with-fc=ifort \
>   --with-cxx=icc \
>   --FOPTFLAGS='-O2 -xSSSE3 -axcore-avx2' \
>   --COPTFLAGS='-O2 -xSSSE3 -axcore-avx2' \
>   --CXXOPTFLAGS='-O2 -xSSSE3 -axcore-avx2’ \
>
>
>
> Thanks, Randy M.
>
-------------- next part --------------
An embedded message was scrubbed...
From: "Fabian.Jakub" <Fabian.Jakub at physik.uni-muenchen.de>
Subject: Problems Using Petsc at Blizzard
Date: Fri, 23 Jan 2015 12:00:47 +0100
Size: 18589
URL: <http://lists.mcs.anl.gov/pipermail/petsc-users/attachments/20180405/ed19cdc8/attachment-0006.eml>
-------------- next part --------------
An embedded message was scrubbed...
From: Hendryk Bockelmann <beratung at dkrz.de>
Subject: Re: Problems Using Petsc at Blizzard
Date: Tue, 27 Jan 2015 11:09:07 +0100
Size: 4151
URL: <http://lists.mcs.anl.gov/pipermail/petsc-users/attachments/20180405/ed19cdc8/attachment-0007.eml>
-------------- next part --------------
An embedded message was scrubbed...
From: Hendryk Bockelmann <beratung at dkrz.de>
Subject: Re: Problems Using Petsc at Blizzard
Date: Wed, 28 Jan 2015 09:56:49 +0100
Size: 3691
URL: <http://lists.mcs.anl.gov/pipermail/petsc-users/attachments/20180405/ed19cdc8/attachment-0008.eml>
-------------- next part --------------
An embedded message was scrubbed...
From: Hendryk Bockelmann <beratung at dkrz.de>
Subject: Re: Problems Using Petsc at Blizzard
Date: Thu, 05 Feb 2015 14:06:14 +0100
Size: 4509
URL: <http://lists.mcs.anl.gov/pipermail/petsc-users/attachments/20180405/ed19cdc8/attachment-0009.eml>
-------------- next part --------------
An embedded message was scrubbed...
From: "Fabian.Jakub" <Fabian.Jakub at physik.uni-muenchen.de>
Subject: Re: Problems Using Petsc at Blizzard
Date: Fri, 13 Feb 2015 17:14:12 +0100
Size: 3095
URL: <http://lists.mcs.anl.gov/pipermail/petsc-users/attachments/20180405/ed19cdc8/attachment-0010.eml>
-------------- next part --------------
An embedded message was scrubbed...
From: Hendryk Bockelmann <beratung at dkrz.de>
Subject: Re: Problems Using Petsc at Blizzard
Date: Mon, 16 Feb 2015 08:13:30 +0100
Size: 5059
URL: <http://lists.mcs.anl.gov/pipermail/petsc-users/attachments/20180405/ed19cdc8/attachment-0011.eml>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: <http://lists.mcs.anl.gov/pipermail/petsc-users/attachments/20180405/ed19cdc8/attachment-0001.sig>