[petsc-dev] -with-kokkos-cuda-arch=AMPERE80 nonsense

It would be very nice to NOT require PETSc users to provide this flag, how the heck will they know what it should be when we cannot automate it ourselves? Any ideas of how this can be determined based on the current system? NVIDIA does not help since these "advertising" names don't seem

Re: [petsc-dev] Regression in manualpages generation?

I think this was likely a non-portable regex that was being used to match the function signatures, causing it to miss anything with an internal "s" in the function name. Here's a quick fix for the release branch: https://gitlab.com/petsc/petsc/-/merge_requests/3813 (This sort of thing will

Re: [petsc-dev] Regression in manualpages generation?

That isn't expected - thanks for pointing this out! I can reproduce locally so will take a look. > Am 03.04.2021 um 11:10 schrieb Pierre Jolivet : > > Hello, > https://www.mcs.anl.gov/petsc/petsc-3.14/docs/manualpages/Mat/MatTranspose.html > >

[petsc-dev] Regression in manualpages generation?

Hello, https://www.mcs.anl.gov/petsc/petsc-3.14/docs/manualpages/Mat/MatTranspose.html lists available implementations while https://www.mcs.anl.gov/petsc/petsc-3.15/docs/manualpages/Mat/MatTranspose.html