Hmm, I fixed this yesterday and pushed my branch. Just confirmed that the 
branch does not use PetscFree1() and that tmp is initialized in the 
declaration. 

   Perhaps the most recent version of the branch did not get merged to 
next-tmp? Anyways please try to get the latest in next or next-tmp for final 
testing.

  Barry


> On Jun 23, 2019, at 3:28 PM, PETSc checkBuilds 
> <[email protected]> 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 [email protected] if you are unable
> to resolve the issues.
> 
> Thanks,
>  The PETSc development team
> 
> ----
> 
> warnings attributed to commit 
> https://bitbucket.org/petsc/petsc/commits/09c5633
> Non-numeric optimizations focused on AIJ, MatFDColoring, and 
> DMCreateMatrix_DA_*AIJ, looking to improve performance in GPU environments
> 
>  src/mat/impls/aij/mpi/fdmpiaij.c:564
>    
> [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs//archive/2019/06/23/build_next-tmp_arch-linux-pkgs-gcov_cg.log]
>      /sandbox/petsc/petsc.next-tmp-2/src/mat/impls/aij/mpi/fdmpiaij.c:564:45: 
> warning: 'tmp' may be used uninitialized in this function 
> [-Wmaybe-uninitialized]
>    
> [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs//archive/2019/06/23/build_next-tmp_arch-linux-cmplx-gcov_si.log]
>      /sandbox/petsc/petsc.next-tmp-2/src/mat/impls/aij/mpi/fdmpiaij.c:564:45: 
> warning: 'tmp' may be used uninitialized in this function 
> [-Wmaybe-uninitialized]
>    
> [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs//archive/2019/06/23/build_next-tmp_arch-linux-matlab-ilp64-gcov_thrash.log]
>      /sandbox/petsc/petsc.next-tmp/src/mat/impls/aij/mpi/fdmpiaij.c:564:45: 
> warning: 'tmp' may be used uninitialized in this function 
> [-Wmaybe-uninitialized]
>    
> [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs//archive/2019/06/23/build_next-tmp_arch-linux-gcov_cg.log]
>      /sandbox/petsc/petsc.next-tmp-3/src/mat/impls/aij/mpi/fdmpiaij.c:564:45: 
> warning: 'tmp' may be used uninitialized in this function 
> [-Wmaybe-uninitialized]
>    
> [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs//archive/2019/06/23/build_next-tmp_arch-linux-uni_crush.log]
>      /sandbox/petsc/petsc.next-tmp-2/src/mat/impls/aij/mpi/fdmpiaij.c:564:45: 
> warning: 'tmp' may be used uninitialized in this function 
> [-Wmaybe-uninitialized]
> 
>  src/mat/impls/aij/seq/seqviennacl/aijviennacl.cxx:130
>    
> [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs//archive/2019/06/23/build_next-tmp_arch-viennacl_frog.log]
>      
> /sandbox/petsc/petsc.next-tmp-2/src/mat/impls/aij/seq/seqviennacl/aijviennacl.cxx:130:34:
>  error: 'PetscFree1' was not declared in this scope
> 
> ----
> To opt-out from receiving these messages - send a request to 
> [email protected].

Reply via email to