[petsc-users] error on Spock

Junchao Zhang junchao.zhang at gmail.com
Tue Jul 13 21:19:05 CDT 2021


Barry, the flags Mark used are required per Spock document. This is a test
platform and the software environment is immature.

 --Junchao Zhang


On Tue, Jul 13, 2021 at 9:09 PM Barry Smith <bsmith at petsc.dev> wrote:

>
>   The expected behavior on Cray systems is you load "appropriate" modules
> and then run ./configure without needing to provide compiler and MPI
> information and it "just works".
>
>   So one should not need to provide --with-cc=cc --with-cxx=CC
> --with-fc=ftn on Cray systems. Loading "appropriate" modules is suppose to
> define the compilers (and MPI) you want to use so on should not need to be
> passed manually to PETSc's configure this kind of information.
>
>   The --HIPPPFLAGS=-I/opt/cray/pe/mpich/8.1.4/ofi/crayclang/9.1include is
> horrific. needing to have pass MPI information to the HIP compiler likely
> means PETSc does not have a proper separation of HIP code from "plain old C
> code" that is mistakenly put in hip files. This is definitely currently
> true with CUDA and likely carried over to the HIP interfaces. (.i.e. most
> of the functions in the .cu files in PETSc should just be in .c files).
>
>   The various rocm information should be handled automatically by
> ./configure and not be required to be provided by users. As it is currently
> handled for the CUDA libraries such as cubBLAS and cuSparse.
>
>
>
>
>
> > On Jul 13, 2021, at 4:47 PM, Mark Adams <mfadams at lbl.gov> wrote:
> >
> >
> > <make.log><configure.log>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-users/attachments/20210713/e5d53aec/attachment.html>


More information about the petsc-users mailing list