[petsc-users] Problems with DMDAVecGetArrayF90 + Intel

[Randall Mackie]

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 --------------
A non-text attachment was scrubbed...
Name: cmd_test
Type: application/octet-stream
Size: 63 bytes
Desc: not available
URL: <http://lists.mcs.anl.gov/pipermail/petsc-users/attachments/20180405/8b0f1a37/attachment.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: makefile
Type: application/octet-stream
Size: 370 bytes
Desc: not available
URL: <http://lists.mcs.anl.gov/pipermail/petsc-users/attachments/20180405/8b0f1a37/attachment-0001.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: test.F90
Type: application/octet-stream
Size: 2507 bytes
Desc: not available
URL: <http://lists.mcs.anl.gov/pipermail/petsc-users/attachments/20180405/8b0f1a37/attachment-0002.obj>