ierr = VecGetLocalSize(xx,);CHKERRQ(ierr);
if (nt != A->rmap->n)
SETERRQ2(PETSC_COMM_SELF,PETSC_ERR_ARG_SIZ,"Incompatible partition of A (%D)
and xx (%D)",A->rmap->n,nt);
ierr = VecScatterInitializeForGPU(a->Mvctx,xx);CHKERRQ(ierr);
ierr =
I am stumped with this GPU bug(s). Maybe someone has an idea.
I did find a bug in the cuda transpose mat-vec that cuda-memcheck detected,
but I still have differences between the GPU and CPU transpose mat-vec.
I've got it down to a very simple test: bicg/none on a tiny mesh with two
processors.
Mark,
Don't worry about this. I am fixing.
> On Jul 9, 2019, at 7:28 AM, PETSc checkBuilds via petsc-checkbuilds
> wrote:
>
>
>
> Dear PETSc developer,
>
> This email contains listings of contributions attributed to you by
> `git blame` that caused compiler errors or warnings in
Matthew Knepley writes:
> On Mon, Jul 8, 2019 at 10:37 PM Jed Brown via petsc-dev <
> petsc-dev@mcs.anl.gov> wrote:
>
>> "Smith, Barry F. via petsc-dev" writes:
>>
>> >> On Jul 8, 2019, at 9:53 PM, Jakub Kruzik via petsc-dev <
>> petsc-dev@mcs.anl.gov> wrote:
>> >>
>> >> Just to clarify, the