[petsc-dev] [petsc-checkbuilds] PETSc blame digest (next) 2016-03-11

[Satish Balay]

Ops - I see src/vec/vec/utils/veccuda/vscatcuda.c was the new addition - and its from origin/pr421/alex/feature-veccuda

Satish

On Fri, 11 Mar 2016, Satish Balay wrote:

> There is one more broken build due to cuda changes.
> 
> 
> http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2016/03/11/make_next_arch-linux-pkgs-dbg-ftn-interfaces_crank.log
> 
> >>>>>>>
> /sandbox/petsc/petsc.clone-3/include/petsc/finclude/ftn-auto/petscvec.h90:740.52:
>     Included at /sandbox/petsc/petsc.clone-3/include/petsc/finclude/petscvec.h90:9:
>     Included at /sandbox/petsc/petsc.clone-3/src/vec/f90-mod/petscvecmod.F:25:
> 
>       subroutine VecScatterInitializeForGPU(a,b,c,z)
>                                                     1
> Error: Symbol 'vecscatterinitializeforgpu' at (1) already has an explicit interface
> <<<<
> 
> I see there are 2 impls of this function each in - resulting in 2
> 'intercace' definitions generated - causing this error.
> 
> src/vec/vec/utils/veccusp/vscatcusp.c
> src/vec/vec/utils/veccuda/vscatcuda.c
> 
> Perhaps they shoud be merged into a single one?
> 
> Satish
> 
> 
> 
> On Fri, 11 Mar 2016, 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 PETSc automated
> > testing.  Follow the links to see the full log files. Please attempt to fix
> > the issues promptly or let us know at petsc-dev at mcs.anl.gov if you are unable
> > to resolve the issues.
> > 
> > Thanks,
> >   The PETSc development team
> > 
> > ----
> > 
> > warnings attributed to commit https://bitbucket.org/petsc/petsc/commits/2692e27
> > Adding PREPROCESSOR directives to protect ELL and HYB storage formats.
> > 
> >   src/sys/objects/init.c:541
> >     [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2016/03/11/build_next_arch-c-exodus-dbg-builder_frog.log]
> >       /home/balay/petsc.clone-3/src/sys/objects/init.c:541:5: warning: implicit declaration of function 'cudaGetDeviceCount' [-Wimplicit-function-declaration]
> >     [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2016/03/11/build_next_arch-cuda-single_frog.log]
> >       /home/balay/petsc.clone-2/src/sys/objects/init.c:541:5: warning: implicit declaration of function 'cudaGetDeviceCount' [-Wimplicit-function-declaration]
> >     [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2016/03/11/build_next_arch-cuda-double_frog.log]
> >       /home/balay/petsc.clone/src/sys/objects/init.c:541:5: warning: implicit declaration of function 'cudaGetDeviceCount' [-Wimplicit-function-declaration]
> > 
> >   src/sys/objects/init.c:580
> >     [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2016/03/11/build_next_arch-cuda-single_frog.log]
> >       /home/balay/petsc.clone-2/src/sys/objects/init.c:580:7: warning: implicit declaration of function 'cudaSetDeviceFlags' [-Wimplicit-function-declaration]
> >     [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2016/03/11/build_next_arch-cuda-double_frog.log]
> >       /home/balay/petsc.clone/src/sys/objects/init.c:580:7: warning: implicit declaration of function 'cudaSetDeviceFlags' [-Wimplicit-function-declaration]
> >     [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2016/03/11/build_next_arch-c-exodus-dbg-builder_frog.log]
> >       /home/balay/petsc.clone-3/src/sys/objects/init.c:580:7: warning: implicit declaration of function 'cudaSetDeviceFlags' [-Wimplicit-function-declaration]
> > 
> > ----
> > To opt-out from receiving these messages - send a request to petsc-dev at mcs.anl.gov.
> > 
> 
>