On Fri, 7 Oct 2016, Antonio Trande wrote:

> 
> They come out by testing serial PETSc libraries according to reported
> configuration in following log, please, see
> https://paste.fedoraproject.org/445643/
> 

+ make -C petsc-3.7.3 PETSC_DIR=/builddir/build/BUILD/petsc-3.7.3/petsc-3.7.3 
PETSC_ARCH=x86_64 streams

I don't think this is necessary - its primarily for users to verify their 
machine performace - before
analyzing PETSc application performance

+ pushd petsc-3.7.3/src/ksp/ksp/examples/tutorials
~/build/BUILD/petsc-3.7.3/petsc-3.7.3/src/ksp/ksp/examples/tutorials 
~/build/BUILD/petsc-3.7.3
+ make ex50

Or this stuff.. [since 'make test' already does basic non-liner test]



> [0]PETSC ERROR: Configure options --build=x86_64-redhat-linux-gnu 
> --host=x86_64-redhat-linux-gnu --program-prefix= --with-dependency-tracking=0 
> --prefix=/usr --exec-prefix=/usr --bindir=/usr/bin --sbindir=/usr/sbin 
> --sysconfdir=/etc --datadir=/usr/share --includedir=/usr/include 
> --libdir=/usr/lib64 --libexecdir=/usr/libexec --localstatedir=/var 
> --sharedstatedir=/var/lib --mandir=/usr/share/man --infodir=/usr/share/info 
> CFLAGS=-O2 -g -pipe -Wall -Werror=format-security =2 -fexceptions 
> -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches 
> -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -m64 -mtune=generic 
> CXXFLAGS=-O2 -g -pipe -Wall -Werror=format-security =2 -fexceptions 
> -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches 
> -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -m64 -mtune=generic 
> FCFLAGS=-O2 -g -pipe -Wall -Werror=format-security =2 -fexceptions 
> -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches 
> -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -m64 -mtune=generic FFLAGS=-O2 
> -g -pipe -Wall -Werror=format-security =2 -fexceptions 
> -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches 
> -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -m64 -mtune=generic 
> LDFLAGS=-Wl,-z,relro -specs=/usr/lib/rpm/redhat/redhat-hardened-ld 
> --with-default-arch=0 --with-make=1 --with-single-library=1 
> --with-debugging=0 --with-shared-libraries=1 --with-precision=double 
> --with-64-bit-indices=0 --with-petsc-arch=x86_64 --with-clanguage=C 
> --with-shared-libraries=1 --with-64-bit-indices=1 --with-fortran-interfaces=1 
> --with-windows-graphics=0 --CC=gcc --FC=gfortran --with-gnu-compilers=1 
> --with-vendor-compilers=0 --with-shared-ld=ld --with-pic=1 
> --sharedLibraryFlags= --dynamicLibraryFlags= --with-clib-autodetect=0 
> --with-fortranlib-autodetect=0 --with-cxxlib-autodetect=0 --with-mpi=0 
> --with-fc=gfortran --with-mpiuni-fortran-binding=1 --with-threadsafety=0 
> --with-log=1 --with-debugging=0 COPTFLAGS="-O2 -g -pipe -Wall 
> -Werror=format-security =2 -fexceptions -fstack-protector-strong 
> --param=ssp-buffer-size=4 -grecord-gcc-switches 
> -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -m64 -mtune=generic -O3 
> -Wl,-z,relro -specs=/usr/lib/rpm/redhat/redhat-hardened-ld" CXXOPTFLAGS="-O2 
> -g -pipe -Wall -Werror=format-security =2 -fexceptions 
> -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches 
> -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -m64 -mtune=generic -O3" 
> FOPTFLAGS="-O2 -g -pipe -Wall -Werror=format-security =2 -fexceptions 
> -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches 
> -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -m64 -mtune=generic -O3 
> -I/usr/lib64/gfortran/modules" --with-blas-lib=-lopenblas64 
> --with-lapack-lib=-lopenblas64 --with-blas-lapack-suffix= 
> --known-64-bit-blas-indices=1 --with-libjpeg=1 --with-libpng=1 --with-x=1 
> --with-openmp=0 --with-metis=0 --with-hwloc=0 --with-ssl=0 --with-papi=1 
> --with-papi-include= --with-papi-lib=-lpapi --with-cgns=1 --with-pthread=1 
> --with-valgrind=1


Hm --with-64-bit-indices=0 --with-64-bit-indices=1 --with-blas-lib=-lopenblas64 
--with-lapack-lib=-lopenblas64 --known-64-bit-blas-indices=1

Hm - this --known-64-bit-blas-indices=1 was primarily tested with MKL - 
assuming its not isssue with -lopenblas64 [thats triggering the SEGV]

Will check..

Satish

Reply via email to