Re: [petsc-dev] sm_70

I have added the configure option --with-cuda-gencodearch=XX to pass down such information to the external packages build. We are not currently using it in the library itself. Il Sab 26 Set 2020, 06:08 Barry Smith ha scritto: > > > On Sep 25, 2020, at 8:36 PM, Jacob Faibussowitsch > wrote: > >

Re: [petsc-dev] sm_70

> On Sep 25, 2020, at 8:36 PM, Jacob Faibussowitsch wrote: > >> Configure by default should find out the available GPU and build for that >> sm_* it should not require the user to set this (how the heck is the user >> going to know what to set?) If I remember correctly there is a utility

Re: [petsc-dev] sm_70

> Configure by default should find out the available GPU and build for that > sm_* it should not require the user to set this (how the heck is the user > going to know what to set?) If I remember correctly there is a utility > available that gives this information. For CUDA I believe the too

Re: [petsc-dev] sm_70

Configure by default should find out the available GPU and build for that sm_* it should not require the user to set this (how the heck is the user going to know what to set?) If I remember correctly there is a utility available that gives this information. For generic builds like in pa

Re: [petsc-dev] sm_70

'--CUDAFLAGS=-arch=sm_70', seems to fix this. On Fri, Sep 25, 2020 at 6:31 PM Mark Adams wrote: > I see kokkos and hyper have a sm_70 flag, but I don't see one for PETSc. > > It looks like you have to specify this to get modern atomics to work in > Cuda. I get: > > /ccs/home/adams/petsc/incl

[petsc-dev] sm_70

I see kokkos and hyper have a sm_70 flag, but I don't see one for PETSc. It looks like you have to specify this to get modern atomics to work in Cuda. I get: /ccs/home/adams/petsc/include/petscaijdevice.h(99): error: no instance of overloaded function "atomicAdd" matches the argument list

Re: [petsc-dev] petsc release plan for Sept/2020

Update: CI is currently overloaded, cuda test failures are delaying the pipeline completions. Please do not restart failed stage-3 cuda jobs - if they are CI failures [if the MR has no cuda changes - the failures are very likely CI issues] - and attempt to proceed to get reviews/approvals [as

Re: [petsc-dev] CI failure?

This change is tripping the gcov script. $ git diff origin/master... src/mat/impls/aij/mpi/mmaij.c diff --git a/src/mat/impls/aij/mpi/mmaij.c b/src/mat/impls/aij/mpi/mmaij.c index 79d770b69d..eaf0335e11 100644 --- a/src/mat/impls/aij/mpi/mmaij.c +++ b/src/mat/impls/aij/mpi/mmaij.c @@ -73,7 +73,6 @

Re: [petsc-dev] CI failure?

It looks like a parse of the gcov output failed: Building html files for C 1579 Traceback (most recent call last): 1580 File "/scratch/svcpetsc/glci-builds/LysKu_HD/0/petsc/petsc/lib/pets

[petsc-dev] CI failure?

I don't see the problem here: https://gitlab.com/petsc/petsc/-/jobs/757483850